Multicast session doesn't start

Hi,
I use NW 6.0 with lasp SP and ZfD 4.01 IR7. I use ZfD Imaging via PXE.
Now I try configure Multicast imaging, setup Server propertities at NDS
etc.
When I boot workstations to PXE menu, on the screen shows multicast
address (231.X.X.X) multicast name and workstations wait for master to
start multicast.
I define that two stations may start multicast or 5 minutes to start it.
On server console shows Multicast sessions (Zenworks imaging server
staistics) with rights name.
But workstations waits for master and no image transfer from server.
Can you help me ?
Lubomir

> [email protected] wrote:
>
> > But workstations waits for master and no image transfer from server.
>
> hmm... are they on the same switch?
yes
> --
> If you have already compiled drivers or have linux.2 please put them on
> http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
> Live BootCd and USB Disk from Mike Charles
> http://forge.novell.com/modules/xfmod/project/?imagingx
> eZie http://forge.novell.com/modules/xfmod/project/?ezie
>
> Marcus Breiden
>
> If you are asked to email me information please change -- to - in my e-
mail
> address.
> The content of this mail is my private and personal opinion.
> http://www.edu-magic.net

Similar Messages

  • When i plug my iPhone 4gs to my macbook pro, it doesn't sync and this msg appearThe iPhone "iPhone de anthony" could not be synced because the sync session failed to start. can anyone help me

    when i plug my iPhone 4gs to my macbook pro, it doesn't sync and this msg appearThe iPhone “iPhone de anthony” could not be synced because the sync session failed to start. can anyone help me

    Same thing for me right now.  Anybody have a fix on a Mac?  My iPad syncs OK but my iphone 4S has this message.

  • [SOLVED] KDE Start New Session doesn't work from lock screen

    On my laptop, if I lock the KDE 4 session and then click Switch Users > Start New Session, I get a login screen and can log in as a different user. All good.
    If I do the same thing on my desktop, it doesn't work. When I click Switch Users > Start New Session, it doesn't start a new session or switch VTs. Instead, I just get reprompted for the existing user's password.
    Both machines are running fully updated Arch. Anyone know how I can troubleshoot this? The only difference I can think of between the laptop and desktop is that the desktop has nomodeset specified as a kernel boot parameter. (It won't boot without it.) Could this be interfering with automatic VT switching? Manual VT switching (e.g. Ctrl+Alt+F1) works fine.
    Last edited by Rob_H (2014-12-27 14:28:06)

    Little more detail. Checking the journal, I can see Xorg is failing to start on display :1. If I compare Xorg.0.log with Xorg.1.log, it appears that it's not finding the proprietary NVIDIA driver in the second case. Don't know why it would be any different for :1, though. See?
    Xorg.0.log (good):
    [ 10.219] (II) LoadModule: "glx"
    [ 10.220] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 10.293] (II) Module glx: vendor="NVIDIA Corporation"
    [ 10.293] compiled for 4.0.2, module version = 1.0.0
    [ 10.293] Module class: X.Org Server Extension
    [ 10.294] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
    [ 10.294] (II) Applying OutputClass "nvidia" to /dev/dri/card0
    [ 10.294] loading driver: nvidia
    [ 10.294] (==) Matched nvidia as autoconfigured driver 0
    [ 10.294] (==) Matched nouveau as autoconfigured driver 1
    [ 10.294] (==) Matched nv as autoconfigured driver 2
    [ 10.294] (==) Matched nouveau as autoconfigured driver 3
    [ 10.294] (==) Matched nv as autoconfigured driver 4
    [ 10.294] (==) Matched modesetting as autoconfigured driver 5
    [ 10.294] (==) Matched fbdev as autoconfigured driver 6
    [ 10.294] (==) Matched vesa as autoconfigured driver 7
    [ 10.294] (==) Assigned the driver to the xf86ConfigLayout
    [ 10.294] (II) LoadModule: "nvidia"
    [ 10.294] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 10.300] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 10.300] compiled for 4.0.2, module version = 1.0.0
    [ 10.300] Module class: X.Org Video Driver
    Xorg.1.log (bad):
    [ 2153.825] (II) LoadModule: "glx"
    [ 2153.825] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2153.833] (II) Module glx: vendor="NVIDIA Corporation"
    [ 2153.833] compiled for 4.0.2, module version = 1.0.0
    [ 2153.833] Module class: X.Org Server Extension
    [ 2153.833] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
    [ 2153.833] (==) Matched nouveau as autoconfigured driver 0
    [ 2153.833] (==) Matched nv as autoconfigured driver 1
    [ 2153.833] (==) Matched modesetting as autoconfigured driver 2
    [ 2153.833] (==) Matched fbdev as autoconfigured driver 3
    [ 2153.833] (==) Matched vesa as autoconfigured driver 4
    [ 2153.833] (==) Assigned the driver to the xf86ConfigLayout
    [ 2153.833] (II) LoadModule: "nouveau"
    [ 2153.833] (WW) Warning, couldn't open module nouveau
    Any idea what would cause it to work for :0 but fail for :1?

  • [SOLVED] Xorg doesn't start after upgrade to 1.17.1

    Archlinux i686
    Intel Core 2 Duo 6600
    01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] (rev a1)
    After following upgrades:
    [2015-02-26 03:27] [PACMAN] Running 'pacman -S mesa mesa-demos mesa-libgl'
    [2015-02-26 03:27] [ALPM] transaction started
    [2015-02-26 03:28] [ALPM] upgraded mesa (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-libgl (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-demos (8.2.0-3 -> 8.2.0-4)
    [2015-02-26 03:28] [ALPM] transaction completed
    [2015-02-26 03:28] [PACMAN] Running 'pacman -S xorg-server xorg-server-common'
    [2015-02-26 03:29] [ALPM] transaction started
    [2015-02-26 03:29] [ALPM] removed xf86-video-vesa (2.3.2-5)
    [2015-02-26 03:29] [ALPM] removed xf86-video-nouveau (1.0.11-2)
    [2015-02-26 03:29] [ALPM] removed xf86-video-modesetting (0.9.0-2)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server-common (1.16.3-2 -> 1.17.1-3)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server (1.16.3-2 -> 1.17.1-3)
    Xorg doesn't start after reboot and I found following kernel message:
    kernel: [drm:drm_mmap_locked] *ERROR* Could not find map
    and /var/log/Xorg.0.log looks like this:
    [ 5.591]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 5.591] X Protocol Version 11, Revision 0
    [ 5.591] Build Operating System: Linux 3.18.6-1-ARCH i686
    [ 5.591] Current Operating System: Linux emeria7 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:59:29 CET 2015 i686
    [ 5.591] Kernel command line: root=/dev/disk/by-label/archroot rw
    [ 5.591] Build Date: 22 February 2015 12:52:47PM
    [ 5.591]
    [ 5.592] Current version of pixman: 0.32.6
    [ 5.592] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 5.592] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 5.592] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 26 14:58:35 2015
    [ 5.597] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 5.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 5.598] (==) ServerLayout "ServerLayout0"
    [ 5.598] (==) No screen section available. Using defaults.
    [ 5.598] (**) |-->Screen "Default Screen Section" (0)
    [ 5.598] (**) | |-->Monitor "<default monitor>"
    [ 5.599] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 5.599] (**) | |-->Device "Device0"
    [ 5.599] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 5.599] (**) Option "BlankTime" "0"
    [ 5.599] (**) Option "StandbyTime" "0"
    [ 5.599] (**) Option "SuspendTime" "0"
    [ 5.599] (**) Option "OffTime" "0"
    [ 5.599] (==) Automatically adding devices
    [ 5.599] (==) Automatically enabling devices
    [ 5.599] (==) Automatically adding GPU devices
    [ 5.608] (==) 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/
    [ 5.608] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 5.608] (**) Extension "Composite" is disabled
    [ 5.608] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 5.608] (II) Loader magic: 0x829e700
    [ 5.608] (II) Module ABI versions:
    [ 5.608] X.Org ANSI C Emulation: 0.4
    [ 5.608] X.Org Video Driver: 19.0
    [ 5.608] X.Org XInput driver : 21.0
    [ 5.608] X.Org Server Extension : 9.0
    [ 5.611] (EE) systemd-logind: failed to get session: PID 995 does not belong to any known session
    [ 5.611] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 5.612] (--) PCI:*(0:1:0:0) 10de:0291:107d:2a62 rev 161, Mem @ 0xfd000000/16777216, 0xc0000000/268435456, 0xfc000000/16777216, I/O @ 0x0000ac00/128, BIOS @ 0x????????/131072
    [ 5.612] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 5.613] (II) LoadModule: "glx"
    [ 5.616] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.632] (II) Module glx: vendor="X.Org Foundation"
    [ 5.632] compiled for 1.17.1, module version = 1.0.0
    [ 5.632] ABI class: X.Org Server Extension, version 9.0
    [ 5.632] (==) AIGLX enabled
    [ 5.632] (==) Matched nouveau as autoconfigured driver 0
    [ 5.632] (==) Matched nv as autoconfigured driver 1
    [ 5.632] (==) Matched nouveau as autoconfigured driver 2
    [ 5.632] (==) Matched nv as autoconfigured driver 3
    [ 5.632] (==) Matched modesetting as autoconfigured driver 4
    [ 5.632] (==) Matched fbdev as autoconfigured driver 5
    [ 5.632] (==) Matched vesa as autoconfigured driver 6
    [ 5.632] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.632] (II) LoadModule: "nouveau"
    [ 5.632] (WW) Warning, couldn't open module nouveau
    [ 5.632] (II) UnloadModule: "nouveau"
    [ 5.632] (II) Unloading nouveau
    [ 5.632] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "nv"
    [ 5.633] (WW) Warning, couldn't open module nv
    [ 5.633] (II) UnloadModule: "nv"
    [ 5.633] (II) Unloading nv
    [ 5.633] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "modesetting"
    [ 5.633] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 5.634] (II) Module modesetting: vendor="X.Org Foundation"
    [ 5.634] compiled for 1.17.1, module version = 1.17.1
    [ 5.634] Module class: X.Org Video Driver
    [ 5.634] ABI class: X.Org Video Driver, version 19.0
    [ 5.634] (II) LoadModule: "fbdev"
    [ 5.634] (WW) Warning, couldn't open module fbdev
    [ 5.634] (II) UnloadModule: "fbdev"
    [ 5.634] (II) Unloading fbdev
    [ 5.634] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 5.634] (II) LoadModule: "vesa"
    [ 5.634] (WW) Warning, couldn't open module vesa
    [ 5.634] (II) UnloadModule: "vesa"
    [ 5.634] (II) Unloading vesa
    [ 5.634] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 5.634] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 5.634] (++) using VT number 7
    [ 5.635] (II) modeset(0): using drv /dev/dri/card0
    [ 5.635] (II) modeset(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.636] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [ 5.636] (==) modeset(0): RGB weight 888
    [ 5.636] (==) modeset(0): Default visual is TrueColor
    [ 5.636] (II) Loading sub module "glamoregl"
    [ 5.636] (II) LoadModule: "glamoregl"
    [ 5.636] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 5.647] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 5.647] compiled for 1.17.1, module version = 1.0.0
    [ 5.647] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.647] (II) glamor: OpenGL accelerated X.org driver based.
    [ 5.772] (II) glamor: EGL version 1.4 (DRI2):
    [ 5.786] (II) modeset(0): glamor initialized
    [ 5.786] (II) Loading sub module "dri2"
    [ 5.786] (II) LoadModule: "dri2"
    [ 5.786] (II) Module "dri2" already built-in
    [ 5.843] (II) modeset(0): Output DVI-0 has no monitor section
    [ 5.896] (II) modeset(0): Output DVI-1 has no monitor section
    [ 5.950] (II) modeset(0): Output TV-0 has no monitor section
    [ 6.006] (II) modeset(0): EDID for output DVI-0
    [ 6.006] (II) modeset(0): Manufacturer: SAM Model: 76f Serial#: 1110590261
    [ 6.006] (II) modeset(0): Year: 2011 Week: 8
    [ 6.006] (II) modeset(0): EDID Version: 1.3
    [ 6.006] (II) modeset(0): Digital Display Input
    [ 6.006] (II) modeset(0): Max Image Size [cm]: horiz.: 51 vert.: 29
    [ 6.006] (II) modeset(0): Gamma: 2.20
    [ 6.006] (II) modeset(0): DPMS capabilities: Off
    [ 6.006] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 6.006] (II) modeset(0): First detailed timing is preferred mode
    [ 6.006] (II) modeset(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    [ 6.006] (II) modeset(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    [ 6.006] (II) modeset(0): Supported established timings:
    [ 6.006] (II) modeset(0): 720x400@70Hz
    [ 6.006] (II) modeset(0): 640x480@60Hz
    [ 6.006] (II) modeset(0): 640x480@67Hz
    [ 6.006] (II) modeset(0): 640x480@72Hz
    [ 6.006] (II) modeset(0): 640x480@75Hz
    [ 6.006] (II) modeset(0): 800x600@56Hz
    [ 6.006] (II) modeset(0): 800x600@60Hz
    [ 6.006] (II) modeset(0): 800x600@72Hz
    [ 6.006] (II) modeset(0): 800x600@75Hz
    [ 6.006] (II) modeset(0): 832x624@75Hz
    [ 6.006] (II) modeset(0): 1024x768@60Hz
    [ 6.006] (II) modeset(0): 1024x768@70Hz
    [ 6.006] (II) modeset(0): 1024x768@75Hz
    [ 6.006] (II) modeset(0): 1280x1024@75Hz
    [ 6.006] (II) modeset(0): 1152x864@75Hz
    [ 6.006] (II) modeset(0): Manufacturer's mask: 0
    [ 6.006] (II) modeset(0): Supported standard timings:
    [ 6.006] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 6.006] (II) modeset(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 6.006] (II) modeset(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 6.006] (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 6.006] (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 6.006] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 6.007] (II) modeset(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 6.007] (II) modeset(0): #7: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 148.5 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Ranges: V min: 50 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 175 MHz
    [ 6.007] (II) modeset(0): Monitor name: SMBX2331
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 6.007] (II) modeset(0): Number of EDID sections to follow: 1
    [ 6.007] (II) modeset(0): EDID (in hex):
    [ 6.007] (II) modeset(0): 00ffffffffffff004c2d6f0735433242
    [ 6.007] (II) modeset(0): 0815010380331d782aee91a3544c9926
    [ 6.007] (II) modeset(0): 0f5054bfef80714f8100814081809500
    [ 6.007] (II) modeset(0): 950fa940b300023a801871382d40582c
    [ 6.007] (II) modeset(0): 4500fd1e1100001e011d007251d01e20
    [ 6.007] (II) modeset(0): 6e285500fd1e1100001e000000fd0032
    [ 6.007] (II) modeset(0): 4b1f5111000a202020202020000000fc
    [ 6.007] (II) modeset(0): 00534d4258323333310a2020202001ee
    [ 6.007] (II) modeset(0): 02031cf14890041f0514131203230907
    [ 6.007] (II) modeset(0): 078301000066030c00100080011d80d0
    [ 6.007] (II) modeset(0): 721c1620102c2580fd1e1100009e011d
    [ 6.007] (II) modeset(0): 8018711c1620582c2500fd1e1100009e
    [ 6.007] (II) modeset(0): 011d00bc52d01e20b8285540fd1e1100
    [ 6.007] (II) modeset(0): 001e8c0ad090204031200c405500fd1e
    [ 6.007] (II) modeset(0): 110000188c0ad08a20e02d10103e9600
    [ 6.007] (II) modeset(0): fd1e110000180000000000000000004c
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Printing probed modes for output DVI-0
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 170.24 1024 1108 1220 1416 768 768 770 801 doublescan -hsync +vsync (120.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 6.008] (II) modeset(0): Modeline "960x720"x75.0 148.50 960 1032 1144 1320 720 720 722 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "960x720"x60.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x75.0 144.00 928 992 1104 1280 696 696 698 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 101.25 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (93.8 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x70.0 94.50 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (87.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x65.0 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (81.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "700x525"x74.8 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (81.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
    [ 6.063] (II) modeset(0): EDID for output DVI-1
    [ 6.116] (II) modeset(0): EDID for output TV-0
    [ 6.116] (II) modeset(0): Output DVI-0 connected
    [ 6.116] (II) modeset(0): Output DVI-1 disconnected
    [ 6.116] (II) modeset(0): Output TV-0 disconnected
    [ 6.116] (II) modeset(0): Using exact sizes for initial modes
    [ 6.116] (II) modeset(0): Output DVI-0 using initial mode 1920x1080
    [ 6.116] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 6.116] (==) modeset(0): DPI set to (96, 96)
    [ 6.116] (II) Loading sub module "fb"
    [ 6.116] (II) LoadModule: "fb"
    [ 6.117] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 6.118] (II) Module fb: vendor="X.Org Foundation"
    [ 6.118] compiled for 1.17.1, module version = 1.0.0
    [ 6.118] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 6.118] (==) Depth 24 pixmap format is 32 bpp
    [ 6.462] (==) modeset(0): Backing store disabled
    [ 6.462] (==) modeset(0): Silken mouse enabled
    [ 6.464] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 6.535] (==) modeset(0): DPMS enabled
    [ 6.535] (WW) modeset(0): Option "EXANoComposite" is not used
    [ 6.535] (II) modeset(0): [DRI2] Setup complete
    [ 6.535] (II) modeset(0): [DRI2] DRI driver: nouveau
    [ 6.535] (II) modeset(0): [DRI2] VDPAU driver: nouveau
    [ 6.535] (--) RandR disabled
    [ 6.551] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 6.551] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 6.551] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 6.551] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 6.551] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 6.551] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 6.551] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 6.552] (II) AIGLX: Loaded and initialized nouveau
    [ 6.552] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 6.559] (II) modeset(0): Setting screen physical size to 507 x 285
    [ 6.741] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 6.741] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.741] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.741] (II) LoadModule: "evdev"
    [ 6.741] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.744] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.744] compiled for 1.16.2, module version = 2.9.1
    [ 6.744] Module class: X.Org XInput Driver
    [ 6.744] ABI class: X.Org XInput driver, version 21.0
    [ 6.744] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.744] (**) Power Button: always reports core events
    [ 6.744] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 6.744] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.744] (--) evdev: Power Button: Found keys
    [ 6.744] (II) evdev: Power Button: Configuring as keyboard
    [ 6.744] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.744] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.744] (**) Option "xkb_rules" "evdev"
    [ 6.744] (**) Option "xkb_model" "pc104"
    [ 6.744] (**) Option "xkb_layout" "us"
    [ 6.744] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.780] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 6.780] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.780] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.780] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.780] (**) Power Button: always reports core events
    [ 6.780] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 6.780] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.780] (--) evdev: Power Button: Found keys
    [ 6.780] (II) evdev: Power Button: Configuring as keyboard
    [ 6.780] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
    [ 6.780] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 6.780] (**) Option "xkb_rules" "evdev"
    [ 6.780] (**) Option "xkb_model" "pc104"
    [ 6.780] (**) Option "xkb_layout" "us"
    [ 6.780] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.781] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 6.781] (II) No input driver specified, ignoring this device.
    [ 6.781] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event10)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event7)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event8)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event9)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.784] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 6.784] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc050
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 6.784] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/0003:046D:C050.0001/input/input1/event1"
    [ 6.784] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 8)
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [ 6.785] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 6.785] (II) No input driver specified, ignoring this device.
    [ 6.785] (II) This device may have been added with another device file.
    [ 6.785] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
    [ 6.785] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 6.785] (**) AT Translated Set 2 keyboard: always reports core events
    [ 6.785] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 6.785] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 6.785] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 6.785] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 6.785] (**) Option "xkb_rules" "evdev"
    [ 6.785] (**) Option "xkb_model" "pc104"
    [ 6.785] (**) Option "xkb_layout" "us"
    [ 6.785] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.803] (EE)
    [ 6.803] (EE) Backtrace:
    [ 6.803] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x132) [0x81df9e2]
    [ 6.804] (EE) 1: ? (?+0x132) [0xb7787cc5]
    [ 6.804] (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x4cd7) [0xb6e2a1c7]
    [ 6.806] (EE) 3: /usr/lib/xorg-server/Xorg (xf86_show_cursors+0x688) [0x80f9008]
    [ 6.806] (EE) 4: /usr/lib/xorg-server/Xorg (xf86DestroyCursorInfoRec+0xcf8) [0x8103fc8]
    [ 6.806] (EE) 5: /usr/lib/xorg-server/Xorg (RamDacHandleColormaps+0x67b) [0x810218b]
    [ 6.807] (EE) 6: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x25d) [0x81c648d]
    [ 6.808] (EE) 7: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x4c1) [0x81c6b31]
    [ 6.808] (EE) 8: /usr/lib/xorg-server/Xorg (CompositeRegisterImplicitRedirectionException+0x4199) [0x8114399]
    [ 6.809] (EE) 9: /usr/lib/xorg-server/Xorg (PanoramiXRenderReset+0x72a) [0x815915a]
    [ 6.810] (EE) 10: /usr/lib/xorg-server/Xorg (ConfineToShape+0x9f1) [0x80843b1]
    [ 6.810] (EE) 11: /usr/lib/xorg-server/Xorg (WindowHasNewCursor+0x3b) [0x8084f2b]
    [ 6.810] (EE) 12: /usr/lib/xorg-server/Xorg (ChangeWindowAttributes+0xb7c) [0x80aa9ec]
    [ 6.811] (EE) 13: /usr/lib/xorg-server/Xorg (ProcBadRequest+0x209) [0x8074a49]
    [ 6.811] (EE) 14: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x3a6) [0x807abf6]
    [ 6.811] (EE) 15: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x42f) [0x807edaf]
    [ 6.811] (EE) 16: /usr/lib/xorg-server/Xorg (miPolyFillRect+0x27f) [0x8068ddf]
    [ 6.814] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xde) [0xb72d864e]
    [ 6.814] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x21) [0x8068bd9]
    [ 6.814] (EE)
    [ 6.814] (EE) Segmentation fault at address 0x0
    [ 6.814] (EE)
    Fatal server error:
    [ 6.814] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 6.814] (EE)
    [ 6.814] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 6.814] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 6.814] (EE)
    [ 6.815] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 6.817] (EE) Server terminated with error (1). Closing log file.
    Note the segfault in modesetting_drv.so!
    Any help?
    I tried to reinstall dependencies of xorg-server and mesa. And then I even went through with the whole system update which I postponed for a few weeks because of the KDE changes. Sadly even the whole system update didn't help.
    Is it possible that any old config files can cause this?
    EDIT:
    I tried kernel parameter "nouveau.modeset=0" but it didn't help.
    Last edited by cro (2015-02-26 16:33:19)

    Ok, I guess I solved it by reinstalling xf86-video-nouveau.
    Funny business! Why did the upgrade to xorg-server 1.17.1 force me to remove it when it is still needed??
    And why does that lead to mysterious error messages and segfault??
    I discovered it accidentally when I stumbled upon the fact that the package was still installed on my newer x86-64 Arch installation despite being on xorg-server 1.17.1.

  • Getting "sync session failed to start" message when trying to sync iPad to Mac

    When i connect ipad to Mac and click on sync, which it has been doing automatically, now it doesn't and i click sync and get message "sync session failed to start".  Any suggestions?  Thank you.

    Keep the connection, quit iTunes totally and re-start iTunes again.

  • When I try to sync my Ipad Mini, I get an error message that says "sync session failed to start".  Anyone ever deal with this?

    When I try to sync my Ipad Mini, I get an error message that says "sync session failed to start".  Anyone ever deal with this?

    Quit iTunes, restart your computer, restart your iPad and try again. If it doesn't work with a restart of the iPad, try a reset of the iPad.
    Reset the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.

  • Session failed to start - after updating to IOS 7

    I've updated to my iphone 4 to IOS 7 and now it won't sync with itunes.  Its says "session failed to start".  Help!

    On the advice I got from others, here's what I finally did:
    1.  I connected my iPhone to my PC and backed it up to iTunes.  Even though the phone doesn't sync, it will still back up and it did. 
    2.  I then went in to settings on my iPhone under "Reset" and did the "Erase All Content and Settings", while still leaving my iPhone connected to my computer.
    3.  Once the phone booted back up, iTunes asked me if I wanted to restore my phone from back up.  I chose restore and it restored my phone back and it is now working 100%.  I'll add that it froze up during the restore process and I simply rebooted my PC and the ran sync and it finally worked.  Took forever for my apps to all load back (couple of hours), but its fixed and working great.
    I cannot tell you how upset I am with Apple.  Many of us have this same issue and Apple has done nothing to help us or fix it.  I've wasted 12 hours of my life on something that should have been simple and seamless.  Isn't that the point of Apple and iPhones? 

  • [SOLVED]Compiz Fusion doesn't start!

    Hello,
    After an upgrade Compiz Fusion doesn't start. Normally I start Compiz Fusion with the command:
    fusion-icon
    But now it gives on a terminal the following output:
    fusion-icon
    * Detected Session: gnome
    * execution of "which glxinfo" failed
    * Error: glxinfo not installed!
    I searched with Yaourt on "glxinfo", but there is no package called "glxinfo".
    Could someone help?
    Jozef
    Last edited by jozef00 (2009-05-11 16:01:39)

    Hello,
    The problem is solved. Instead of
    fusion-icon
    I use
    compiz-manager
    Thanks to xaiviax for his reply.
    Jozef

  • After installation of Solaris 10  - CDE login doesn't start

    I have installed Solaris 10 on Sparc Machine but the CDE login doesn't start .
    I received the message :
    Suspendind Desktop Login...
    If currently logged out, press [enter] for a console login promt.
    desktop Login will resume shortly after you exit console session.
    In the file /var/dt/Xerrors I have :
    fbconsole: ioctl SRIOCSREDIR: Device busy
    ioctl(MSIOSRESOLUTION): Invalid argument
    ddxSUNWmouse: couldn't set absolute mouse scaling resolution on /dev/mouse
    Tue Sep 12 11:54:15 2006
    error (pid 2490): Can not lock pid file /var/dt/Xpid, another Dtlogin is running (pid 873)
    I set the resolution of monitor for one supported :
    fbconfig -res 1280x1024x60
    But always I obtain the same thing,
    Can someone help me ?
    May thanks in advance,
    Luz

    I don't know if it helps. But I had problems with the x-server not starting (didn't even get a gui login just command line) re-setting the network properties seemed to fix it, looks like anything dodgy in the network config stuffs up the start up proceedure.

  • Gnome-settings-daemon sometimes doesn't start

    Hey guys. I have an occasional problem where the gnome-settings-daemon doesn't start on login. If I log out and then back in it usually starts. Or, I can run it by hand and everything works fine. It's not a big deal, but it's a little annoying. Has anybody run into this or does anybody know of a log file or something I can check to see why it doesn't come up?
    Thanks
    -mS
    Last edited by aglarond (2009-01-25 01:01:02)

    I had this problem, and I have a very fresh arch install; no old homedir, and gnome was installed at version 2.24.1 (current).
    However the problem seems to have gone away once I cleared out the files in my $HOME/.config/autostart/
    That directory had some .desktop files, including gnome-settings-daemon-helper.desktop (but not gnome-settings-daemon.desktop!).
    Actually I find it weird that gnome-settings-daemon.desktop resides (on my system) in /etc/xdg/autostart, whereas gnome-settings-daemon-helper.desktop is in /usr/share/gnome/autostart/.
    I'm not sure what the significance of any of this is, or if my entire experience (rm ~/.config/autostart/*) even makes sense. But see if it works for you
    Edit: Nevermind, I still have this problem happen sporadically; the above solved nothing, it seems
    Any ideas how we can debug this? How can I trace exactly what gnome-session is doing?
    Last edited by infohigh (2009-01-29 05:26:16)

  • Session "" failed to start with the following error: 0xc0000022

    Newly installed Windows 2012 R2 server throws the following event roughly every 3 minutes:
    Session "" failed to start with the following error: 0xc0000022
    The PID referenced in the event points to WmiPrvSE.exe running as NETWORK SERVICE.  Is there something obvious I'm missing because I'm not sure where to go with the information I found so far.  I already did my fair sharing of Binggling and everything
    I find doesn't apply or doesn't fix the problem.

    Hi,
    Can you let me know the full event log content?
    I suggest you restart the Windows Management Instrumentation service.
    Niki Han
    TechNet Community Support

  • Multicast sessions page of server properties

    I am using ZEN 4.0.1 ir7, Netware 6.5sp4, ConsoleOne 1.3.6e.
    I was creating multicast sessions on the multicast sessions page of server
    properties for later use by my technician. I had created 5 sessions, then
    closed the property page. Then later I went back to make changes on one of
    the sessions. When I attempt to open that tab I get the message 'Loading,
    one moment please...', and there it stays. I have to kill the ConsoleOne
    process in task manager and restart ConsoleOne in order to do anything.
    What's going on, and how do I correct it?

    Thanks guys. I started c1 without the zen snapins, then deleted one of the
    sessions from the 'other' tab. Then I put the zen snapins back in and was
    able to view the rest of the multicast sessions. Kind of screws up the
    linkages in edir doing it that way, but that's fixable.
    >>> Kurt Finlayson<[email protected]> 11/5/2006 9:03:10 PM >>>
    >Bill Knaack wrote:
    >> I am using ZEN 4.0.1 ir7, Netware 6.5sp4, ConsoleOne 1.3.6e.
    >>
    >> I was creating multicast sessions on the multicast sessions page of
    >server
    >> properties for later use by my technician. I had created 5 sessions,
    >then
    >> closed the property page. Then later I went back to make changes on one
    >of
    >> the sessions. When I attempt to open that tab I get the message
    >'Loading,
    >> one moment please...', and there it stays. I have to kill the ConsoleOne
    >> process in task manager and restart ConsoleOne in order to do anything.
    >> What's going on, and how do I correct it?
    >>
    >
    >This sounds familiar. I think this is fixed in a newer version of
    >ZENworks but not in ZfD 4.x. You could try a consoleOne containing newer
    >snapins of ZDM 6.5 or 7 and see what happens? Just a thought.

  • ERROR: "The iPhone could not be synced because the sync session failed to start.?"

    I have iTunes 10.5 (whatever the most updated is) with the new iPhone 4S. Its new, i never dropped it, and i'm 99.99999% confident there's nothing wrong with it.
    With that in mind, these last few days this strange error, "the iphone could not be synced because the sync session failed to start"... It used to sync properly but now it just doesn't sync at all.
    I have Windows Vista also. This is not normal and i've never seen this before.
    What can I do to fix this error?

    The way I fixed this (though I'm using a iTouch 4G): disconnect your iPhone from the computer, shut down iTunes, then reset your iPhone by holding the Power/Sleep & Home buttons together for 10 seconds. Restart iTunes, then when your iPhone restarts, reconnect it to the computer, and everything should work fine

  • Gnome 3 doesn't start = gnome-shell crashes

    Well guys, I've been playing around with arch for a while, and now I have decided to test GNOME 3 by myself. So I installed gnome and gnome-extra packages, started gdm, logged into my user and... Nothing. GDM takes forever to start the session and... Well, it doesn't start the session at all. So I thought I could open gnome in the same way I open my openbox session, so I changed my exec ck-launch-session openbox-session in .xinitrc to exec ck-launch-session gnome-session.
    I run startx and... Nothing! Well, it loads the wallpaper, and then the screen goes black and it says it couldn't load the session, asks me to try again.
    So I realized I'd have to test some things. Well, running gnome-shell and metacity from console just shut down the X server!
    And yes, I've searched in the forums, but the solutions I found didn't work for me. If you want me to post a log, or the packages installed... I dunno.
    I wasn't using the testing repos when the error start. I upgraded and the error is still the same.
    Guys, I just want to test this freak!
    Sorry for my bad english, and thank you already

    can you post ~/.xsession-errors after you login via GDM?

  • Error event id 2 - Kernel Event Tracing - Session "" failed to start with the following error: 0xC000000D

    I keep getting this strange error logged as Error event id 2. Note session string is blank "". Any ideas?
    Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
    Source:        Microsoft-Windows-Kernel-EventTracing
    Date:          24/12/2009 09:08:20
    Event ID:      2
    Task Category: Session
    Level:         Error
    Keywords:      Session
    User:          SYSTEM
    Computer:      George-XXL
    Description:
    Session "" failed to start with the following error: 0xC000000D
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
        <EventID>2</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>2</Task>
        <Opcode>12</Opcode>
        <Keywords>0x8000000000000010</Keywords>
        <TimeCreated SystemTime="2009-12-24T09:08:20.835299100Z" />
        <EventRecordID>36</EventRecordID>
        <Correlation />
        <Execution ProcessID="1944" ThreadID="1948" />
        <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
        <Computer>George-XXL</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="SessionName">
        </Data>
        <Data Name="FileName">
        </Data>
        <Data Name="ErrorCode">3221225485</Data>
        <Data Name="LoggingMode">5</Data>
      </EventData>
    </Event>

    Can you let us know if you get any Blue Screen crush error while using your comptuer?
    Generally we can safely ignore the errors in the Event log. Aas we don't if you have get other issues in your computer, you can test your computer in the Clean Boot mode. This method will help us determine if this issue is caused by a loading program or service.
    You can try the the following steps:
    1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.
    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
    3. Click the "Startup" tab, click "Disable All" and click "OK".
    Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.
    Please test this issue in this Clean Boot environment, if the issue disappears in the Clean Boot environment, you can use the dichtomy to quickly narrow down which entry is causing the issue. You can refer to the
    KB929135.
    Good luck!
    John
    This is a very poor answer.  This guy doesn't know what he's talking about because if you tell someone its ok to  "safely ignore the errors in the event log"  as a blanket instruction ESPECIALLY because as he stated so himself
    he didn't know if there were other issues with the OP's pc then he's giving really bad advice. If you ignore errors in the event log then over time your system will degrade and you will have other issues.. Every error on your pc should NOT be ignored.
    It should be decided on a case by case situation.
    Furthermore this is an error involving the Windows Session which it states has failed. Definitely should NOT be ignored.
    I've got the same error which has suddenly just showed up. No BSOD, Do not have WHS installed and all my media center connectors have NEVER been connected. I don't believe this is a service issue. I think it has something
    to do with kernel event tracing.
    Of course, it's just my opinion....I could be wrong!

Maybe you are looking for

  • I am having a weird problem while attempting to re-install iTunes, is there anyone who can help?

    Its kind of an odd problem, never happened to me before, but my old iTunes was very outdated because my updater was not working, and today having to actually use iTunes but it was very outdated, I read on the apple support site that the only way to u

  • Round trip to Photoshop

    After I have perfected an image in Aperture and I wish to do more work on it in Photoshop I use the export to external editor command. Once the changes are made I save back in Aperture. The reimported image prints differently. Do I have to assure tha

  • Use of minimum order value condtion AMIZ and AMIW

    I am using the above standard SAP conditions to calculate a minimum order value. It is working fine for an order with a single order item but for multi-item orders it is only doing the calcualtion for the last item.  As per standard SAP i have AMIW d

  • Sqldeveloper does not work under "xgl"

    Hi, I just installed "xgl" on my linux desktop and try to run "sqldeveloper". It starts as usual and open main window, but this window is empty ( no menus and other GUI ). sqldeveloper works fine when I restart my desktop with regular "xorg" server i

  • Alternate Develop Settings

    One thing I really liked in RSP and miss in LR was the ability to set multiple "develop" settings for a single image. What happens is that sometimes I may be heading down a certain path in the way I am adjusting my settings for an image, when suddenl