[solved]Digikam fails to load with kde 4.8

After upgrading to kde4.8 digikam won't start:
digikam
digikam: error while loading shared libraries: libmarblewidget.so.12: cannot open shared object file: No such file or directory
creating a symlink to libmarblewidget.so.13 fix the starting issue but then no images are displayed so it's quiet useless
Bug is this one, marked as fixed:
https://bugs.archlinux.org/task/28127
But even with digikam 2.5.0-3 from [testing] I get the same error.
Ideas?
Last edited by steff (2012-01-29 14:14:38)

Solved with libkgeomap-2.5.0-4 and digikam 2.5.0-4, thanks to all.

Similar Messages

[Solved] colord fails to load

Hi,
Lately, colord.service fails to load with this message :
colord.service - Manage, Install and Generate Color Profiles
Loaded: loaded (/usr/lib/systemd/system/colord.service; static)
Active: failed (Result: core-dump) since lun. 2013-05-06 18:59:04 CEST; 6min ago
Process: 1480 ExecStart=/usr/lib/colord/colord (code=dumped, signal=SEGV)
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-6fb3a23d8d7d23908c613c556d3e10cf
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-99e1cb8aae315f3241bc6866325d7e1e
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-9641812b452fc79a145471df34e5133c
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-90bb3cf4d7f73e2aa1f2e7c93ca71710
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-bc2d6f78dfa777ece4bda1ecabceefc6
mai 06 18:59:04 shellphone colord[1480]: Profile added: icc-c3f7b1c952897dd0cea880a54292f0d1
mai 06 18:59:04 shellphone colord[1480]: (colord:1480): libcolord-CRITICAL **: cd_icc_load_data: assertion `data_len != 0' failed
mai 06 18:59:04 shellphone systemd-coredump[1483]: Process 1480 (colord) dumped core.
mai 06 18:59:04 shellphone systemd[1]: colord.service: main process exited, code=dumped, status=11/SEGV
mai 06 18:59:04 shellphone systemd[1]: MESSAGE=Unit colord.service entered failed state.
Does it work for you ? Any clue about what's happening ?
Last edited by omer666 (2013-05-14 12:26:08)

Works here v0.1.34-1. What version are you running?
Does it occur at boot and/or manual start?
Have you checked colord's bug tracker? If there's not a report there it's probably worth reporting as even if you have a set-up issue, it shouldn't really core dump.
Last edited by skanky (2013-05-15 13:42:20)

The applet fails to load. with 'red cross' screen JVM 1.6.19 and above

After updating the JVM to one of the latest version 1.6 builds, our users started to experience a problem with opening java applets.
All the users have JVM versions 1.6.0_19 – 1.6.0_26 on Windows 7/2008. The browser is IE8. On the server usually there is IIS7, with ‘Integrated Windows authentication’
on applet’s virtual folder. Applet’s classes are packaged into a signed JAR file. Both the client and the server are located in the same local area network with no proxy or firewall between them.
The applet’s website usually belongs to the trusted security zone. When loaded, the applet establishes HTTP connection to the server to get the necessary data.
When the user tries to open an HTML page containing the applet, there can be the following scenarios:
1.     The applet fails to load. We’re getting a ‘red cross’ screen. All the HTML elements except of the applet are loaded OK.
From the IIS log we can see that the loading of the JAR file failed with the error code 401, the user name field in the log for the JAR is empty.
2.     The java asks for the user name and password showing a popup ‘Authentication required’. At this moment we can see the following message in the Java console:
network: Firewall authentication: site=/XX.XX.XX.XX:XX, protocol=http, prompt=, scheme=ntlm
If the user enters the correct credentials, the applet loads OK. Even if the user checks the ‘Save the password in your password list’ checkbox, Java continues to ask for credentials
on every page reload. It’s worth to note that the company’s external firewall doesn’t get any requests from the applet.
The problems happen even when the client and the server are located on the same machine, but never happens when we use localhost as the server name in the page URL.
During investigations we found out the following workarounds:
1.     Enabling anonymous authentication on the virtual folder always solves the problem.
2.     Sometimes, changing security zone from ‘Trusted’ to ‘Local intranet’ solves the scenario 2 (‘Authentication required’ popup) problem.
It’s worth to note that changing the security zone never helps if the page URL contains dots (for example, uses IP address instead the server name).
3.     Upgrading to IE9 solves the scenario 2 problem partly: Java asks for the credentials only once.

I have the same issue. I use single sign-on with IIS 7 and Integrated Window authentication on the tomcat virtual folder. The applet jar file is on the root directory of the web application (the same level of index.html). So I use '.' as the code_base to call the applet from javascript.
So when I launch my web application into a browser, the auto-connection is successfully performed (single sign-on through Upstream, kerberos, remote_user, ...). But when I want to launch the applet in the web application, a new authentication panel (red panel with "authentication required") occurs in order to set credentials (login, password, domain) with the message in the java applet console:
"network: Firewall authentication: site=myApplicationUrl, protocol=http, prompt=, scheme=ntlm"
So why the applet doesn't inherit previous credentials in this case ??
Have you solved this problem ?
Thanks
Edited by: 886341 on 20 sept. 2011 08:56

[SOLVED]Get [FAIL] when loading user specified modules.

That is it, when the system is booting i get a [FAIL] message when loading user specified modules after upgrading udev, and the kmod new module handling or something as say in the news. I dont have a modprobe.conf or a modprobe.conf.pacsave file either and creating a modprobe.conf file doesn't solve the problem. The strange thing is that the modules are loaded anyways. I mean the ones that are specified in rc.conf. I dont know if the system [FAIL] to load that modules or others...The system works fine for now too.
Thanks.
PD: sorry if you notice my poor english.
Last edited by Hyugga (2012-01-22 23:09:02)

I had the same problem and removing the governor performance from rc.conf solved the problem. I tried however to remove both governors and only leave powernow-k8 (this is the only one that works for me) leaving rc.conf like this:
MODULES=(brcmsmac powernow-k8)
When I boot the laptop and check which governors are available and being used I get the following:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.10 GHz.
This like as if the ondemand governor would not be available but when unplugging the laptop and check again I get this:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
This shows that the ondemand module can be autoloaded when needed, so I leave rc.conf only with powernow-k8.
Thanks for your help.

[SOLVED] XOrg fails to load Nvidia driver on startup

Hi,
I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
$sudo systemctl restart kdm
works, and everything starts up fine. When kdm is in the failed state, I see this:
$sudo systemctl status kdm
● kdm.service - K Display Manager
Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
Main PID: 247 (kdm)
CGroup: /system.slice/kdm.service
└─247 /usr/bin/kdm -nodaemon
Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
Dec 19 18:47:27 laptop kdm[247]: X server died during startup
Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
And in my XOrg log, I see:
[ 3.639]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 3.639]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 3.639] X Protocol Version 11, Revision 0
[ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 3.639] Build Date: 10 December 2014 02:34:24PM
[ 3.639]
[ 3.639] Current version of pixman: 0.32.6
[ 3.639] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
[ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.649] (==) No Layout section. Using the first Screen section.
[ 3.649] (==) No screen section available. Using defaults.
[ 3.649] (**) |-->Screen "Default Screen Section" (0)
[ 3.649] (**) | |-->Monitor "<default monitor>"
[ 3.650] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3.650] (==) Automatically adding devices
[ 3.650] (==) Automatically enabling devices
[ 3.650] (==) Automatically adding GPU devices
[ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3.658] Entry deleted from font path.
[ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.659] Entry deleted from font path.
[ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.660] Entry deleted from font path.
[ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.660] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.660] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.660] (II) Loader magic: 0x818d80
[ 3.660] (II) Module ABI versions:
[ 3.660] X.Org ANSI C Emulation: 0.4
[ 3.660] X.Org Video Driver: 18.0
[ 3.660] X.Org XInput driver : 21.0
[ 3.660] X.Org Server Extension : 8.0
[ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
[ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.664] (II) LoadModule: "glx"
[ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
[ 3.767] compiled for 4.0.2, module version = 1.0.0
[ 3.767] Module class: X.Org Server Extension
[ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 3.769] (==) Matched nouveau as autoconfigured driver 0
[ 3.769] (==) Matched nv as autoconfigured driver 1
[ 3.769] (==) Matched modesetting as autoconfigured driver 2
[ 3.769] (==) Matched fbdev as autoconfigured driver 3
[ 3.769] (==) Matched vesa as autoconfigured driver 4
[ 3.769] (==) Assigned the driver to the xf86ConfigLayout
[ 3.769] (II) LoadModule: "nouveau"
[ 3.769] (WW) Warning, couldn't open module nouveau
[ 3.769] (II) UnloadModule: "nouveau"
[ 3.769] (II) Unloading nouveau
[ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 3.769] (II) LoadModule: "nv"
[ 3.769] (WW) Warning, couldn't open module nv
[ 3.769] (II) UnloadModule: "nv"
[ 3.769] (II) Unloading nv
[ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
[ 3.769] (II) LoadModule: "modesetting"
[ 3.769] (WW) Warning, couldn't open module modesetting
[ 3.769] (II) UnloadModule: "modesetting"
[ 3.769] (II) Unloading modesetting
[ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.769] (II) LoadModule: "fbdev"
[ 3.769] (WW) Warning, couldn't open module fbdev
[ 3.769] (II) UnloadModule: "fbdev"
[ 3.769] (II) Unloading fbdev
[ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.769] (II) LoadModule: "vesa"
[ 3.770] (WW) Warning, couldn't open module vesa
[ 3.770] (II) UnloadModule: "vesa"
[ 3.770] (II) Unloading vesa
[ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.770] (EE) No drivers available.
[ 3.770] (EE)
Fatal server error:
[ 3.770] (EE) no screens found(EE)
[ 3.770] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 3.770] (EE)
Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
[ 78.897]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 78.897]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 78.897] X Protocol Version 11, Revision 0
[ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 78.897] Build Date: 10 December 2014 02:34:24PM
[ 78.897]
[ 78.897] Current version of pixman: 0.32.6
[ 78.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
[ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 78.897] (==) No Layout section. Using the first Screen section.
[ 78.897] (==) No screen section available. Using defaults.
[ 78.897] (**) |-->Screen "Default Screen Section" (0)
[ 78.897] (**) | |-->Monitor "<default monitor>"
[ 78.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 78.898] (==) Automatically adding devices
[ 78.898] (==) Automatically enabling devices
[ 78.898] (==) Automatically adding GPU devices
[ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 78.898] Entry deleted from font path.
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 78.898] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 78.898] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 78.898] (II) Loader magic: 0x818d80
[ 78.898] (II) Module ABI versions:
[ 78.898] X.Org ANSI C Emulation: 0.4
[ 78.898] X.Org Video Driver: 18.0
[ 78.898] X.Org XInput driver : 21.0
[ 78.898] X.Org Server Extension : 8.0
[ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
[ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 78.901] (II) LoadModule: "glx"
[ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
[ 78.913] compiled for 4.0.2, module version = 1.0.0
[ 78.913] Module class: X.Org Server Extension
[ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
[ 78.914] (==) Matched nvidia as autoconfigured driver 0
[ 78.914] (==) Matched nouveau as autoconfigured driver 1
[ 78.914] (==) Matched nv as autoconfigured driver 2
[ 78.914] (==) Matched nouveau as autoconfigured driver 3
[ 78.914] (==) Matched nv as autoconfigured driver 4
[ 78.914] (==) Matched modesetting as autoconfigured driver 5
[ 78.914] (==) Matched fbdev as autoconfigured driver 6
[ 78.914] (==) Matched vesa as autoconfigured driver 7
[ 78.914] (==) Assigned the driver to the xf86ConfigLayout
[ 78.914] (II) LoadModule: "nvidia"
[ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 78.920] compiled for 4.0.2, module version = 1.0.0
[ 78.920] Module class: X.Org Video Driver
[ 78.920] (II) LoadModule: "nouveau"
[ 78.921] (WW) Warning, couldn't open module nouveau
[ 78.921] (II) UnloadModule: "nouveau"
[ 78.921] (II) Unloading nouveau
[ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 78.921] (II) LoadModule: "nv"
[ 78.921] (WW) Warning, couldn't open module nv
[ 78.921] (II) UnloadModule: "nv"
[ 78.921] (II) Unloading nv
[ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
[ 78.921] (II) LoadModule: "modesetting"
[ 78.921] (WW) Warning, couldn't open module modesetting
[ 78.921] (II) UnloadModule: "modesetting"
[ 78.921] (II) Unloading modesetting
[ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 78.921] (II) LoadModule: "fbdev"
[ 78.922] (WW) Warning, couldn't open module fbdev
[ 78.922] (II) UnloadModule: "fbdev"
[ 78.922] (II) Unloading fbdev
[ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 78.922] (II) LoadModule: "vesa"
[ 78.922] (WW) Warning, couldn't open module vesa
[ 78.922] (II) UnloadModule: "vesa"
[ 78.922] (II) Unloading vesa
[ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 78.922] (++) using VT number 7
[ 78.935] (II) Loading sub module "fb"
[ 78.935] (II) LoadModule: "fb"
[ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 78.936] (II) Module fb: vendor="X.Org Foundation"
[ 78.936] compiled for 1.16.2.901, module version = 1.0.0
[ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.936] (II) Loading sub module "wfb"
[ 78.936] (II) LoadModule: "wfb"
[ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 78.937] (II) Module wfb: vendor="X.Org Foundation"
[ 78.937] compiled for 1.16.2.901, module version = 1.0.0
[ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.937] (II) Loading sub module "ramdac"
[ 78.937] (II) LoadModule: "ramdac"
[ 78.937] (II) Module "ramdac" already built-in
[ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 78.939] (==) NVIDIA(0): RGB weight 888
[ 78.939] (==) NVIDIA(0): Default visual is TrueColor
[ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
[ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 79.610] (II) NVIDIA(0): 3D Vision stereo.
[ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
[ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
[ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
[ 79.616] (--) NVIDIA(0): DFP-2
[ 79.616] (--) NVIDIA(0): DFP-3
[ 79.616] (--) NVIDIA(0): DFP-4
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
[ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
[ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
[ 79.618] (==) NVIDIA(0):
[ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 79.618] (==) NVIDIA(0): will be used as the requested mode.
[ 79.618] (==) NVIDIA(0):
[ 79.619] (II) NVIDIA(0): Validated MetaModes:
[ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
[ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 80.144] (--) NVIDIA(0): option
[ 80.144] (--) Depth 24 pixmap format is 32 bpp
[ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 80.144] (II) NVIDIA: access.
[ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 80.150] (II) NVIDIA(0): Config Options in the README.
[ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 80.532] (==) NVIDIA(0): Backing store enabled
[ 80.532] (==) NVIDIA(0): Silken mouse enabled
[ 80.533] (==) NVIDIA(0): DPMS enabled
[ 80.533] (II) Loading sub module "dri2"
[ 80.533] (II) LoadModule: "dri2"
[ 80.533] (II) Module "dri2" already built-in
[ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
[ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 80.533] (--) RandR disabled
[ 80.539] (II) Initializing extension GLX
[ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.605] (II) LoadModule: "evdev"
[ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 80.607] (II) Module evdev: vendor="X.Org Foundation"
[ 80.607] compiled for 1.16.2, module version = 2.9.1
[ 80.607] Module class: X.Org XInput Driver
[ 80.607] ABI class: X.Org XInput driver, version 21.0
[ 80.607] (II) Using input driver 'evdev' for 'Power Button'
[ 80.607] (**) Power Button: always reports core events
[ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
[ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.608] (--) evdev: Power Button: Found keys
[ 80.608] (II) evdev: Power Button: Configuring as keyboard
[ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
[ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 80.608] (**) Option "xkb_rules" "evdev"
[ 80.608] (**) Option "xkb_model" "pc104"
[ 80.608] (**) Option "xkb_layout" "us"
[ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
[ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
[ 80.635] (**) Video Bus: always reports core events
[ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
[ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 80.635] (--) evdev: Video Bus: Found keys
[ 80.635] (II) evdev: Video Bus: Configuring as keyboard
[ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
[ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 80.635] (**) Option "xkb_rules" "evdev"
[ 80.635] (**) Option "xkb_model" "pc104"
[ 80.635] (**) Option "xkb_layout" "us"
[ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
[ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.636] (II) Using input driver 'evdev' for 'Power Button'
[ 80.636] (**) Power Button: always reports core events
[ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
[ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.636] (--) evdev: Power Button: Found keys
[ 80.636] (II) evdev: Power Button: Configuring as keyboard
[ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
[ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 80.636] (**) Option "xkb_rules" "evdev"
[ 80.636] (**) Option "xkb_model" "pc104"
[ 80.636] (**) Option "xkb_layout" "us"
[ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
[ 80.637] (II) No input driver specified, ignoring this device.
[ 80.637] (II) This device may have been added with another device file.
[ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
[ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
[ 80.637] (**) Sleep Button: always reports core events
[ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
[ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 80.637] (--) evdev: Sleep Button: Found keys
[ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
[ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
[ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 80.637] (**) Option "xkb_rules" "evdev"
[ 80.637] (**) Option "xkb_model" "pc104"
[ 80.637] (**) Option "xkb_layout" "us"
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
[ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 80.639] (**) LOGITECH G110 G-keys: always reports core events
[ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
[ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 80.639] (**) Option "xkb_rules" "evdev"
[ 80.639] (**) Option "xkb_model" "pc104"
[ 80.639] (**) Option "xkb_layout" "us"
[ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
[ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.639] (**) Gaming Keyboard G110: always reports core events
[ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.640] (**) Option "xkb_layout" "us"
[ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
[ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.640] (**) Gaming Keyboard G110: always reports core events
[ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.641] (**) Option "xkb_layout" "us"
[ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
[ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
[ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.641] (**) Razer Razer Lachesis: always reports core events
[ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
[ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
[ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
[ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
[ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
[ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
[ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
[ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
[ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
[ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
[ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
[ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
[ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
[ 80.642] (II) No input driver specified, ignoring this device.
[ 80.642] (II) This device may have been added with another device file.
[ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
[ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
[ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.643] (**) Razer Razer Lachesis: always reports core events
[ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
[ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
[ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
[ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
[ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
[ 80.643] (**) Option "xkb_rules" "evdev"
[ 80.643] (**) Option "xkb_model" "pc104"
[ 80.643] (**) Option "xkb_layout" "us"
[ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 80.643] (II) No input driver specified, ignoring this device.
[ 80.643] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 80.645] (II) No input driver specified, ignoring this device.
[ 80.645] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
[ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
[ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
[ 80.645] (**) BisonCam, NB Pro: always reports core events
[ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
[ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
[ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
[ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
[ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
[ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
[ 80.645] (**) Option "xkb_rules" "evdev"
[ 80.645] (**) Option "xkb_model" "pc104"
[ 80.645] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
[ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
[ 80.646] (**) Option "xkb_rules" "evdev"
[ 80.646] (**) Option "xkb_model" "pc104"
[ 80.646] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
[ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 80.647] (II) LoadModule: "synaptics"
[ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
[ 80.647] compiled for 1.16.0, module version = 1.8.1
[ 80.647] Module class: X.Org XInput Driver
[ 80.647] ABI class: X.Org XInput driver, version 21.0
[ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.647] (**) Option "Device" "/dev/input/event20"
[ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 80.757] (**) Option "TapButton1" "1"
[ 80.757] (**) Option "TapButton2" "2"
[ 80.757] (**) Option "TapButton3" "3"
[ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
[ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[ 80.811] (II) No input driver specified, ignoring this device.
[ 80.811] (II) This device may have been added with another device file.
[ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
Notably, the following lines appear in the working case, but not the broken case:
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
Does anyone know what might be going on here?
Last edited by straemer (2014-12-20 13:03:58)

Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.

[Solved] Catalyst fails to load kernel module

I have just been through the Catalyst install guide, I installed from the Vi0L0 repos rather than building myself.
Everything appeared to go fine, however fglrx fails to load when I reboot. The xorg log contains;
fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible
fglrx(0): **********************************************************
fglrx(0): * DRI initialization failed
fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible
fglrx(0): * 2D and 3D acceleration disabled
fglrx(0): **********************************************************
Is this recoverable? Or does this mean that the current Vi0L0 module has not been built for my kernel (3.11.5-1-ARCH)?
Last edited by ~lynks (2013-11-03 16:16:00)

This issue has now been resolved after the update to xorg 1.14
lsmod | grep fglrx
shows fglrx is not loaded, and:
modprobe fglrx
returns with;
modprobe: ERROR: could not insert 'fglrx': Exec format error
Does that indicate a 32/64 bit issue?
This issue has now been resolved after the update to xorg 1.14
Last edited by ~lynks (2013-11-03 16:15:48)

AOL fails to load with Firefox (hangs) all fine with Chrome??

Firefox has always been the prefered browser. Updated version(s), now fail to load AOL (hangs) No problem however, when using Chrome ?

Try to remove the cert8.db file in the Firefox Profile Folder or rename the file to cert8.db.old to remove the intermediate certificates that Firefox has stored.
Firefox will automatically store new intermediate certificates when you visit websites that send them.
You can use this button to go to the Firefox profile folder:
* Help > Troubleshooting Information > Profile Directory: Open Containing Folder
* http://kb.mozillazine.org/Profile_folder_-_Firefox

[SOLVED] How to start JACK with KDE 4? (and which JACK should I use?)

Hi again
I'm using KDE 4, and I've just installed JACK again, and since I can't find any decent documentation on this, I'm having a bit of a problem.
Currently I have jack from [extra] installed, rather than jack2. When I try starting jack as the ArchWiki suggests, i.e. by typing "jackd -d alsa", I get the following error:
$ jackd -d alsa
jackd 0.120.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
the playback device "hw:0" is already in use. Please stop the application using it and run JACK again
cannot load driver module alsa
I've also tried jack2 from [community], and after starting it with "jack_control start", I get this...
$ jack_control start
--- start
DBus exception: org.jackaudio.Error.Generic: Failed to start server
So how do I start it? I'm guessing jack doesn't want to start because some other KDE application grabbed alsa before jackd (but I've been wrong before), and I don't have the slightest idea what jack2 is about with that "generic" error. If anyone would help me shed some light on this, I'd appreciate it a lot.
Thanks in advance!
Last edited by Wintershade (2011-03-26 19:22:08)

@schivmeister thanks that one worked
Yes, it was knotify4. So now this part works. I've switched to jack2 and it works flawlessly when starting it with jackd
So this part is solved... now, would you be so kind (if you know) as to point me to some tutorials or howtos (or proper documentation, cos I can't find much of that either) on how to connect various ALSA channels with JACK?
Basically, I want to route my PCM channel and the Mic channel into Capture 1 (or one to Capture 1 and other to Capture 2), since my Intel HDA audio card doesn't have the "Mix" or "What-U-Hear" or whatever as an available capture source. Any leads on that? (or do I have to open another thread for it?)
TIA

[solved] MySQLd fails to load

<solution>
Solved by reinstalling the package...
</solution>
Hey,
Ever since the last mysqld update, it won't load for me.
First I checked the error logs, but it doesn't have anything usful.
# tail -n 2 /var/lib/mysql/myhostname.err
090729 07:02:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
090729 07:02:06 mysqld_safe mysqld from pid file /var/lib/mysql/myhostname.pid ended
But dmesg is a bit more interesting:
mysqld[5922] general protection ip:94b9ca sp:7fff769940e0 error:0 in mysqld[400000+818000]
Frankly though, I have no idea what this 'general protection' message means.
I tried that chmod thing in the wiki, no help.
Running mysql 5.1.36-1 on Arch64.
Also note that even running 'mysqld' alone, 'mysqld --help' or 'mysqld --anything-else' does the same: it dumps a core file, quits and dmesg shows that line.
Any ideas?
Thanks.
Yo'av
Last edited by bjesus (2009-07-29 11:13:08)

I'm running Arch64 and your same version of MySQL and it works.
I've seen lots of core dumps with various versions of MySQL that I won't be surprised if it were an upstream bug.
Try opening an bug report at http://bugs.mysql.com/

[SOLVED]Chromium fails to load Amazon

Has anyone else had problems loading amazon.com on chromium?
Been happening with
╔═[20:13]═[inxs @ wolfdale]
╚═══===═══[~]>> chromium --version
Chromium 6.0.472.62
It started with the version before this one. Basically the moment you go to amazon.com, it fails and says "Aw snap". Don't think its flash, as you tube works fine.

never mind. I deleted the user config and all is well now.
delete
rm -f ~/.cache/chromium/Cache/*
rm -f ~/.cache/chromium/Media\ Cache/*
rm -rf ~/.config/chromium
Don't know what the problem was though, but the solution was offered by clicking on the link "Learn More" under the "Aw Snap" -- They only talk about deleting user data under windows, but I figured it should work for linux as well.
and it does !!

[SOLVED] slim fails to load on boot

Hi,
On boot the system will attempt to load slim, but fails, with no onscreen reason as to why. If I attempt to launch slim from the console, the same thing happens. Here's what systemctl thinks:-
$ systemctl status slim
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Fri 2014-01-31 20:24:01 GMT; 2h 15min ago
Process: 325 ExecStart=/usr/bin/slim -nodaemon (code=exited, status=1/FAILURE)
Main PID: 325 (code=exited, status=1/FAILURE)
CGroup: /system.slice/slim.service
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XVideo
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XVideo-MotionCompensation
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-VidModeExtension
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-DGA
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-DRI
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension DRI2
Jan 31 20:23:58 laptop slim[325]: Loading extension GLX
Jan 31 20:23:58 laptop slim[325]: (II) [KMS] Kernel modesetting enabled.
Jan 31 20:24:01 laptop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Jan 31 20:24:01 laptop systemd[1]: Unit slim.service entered failed state.
There's this from journalctl too:-
Jan 31 20:24:01 laptop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Jan 31 20:24:01 laptop slim[325]: (EE) Server terminated successfully (0). Closing log file.
Jan 31 20:24:01 laptop systemd[1]: Unit slim.service entered failed state.
I should add. If I login to a bash prompt, and launch X with startx, it boots to the desktop.
Last edited by n1md4 (2014-01-31 23:25:39)

pacman -R slim
pacman -S slim

[solved] qbittorrent fails to load

Hi,
I installed qbittorrent (and rb_libtorrent) from community repo about one month ago (since then I'm using Arch, so I'm pretty new to it, before I was using Ubuntu64). Everything works fine till 13/14. July. On that day there was a qt update and starting qbittorrent leads to an segmentation fault, reinstallation changed nothing. Next day an rb_libtorrent update: no segmentation fault any more, but:
qbittorrent: error while loading shared libraries: libtorrent-0.13.so: cannot open shared object file: No such file or directory
I tried to reinstall, but nothing changed.
Because there is no update of qbittorrent in community repo yet (for x86_64), I tried to make my own pkgbuild (found some old ones here and modified them). Building and installation worked fine, but qbittorrent don't start either (segmentation fault again).
What am I doing wrong?
Hier my pkgbuilds:
rb_libtorrent
pkgname=rb_libtorrent
pkgver=0.13
pkgrel=1
pkgdesc="A C++ library that aims to be a good alternative to all the other bittorrent implementations around"
arch=(i686 x86_64)
url="http://www.rasterbar.com/products/libtorrent/"
license=('GPL')
makedepends=('boost')
conflicts=('libtorrent')
source=(http://garr.dl.sourceforge.net/sourceforge/libtorrent/libtorrent-$pkgver.tar.gz)
build() {
cd $startdir/src/libtorrent-$pkgver
./configure --prefix=/usr
--disable-debug
--with-boost-date-time=mt
--with-boost-filesystem=mt
--with-boost-thread=mt
--with-boost-regex=mt
--with-boost-program_options=mt
make || return 1
make DESTDIR=$startdir/pkg install
qbittorrent
pkgname=qbittorrent
pkgver=1.0.0
pkgrel=3
pkgdesc="A bittorrent client written in C++ / Qt4 using the good libtorrent library"
arch=(i686 x86_64)
url="http://www.qbittorrent.org/"
license=('GPL')
depends=('qt' 'rb_libtorrent' 'curl' 'python' 'boost')
source=(http://osdn.dl.sourceforge.net/sourceforge/qbittorrent/$pkgname-$pkgver.tar.gz)
build() {
cd $startdir/src/$pkgname-$pkgver
./configure --prefix=$startdir/pkg/usr --qtdir=/opt/qt4
make || return 1
make DESTDIR=$startdir/pkg install
I tried to install qbittorrent in Arch32 (Virtalbox) too (there was an qbittorrent update), but it didn't start either (segmentation fault).
Qbittorrent is my favorite torrent client, please help me that I could use it again.
(and sorry for my english ^^)
Problem solved:
creating a sym link in /usr/lib/ was the solution:
ln -sf /usr/lib/libtorrent-rasterbar.so /usr/lib/libtorrent-0.13.so
Everything is fine again
Last edited by inside-hex (2008-07-23 20:09:46)

Right now, I am having trouble compiling qbittorrent from the aur. For some reason, it keeps spitting that I need a version of libtorrent, which for one thing is wrong because qbittorrent uses rb_libtorrent, and my version of rb_libtorrent is up to date.
Update: I had to manually get the source from the qbittorrent site and compile it rather than using the version I already had up to make the latest package. I will give this a shot and let you know how it turns out.
FINAL SOLUTION!
I just had to rebuild the package, I will upload it to my repository right now.
pacman -Sy qbittorrent should yield a working product now. Sorry for having it broken, and thank you for bringing this problem to my attention.
Last edited by Fatsobob (2007-05-29 12:53:09)

[SOLVED] mongodb fails to start with exit status 4

Today I tried starting mongodb via systemctl and it would fail with exit status 4. The issue turned out to be related to an upgrade from mongodb 2.6 to 3.0. It took me a bit of digging and trial and error to get it running again, so I thought I should share the steps in case anyone else runs into this
1. Downgrade to 2.6 (using the latest 2.6.x you hopefully still have in the cache)
$ pacman -U /var/cache/pacman/pkg/mongodb-2.6.8-1-x86_64.pkg.tar.xz
$ systemctl start mongodb
2. Run authSchemaUpgrade
$ mongo
> db.adminCommand({authSchemaUpgrade: 1});
3. Upgrade mongdb
$ pacman -S mongodb
Hope this is helpful to someone.

https://wiki.archlinux.org/index.php/Catalyst
- xorg-server 1.12 is in [extra] repo, catalyst does not support it so please use [xorg111] repo.

[Solved] Gummiboot fails to load Initramfs

I installed Arch on two partitions, one encrypted with LVM on LUKS
(sda2) and a separate /boot partition (sda1). I use gummiboot as my bootloader.
The gummiboot entry which loads the initramfs looks as follows:
title Arch linux
efi \EFI\arch\vmlinuz-linux.efi
options initrd=\EFI\arch\initramfs-linux.img cryptdevice=/dev/sda2:vgroup root=/dev/mapper/vgroup-root rw acpi_backlight=vendor
After each kernel update (i.e. rebuilding the initramfs) I manually copy
the images to where the loader entries point.
cp /boot/initramfs-linux.img /boot/EFI/arch/
cp /boot/initramfs-linux-fallback.img /boot/EFI/arch/
cp /boot/vmlinuz-linux /boot/EFI/arch/
cp /boot/vmlinuz-linux /boot/EFI/arch/vmlinuz-linux.efi
(Actually I'm not sure if I need the .efi extension on vimlinuz-linux,
so I copy them both...)
When this Laptop boots, it shows the gummiboot loader and I select the
"Arch Linux" entry. With the last kernel update, when I hit the "Arch
Linux" boot entry, the screen goes black for some seconds, then the
whole screen gets pixelated with some colorful static noise.
It looks like the initramfs is corrupted/not found, so chrooted into my
system from the live installer and reinstalled the kernel, mkinitcpio
and gummiboot ('linux' 3.12.7-2, 'gummiboot' 41-1, 'mkinitcpio' 16-2).
I also re-ran
gummiboot install
Still, the system refuses to boot.
Since I get no error output at all, I can't provide much more debug
information. I am aware of a rather large number of threads but in
virtually all of those cases the boot process crashes with some helpful
error messages...
Anyone got some helpful hint? It looks like I am missing something
obvious.
Last edited by okyr (2014-01-20 15:34:28)

By the way, why are you copying your bootimages manually? Your folders seem odd to me, but maybe thats just a lack of information on my side.
An loader entry on my box looks like this:
root@x230 /boot/loader/entries # cat arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda2 quiet rw init=/usr/lib/systemd/systemd add_efi.memmap acpi_osi="!Windows 2012"
The .img files are simply in /boot where mkinitcpio puts them after the kernel update.

Oracleasm lib failed to load with "Invalid module format" error

Hi,
I'm tring to install the oracleasm lib onto our hardened Redhat EL5 server
I've download the oracleasm rpm from this page http://www.oracle.com/technology/software/tech/linux/asmlib/rhel5.html.
We're using Redhat 5 U 2
[root@PG673 modules]# uname -rm
2.6.18-92.el5 x86_64
[root@PG673 modules]#
The package I downloaded is an exact match with our kernel version
[root@PG673 modules]# rpm -qa | grep asm
oracleasm-2.6.18-92.el5-2.0.5-1.el5
oracleasm-support-2.1.3-1.el5
oracleasm-support-2.1.3-1.el5
oracleasm-2.6.18-92.el5-2.0.5-1.el5
oracleasmlib-2.0.4-1.el5
oracleasmlib-2.0.4-1.el5
[root@PG673 modules]#
RPM installation went well, but when we run the /etc/init.d/oracleasm configure command, we hit the following error
[root@PG673 other]# /etc/init.d/oracleasm configure
/etc/init.d/oracleasm: line 207: /usr/sbin/oracleasm: cannot execute binary file
Later we found out that the oracleasm module haven't been loaded, so we try to load it manually, but we hit the "Invalid module format" error.
[root@PG673 modules]# modprobe -l | grep asm
/lib/modules/2.6.18-92.el5/kernel/drivers/addon/oracleasm/oracleasm.ko
[root@PG673 modules]# modprobe oracleasm
FATAL: Error inserting oracleasm (/lib/modules/2.6.18-92.el5/kernel/drivers/addon/oracleasm/oracleasm.ko): Invalid module format
[root@PG673 modules]#
As I know this error could happen if the driver version is not match with the system kernel version.
The problem is we're already using an exact match version of driver with our system, I can't think of what to do next in order to proceed the installation.
Really appreciate if someone could point me a direction.
Thanks
Mike

Hi Mike,
something looks a bit strange for me. On my OEL 5.4 x64 system i have just the following 3 packages:
$ rpm -qa | grep asm
oracleasm-2.6.18-164.el5-2.0.5-1.el5
oracleasm-support-2.1.3-1.el5
oracleasmlib-2.0.4-1.el5 Your packages should be I think the following:
http://oss.oracle.com/projects/oracleasm-support/dist/files/RPMS/rhel5/amd64/2.1.3/oracleasm-support-2.1.3-1.el5.x86_64.rpm
http://otn.oracle.com/software/tech/linux/asmlib/files/RPMS/rhel5/amd64/2.0.4/oracleasmlib-2.0.4-1.el5.x86_64.rpm
http://oss.oracle.com/projects/oracleasm/dist/files/RPMS/rhel5/amd64/2.0.5/2.6.18-92.el5/oracleasm-2.6.18-92.el5-2.0.5-1.el5.x86_64.rpm
Uninstall all asm packages and retry with just those three.
Good luck!
Cheers,
David
OCP 9i / 10g
http://www.oratoolkit.ch/knowledge/howto/installation/otn.php

[solved]Digikam fails to load with kde 4.8

Similar Messages

Maybe you are looking for