Webelements : Hide crystal parameter screen when using webelements screen
hi Masters,
i have made a very good progress on Using Web Elements from SAP as data source.
my WEBELEMENTS are working when i connect to SAP as data source...i am able to pass values.
i have a concern here at this point.
1. when i use webelemnts as selection screen and when i submit it still ask for the parameters on Crystal parameter screen
2. i dont want the crystal parameter screen bcoz i am already using the Webelements
3. how can i hide that Crystal screen?
look forward to your solutions,
thank you,
pasala.
hi pasala,
firstly, you must ensure that you use opendocument syntax and not the viewrpt (older url reporting) syntax as webelements only work with opendocument. please see the webElements Submit Methods report that is included in the main download [here |Crystal Reports webElements]. you can publish these samples to your enterprise system to see their behaviour.
as mentioned before, there are also problems with the SAP integration kit depending on what version you have.
another of them is that even if you pass a report a complete opendocument url, you will still get prompted by the sap integration kit's parameter screen...this is a bug that i've seen before. if you create a proper opendocument url using the method i described before, and paste it into a browser, and the url is intercepted by the SAP integration kit prompt / parameter screen, then there is an issue. you can try to install the latest integration kit on a test bed to see if that helps. if it doesn't help, then i would advise you to contact Customer Assurance.
if you are successfully able to paste an opendocument url into a browser and bring up the report then see the options below.
Option A
1 create an opendocument url that will target the report that has webelements on it
2 ensure that this new url will have a value for every parameter on it as a default...if you don't have a value for each parameter on the url then you will get prompted
3 publish this url to your infoview system or distribute the url to anyone that accesses the report
as an example paste this url into your browser...the url has an "lsS" parameter on it for a parameter named "HighlightBoat"...
http://experience.sap.com/OpenDocument/opendoc/5O5SSO.jsp?&docid=140166&&drilldowntabs=hide&sReportMode=weblayout&toolbar=hide&lsSHighlightBoat=AUS%208801
4 use the method mentioned before to create the hyperlink
Option B
1 create a separate report that has only webelements on it...you can use this new report as a parameter page
2 have this new report published to your enteprise system with Saved Data
3 in this new parameter report, have your submit button target a New Window when the submit button is pressed
this option "b" will also help you avoid being prompted.
i hope this helps,
jamie
Similar Messages
-
Completely White screen when using green screen
I have successfully used the Green Screen feature in the past but I am having some problems with it now. When I drop a Green Screen clip onto a back ground the play back shows no image and the screen is completely white. What is happening and how do I correct it?
Many thanks for this - I had checked them previously, but switched off, unplugged everything and then reconnected - all up and working again. Best Rgds
-
How to blank laptop screen when using external monitor/
Hi there
I need some help with figuring out how to configure my xorg.conf for my Arch Linux 64 bit installation on a HP Pavilion dv 5000 laptop so that I can automatically blank my laptop screen when using an external monitor. I have Arch Linux installed along with Ubuntu Feisty. In Ubuntu my external monitor (Viewsonic 1912WB) was not detected at the time of installation but with the native 1280X800 resolution that is good for the laptop takes effect for the external monitor automatically when the external monitor is plugged in. The laptop monitor goes blank when the external monitor is plugged in.
In my Arch Linux installation I have not been able to configure a dual head configuration using the ATI Radeon drivers (fglrx). I have the native 1280X800 resolution set up for the laptop monitor and this resolution takes effect for the external monitor also. However the laptop monitor also continues to function when the external monitor is plugged in. I would like to blank the laptop monitor when using the external monitor.
I am attaching my Arch Linux xorg.conf and the Ubuntu xorg.conf below. Thanks for anyone who can help, I am having a lot of difficulty in figuring out how to set up xorg.conf among all the things that I have had to learn so far in Linux and I am a relative newcomer to the whole thing. I have tried to compare the two xorg.conf files and edit my Arch xorg.conf in accordance with the Ubuntu one but it did not work and I keep getting errors!
I am using XFCE as my Desktop environment.
Arch Linux xorg.conf
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
EndSection
Section "InputDevice"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
# Identifier and driver
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 30.0 - 62.0
VertRefresh 50.0 - 70.0
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Identifier "* Generic VESA compatible"
Driver "vesa"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "* Generic VESA compatible"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Ubuntu xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "Device"
Identifier "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Driver "ati"
BusID "PCI:1:5:0"
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection
Section "DRI"
Mode 0666
EndSectionXrandr 1.2 provides means for this. But today the only supported configuration is xorg-server-1.3 + xf86-video-intel-2.0. So for Radeon you'll have to wait for drivers that support Randr 1.2.
On my laptop (Thinkpad x60s) that would be:
xrandr --output VGA --auto
xrandr --output LVDS --off -
Using just the TV screen when using HDMI port?
Hi,
I have the Macbook Pro with retina display and I was wondering how I could use just the TV screen when using HDMI port. I don't want mirroring displays, just one on the TV.With the TV connected and the MBP plugged into the mains (i.e. not running on battery power) close the lid. The MBP will go to sleep, wake it up with an external keyboard or mouse - which must be connected in advance, or paired in advance if a bluetooth keyboard/mouse.
-
The settings box is always in the middle of my screen when using Flash Player , Won't close ?
See:How do I do a clean install of Flash Player?
It should work ok after that. -
2012 macbook pro retina display artifacts on screen when using onboard video
2012 Macbook Pro Retina Display artifacts on screen when using onboard video.
About a month ago I've noticed these strange artifacts (blocky pixelated looking) running vertically down the screen. It first started when using Safari. Then it started to happen all the time. I turned off the auto switch video in preferences, which I'm assuming forces the computer to use the separate video card and the artifacts go away.
On top of that issue I also have had the ghosting issue.
Anyone else have this problem?artifacts onscreen could mean a faulty gpu. You said by forcing it on inbuilt gpu you do not find this issue highlights that. Do take it in to apple for service and also tell them of your ghosting issue.
There are a few retina owners who have faulty gpus. -
How does one get a full screen when using air play on my tv when I'm mirroring,.? Thanks in advance
The iPad's display is 4:3, so it cannot fill your TV screen, which is 16:9
The only way is to change your TV settings and stretch the image. -
I want to remove or hide the Details Panel. when using OpenDoc.
Hello I'm Yong ho Park.
I recently had hard time because of Details Panel.
I want to remove or hide the Details Panel. when using OpenDoc(Dashboard file).
My system's version is BI 4.1 SP02.
Is your problem solved??
If your problem isn't solved, I want to be offered related formation.
I need your help. !!Hi,
you cant hide the Details Panel. This behaviour is By Design.
http://service.sap.com/sap/support/notes/2021076
Regards
-Seb. -
Thin flickering white line at the very top of screen when using mail
using an imac 27 inch, new...
there is a thin flickering white line at the very top of screen when using mail.
usually when sending a mail or when the cursor moves over a link ( in apple mail )
the flickering line is just under the very top menu bar which has the date on etc...
anyone else had this or know how to fix it?
cheersI am facing the same problem. In fact mac book pro 13 retina was in the 14 day period so I got it retuned today, after directions from the apple telephone support. However, the new machine I got in exchange has the same problem or flickering line under the menu tab.
The only relief it seems is the fact that it's not a hardware problem probably. I also think so because if I do a full screen which essentially means there is no menu bar, then there is no flickering white line.
Hope apple fixes this. Sad to notice this drop in apple quality, and yet not fixed. -
Blue Screen When using Magic Bullet Instant HD in Premiere Pro CC
When using Adobe Premiere Pro CC, using Magic Bullet Instant HD to convert a 720p video to a 1080p. The system will blue screen and the problem dll file seems to be hal.dll.
What is the cause of this?
and how to fix it?
System Specs:
OS: Win 7 Ultimate 64 bit
CPU: i7 3770k 3.5 Ghz
RAM: 16 GB
GRAPHICS: AMD Radeon HD 7700
MOTHERBOARD: ASRock Z77 Extreme6
STORAGE: 1 TB local disk, 3 2TB Expanded driver attached to 3.0 port
Wireless mouse and keyboardHi Kris,
I have checked all the three dumps, they all showed the same bugcheck 124.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8010821028, be200000, 21136}
Probably caused by : GenuineIntel
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010821028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Adobe Premiere
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
fffff880`0350ab58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`10821028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0350ab60 fffff800`035d6463 : 00000000`00000001 fffffa80`10817950 00000000`00000000 fffffa80`108179a0 : hal!HalBugCheckSystem+0x1e3
fffff880`0350aba0 fffff800`03413700 : 00000000`00000728 fffffa80`10817950 fffff880`0350af30 fffff880`0350af00 : nt!WheaReportHwError+0x263
fffff880`0350ac00 fffff800`03413052 : fffffa80`10817950 fffff880`0350af30 fffffa80`10817950 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0350ad50 fffff800`03412f0d : 00000000`00000008 00000000`00000001 fffff880`0350afb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0350ad90 fffff800`03406e88 : 000007ff`fda7f140 00000000`00000b40 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0350adc0 fffff800`034be4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0350adf0 fffff800`034be313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0350af30 00000000`0352f2c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`36c0cdd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x352f2c9
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
Information for Bugcheck 124:
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR.
Bugcheck 124, This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Which is probably caused by "GenuineIntel". Make sure we have updated the BIOS drivers, take a check with the hardware tool provided by the manufacturer, or you may take a check with them.
Best regards
Michael Shao
TechNet Community Support -
Why does my dock get stuck when using full screen apps?
When using a full screen app like Safari, if I go back to my desktop and to the dock (which i keep minimized) it stays there when going back to the full screen app. I have to go back to the first page and hover over the dock to get it to go back. Not sure whats going on...
I may not have explained exactly...so basically when i go to the main desktop screen, and open a program or use the dock, it sometimes gets stuck in show mode. Then when i go back to the safari full screen app for instance, the dock stays up, with the latest program highlighted. In order to get the dock to go away, i need to go back to the desktop and hover over the dock again for it to hide.
I really hope someone else is experiencing this because its very annoying and I want apple to fix it quickly -
"Server Busy" error in Crystal Reports XI when using date picker
Hi,
I have come across an issue whereby I get a error pop up when using the date picker to select a date parameter as I run a report from within Crystal Report XI on a particular PC. While I am able to type in the date using the yyyy-mm-dd format, selecting the date picker displays an error message titled "Server Error" stating that the program is not responding and giving options "Switch To" and "Retry". Selecting either button displays the same error message and need to kill the application from the Task Manager to restart.
I have run the same report from other PCs (including using the date picker to pick a date parameter) without the error popping up. All of the PCs have the same version of the application.
Has anyone come across this and how were you able to resolve it?yes test is a formula that i used to calculate a difference
that should work, but i would put () around the
(if(remainder(({ztrptActVol.CPT}*{tlkpBblMileage.CPT}),1)>0 and
remainder(({ztrptActVol.CPT}*{tlkpBblMileage.CPT}),1)<1) then
truncate(({ztrptActVol.CPT}*{tlkpBblMileage.CPT}))+1
else ({ztrptActVol.CPT}*{tlkpBblMileage.CPT})
rounding in crystal is a pain in the && -
How can I make iPhone 4S Video's fill the screen when using them in iMovie 11 on My MacBook Pro
Hey Guys.
I am a singer songwriter from he UK.... I recently bought an Iphone4s, Ipad and Mac book pro (haha, apple hero, I know). I have always wanted to make the big jump to apple, just was waiting a little while.
I am thrilled so far, it's all great. But, I use Imovie (i am still getting to grips with it, but the features are amazing) to make videos of me singing coversand original videos for youtube.
The Camera on the iphone4s is great.
But, when I import videos into Imovie11, the videos do not fill the screen in their original form.
In some videos, I use the Ken Burns effect. Now, on the parts of my video when I use this effect, it fills the screen as it should do.
Why do the videos in their untampered form not do this? I have tried importing widescreen, original size, and Large, but it alwys sits in the middle of the screen, fairly thin lookin. It fills the screen when it's on my Iphone, I am very lost.
plesse help.
thanks.if i can offer any more info please just ask
-
[SOLVED]Xorg crash with some applications when using double screen
Hi,
I have a TV that I often use to watch dvd from my computer, and to do that I've set it up as a second screen in my xorg.conf, but on a daily basis I use a xorg.conf file with only my main screen. Up until last week I was able to use my second screen without problem, but yesterday I tried and it crashed instantly.
So I ran a few tests, amsn and vlc seems to be 2 applications that makes X crash (though there might be other, but I seem to be able to use chromium firefox and ktorrent just fine).
My WM is not to blame, I've launched X without any WM and vlc still makes X crash.
The problem does not happen when using a single screen.
I thought that my xorg.conf might be the problem, so I used nvidia-settings to create a new one, but that didn't change anything.
Here are my xorg.conf used for dual screen, and the logfile from the Xorg crash:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder62) Wed May 27 01:58:49 PDT 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection
Section "Files"
EndSection
Section "ServerFlags"
Option "Xinerama" "1"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "fr"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Lite-On e1770NSL/T"
HorizSync 30.0 - 70.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "CRT-1"
HorizSync 31.5 - 64.0
VertRefresh 56.0 - 75.0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8800 GT"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8800 GT"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT-0: 1280x1024 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "CRT-1: 1360x768 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
[ 12049.854]
X.Org X Server 1.9.0
Release Date: 2010-08-20
[ 12049.855] X Protocol Version 11, Revision 0
[ 12049.855] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 12049.855] Current Operating System: Linux Arch 2.6.35-ARCH #1 SMP PREEMPT Wed Sep 29 08:45:18 CEST 2010 x86_64
[ 12049.855] Kernel command line: root=/dev/disk/by-uuid/132b76f3-06e9-4838-944f-43ac4deccebb ro
[ 12049.855] Build Date: 24 August 2010 01:44:37PM
[ 12049.855]
[ 12049.855] Current version of pixman: 0.18.4
[ 12049.856] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 12049.856] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 12049.856] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 5 17:25:50 2010
[ 12049.857] (==) Using config file: "/etc/X11/xorg.conf"
[ 12049.857] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 12049.857] (==) ServerLayout "Layout0"
[ 12049.857] (**) |-->Screen "Screen0" (0)
[ 12049.857] (**) | |-->Monitor "Monitor0"
[ 12049.857] (**) | |-->Device "Device0"
[ 12049.857] (**) |-->Screen "Screen1" (1)
[ 12049.857] (**) | |-->Monitor "Monitor1"
[ 12049.857] (**) | |-->Device "Device1"
[ 12049.857] (**) |-->Input Device "Keyboard0"
[ 12049.857] (**) |-->Input Device "Mouse0"
[ 12049.857] (**) Option "Xinerama" "1"
[ 12049.857] (==) Automatically adding devices
[ 12049.857] (==) Automatically enabling devices
[ 12049.857] (**) Xinerama: enabled
[ 12049.857] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 12049.857] Entry deleted from font path.
[ 12049.857] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 12049.857] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 12049.857] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 12049.857] (WW) Disabling Keyboard0
[ 12049.857] (WW) Disabling Mouse0
[ 12049.857] (II) Loader magic: 0x7d4880
[ 12049.857] (II) Module ABI versions:
[ 12049.857] X.Org ANSI C Emulation: 0.4
[ 12049.857] X.Org Video Driver: 8.0
[ 12049.857] X.Org XInput driver : 11.0
[ 12049.857] X.Org Server Extension : 4.0
[ 12049.858] (--) PCI:*(0:1:0:0) 10de:0611:1462:1170 rev 162, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
[ 12049.858] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 12049.858] (II) LoadModule: "extmod"
[ 12049.858] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 12049.858] (II) Module extmod: vendor="X.Org Foundation"
[ 12049.858] compiled for 1.9.0, module version = 1.0.0
[ 12049.858] Module class: X.Org Server Extension
[ 12049.858] ABI class: X.Org Server Extension, version 4.0
[ 12049.858] (II) Loading extension MIT-SCREEN-SAVER
[ 12049.858] (II) Loading extension XFree86-VidModeExtension
[ 12049.858] (II) Loading extension XFree86-DGA
[ 12049.858] (II) Loading extension DPMS
[ 12049.858] (II) Loading extension XVideo
[ 12049.858] (II) Loading extension XVideo-MotionCompensation
[ 12049.858] (II) Loading extension X-Resource
[ 12049.858] (II) LoadModule: "dbe"
[ 12049.859] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 12049.859] (II) Module dbe: vendor="X.Org Foundation"
[ 12049.859] compiled for 1.9.0, module version = 1.0.0
[ 12049.859] Module class: X.Org Server Extension
[ 12049.859] ABI class: X.Org Server Extension, version 4.0
[ 12049.859] (II) Loading extension DOUBLE-BUFFER
[ 12049.859] (II) LoadModule: "glx"
[ 12049.859] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 12049.866] (II) Module glx: vendor="NVIDIA Corporation"
[ 12049.867] compiled for 4.0.2, module version = 1.0.0
[ 12049.867] Module class: X.Org Server Extension
[ 12049.867] (II) NVIDIA GLX Module 256.53 Fri Aug 27 20:50:26 PDT 2010
[ 12049.867] (II) Loading extension GLX
[ 12049.867] (II) LoadModule: "record"
[ 12049.867] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 12049.867] (II) Module record: vendor="X.Org Foundation"
[ 12049.867] compiled for 1.9.0, module version = 1.13.0
[ 12049.867] Module class: X.Org Server Extension
[ 12049.867] ABI class: X.Org Server Extension, version 4.0
[ 12049.867] (II) Loading extension RECORD
[ 12049.867] (II) LoadModule: "dri"
[ 12049.867] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 12049.867] (II) Module dri: vendor="X.Org Foundation"
[ 12049.867] compiled for 1.9.0, module version = 1.0.0
[ 12049.867] ABI class: X.Org Server Extension, version 4.0
[ 12049.867] (II) Loading extension XFree86-DRI
[ 12049.867] (II) LoadModule: "dri2"
[ 12049.867] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 12049.867] (II) Module dri2: vendor="X.Org Foundation"
[ 12049.867] compiled for 1.9.0, module version = 1.2.0
[ 12049.867] ABI class: X.Org Server Extension, version 4.0
[ 12049.867] (II) Loading extension DRI2
[ 12049.867] (II) LoadModule: "nvidia"
[ 12049.867] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12049.868] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 12049.868] compiled for 4.0.2, module version = 1.0.0
[ 12049.868] Module class: X.Org Video Driver
[ 12049.868] (II) NVIDIA dlloader X Driver 256.53 Fri Aug 27 20:29:45 PDT 2010
[ 12049.868] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 12049.868] (--) using VT number 7
[ 12049.869] (II) Loading sub module "fb"
[ 12049.869] (II) LoadModule: "fb"
[ 12049.869] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12049.870] (II) Module fb: vendor="X.Org Foundation"
[ 12049.870] compiled for 1.9.0, module version = 1.0.0
[ 12049.870] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12049.870] (II) Loading sub module "wfb"
[ 12049.870] (II) LoadModule: "wfb"
[ 12049.870] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12049.870] (II) Module wfb: vendor="X.Org Foundation"
[ 12049.870] compiled for 1.9.0, module version = 1.0.0
[ 12049.870] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12049.870] (II) Loading sub module "ramdac"
[ 12049.870] (II) LoadModule: "ramdac"
[ 12049.870] (II) Module "ramdac" already built-in
[ 12049.870] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 12049.870] (==) NVIDIA(0): RGB weight 888
[ 12049.870] (==) NVIDIA(0): Default visual is TrueColor
[ 12049.870] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 12049.870] (**) NVIDIA(0): Option "TwinView" "0"
[ 12049.870] (**) NVIDIA(0): Option "MetaModes" "CRT-0: 1280x1024 +0+0"
[ 12049.870] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
[ 12049.870] (**) NVIDIA(0): Enabling RENDER acceleration
[ 12049.870] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 12049.870] (II) NVIDIA(0): enabled.
[ 12049.955] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-1
[ 12049.957] (II) NVIDIA(0): NVIDIA GPU GeForce 8800 GT (G92) at PCI:1:0:0 (GPU-0)
[ 12049.957] (--) NVIDIA(0): Memory: 524288 kBytes
[ 12049.957] (--) NVIDIA(0): VideoBIOS: 62.92.23.00.00
[ 12049.957] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 12049.957] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 12049.957] (--) NVIDIA(0): Connected display device(s) on GeForce 8800 GT at PCI:1:0:0:
[ 12049.957] (--) NVIDIA(0): Lite-On e1770NSL/T (CRT-0)
[ 12049.957] (--) NVIDIA(0): CRT-1
[ 12049.957] (--) NVIDIA(0): Lite-On e1770NSL/T (CRT-0): 400.0 MHz maximum pixel clock
[ 12049.957] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[ 12049.960] (II) NVIDIA(0): Display Device found referenced in MetaMode: CRT-0
[ 12049.967] (II) NVIDIA(0): Assigned Display Device: CRT-0
[ 12049.967] (II) NVIDIA(0): Validated modes:
[ 12049.967] (II) NVIDIA(0): "CRT-0:1280x1024+0+0"
[ 12049.967] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[ 12049.999] (--) NVIDIA(0): DPI set to (101, 108); computed from "UseEdidDpi" X config
[ 12049.999] (--) NVIDIA(0): option
[ 12049.999] (WW) NVIDIA(0): 32-bit ARGB GLX visuals are not currently supported with the
[ 12049.999] (WW) NVIDIA(0): Xinerama extension.
[ 12049.999] (WW) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
[ 12049.999] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
[ 12049.999] (==) NVIDIA(1): RGB weight 888
[ 12049.999] (==) NVIDIA(1): Default visual is TrueColor
[ 12049.999] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 12049.999] (**) NVIDIA(1): Option "TwinView" "0"
[ 12049.999] (**) NVIDIA(1): Option "MetaModes" "CRT-1: 1360x768 +0+0"
[ 12049.999] (**) NVIDIA(1): Enabling RENDER acceleration
[ 12049.999] (II) NVIDIA(1): NVIDIA GPU GeForce 8800 GT (G92) at PCI:1:0:0 (GPU-0)
[ 12049.999] (--) NVIDIA(1): Memory: 524288 kBytes
[ 12049.999] (--) NVIDIA(1): VideoBIOS: 62.92.23.00.00
[ 12049.999] (II) NVIDIA(1): Detected PCI Express Link width: 16X
[ 12049.999] (--) NVIDIA(1): Interlaced video modes are supported on this GPU
[ 12049.999] (--) NVIDIA(1): Connected display device(s) on GeForce 8800 GT at PCI:1:0:0:
[ 12049.999] (--) NVIDIA(1): Lite-On e1770NSL/T (CRT-0)
[ 12049.999] (--) NVIDIA(1): CRT-1
[ 12049.999] (--) NVIDIA(1): Lite-On e1770NSL/T (CRT-0): 400.0 MHz maximum pixel clock
[ 12049.999] (--) NVIDIA(1): CRT-1: 400.0 MHz maximum pixel clock
[ 12050.002] (II) NVIDIA(1): Display Device found referenced in MetaMode: CRT-1
[ 12050.006] (II) NVIDIA(1): Assigned Display Device: CRT-1
[ 12050.006] (WW) NVIDIA(1): No valid modes for "CRT-1:1360x768+0+0"; removing.
[ 12050.006] (WW) NVIDIA(1):
[ 12050.006] (WW) NVIDIA(1): Unable to validate any modes; falling back to the default mode
[ 12050.006] (WW) NVIDIA(1): "nvidia-auto-select".
[ 12050.006] (WW) NVIDIA(1):
[ 12050.006] (II) NVIDIA(1): Validated modes:
[ 12050.006] (II) NVIDIA(1): "nvidia-auto-select"
[ 12050.006] (II) NVIDIA(1): Virtual screen size determined to be 1024 x 768
[ 12050.009] (WW) NVIDIA(1): Unable to get display device CRT-1's EDID; cannot compute DPI
[ 12050.009] (WW) NVIDIA(1): from CRT-1's EDID.
[ 12050.009] (==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
[ 12050.009] (WW) NVIDIA(1): 32-bit ARGB GLX visuals are not currently supported with the
[ 12050.009] (WW) NVIDIA(1): Xinerama extension.
[ 12050.009] (WW) NVIDIA(1): Disabling 32-bit ARGB GLX visuals.
[ 12050.009] (--) Depth 24 pixmap format is 32 bpp
[ 12050.009] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 12050.010] (II) NVIDIA(0): Initialized GPU GART.
[ 12050.014] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 12050.014] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 12050.014] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 12050.014] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 12050.014] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 12050.014] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 12050.014] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 12050.014] (II) NVIDIA(0): Config Options in the README.
[ 12050.017] (II) NVIDIA(0): Setting mode "CRT-0:1280x1024+0+0"
[ 12050.049] (II) Loading extension NV-GLX
[ 12050.064] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 12050.071] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 12050.071] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 12050.071] (==) NVIDIA(0): Backing store disabled
[ 12050.071] (==) NVIDIA(0): Silken mouse enabled
[ 12050.085] (**) NVIDIA(0): DPMS enabled
[ 12050.085] (II) Loading extension NV-CONTROL
[ 12050.085] (II) Loading sub module "dri2"
[ 12050.085] (II) LoadModule: "dri2"
[ 12050.085] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 12050.085] (II) NVIDIA(0): [DRI2] Setup complete
[ 12050.085] (==) RandR enabled
[ 12050.086] (II) NVIDIA(1): Initialized GPU GART.
[ 12050.090] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 12050.090] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
[ 12050.090] (II) NVIDIA(1): configuration option may not be set correctly. When the
[ 12050.090] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
[ 12050.090] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
[ 12050.090] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
[ 12050.090] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
[ 12050.090] (II) NVIDIA(1): Config Options in the README.
[ 12050.090] (II) NVIDIA(1): Setting mode "nvidia-auto-select"
[ 12050.145] (II) NVIDIA(1): Initialized OpenGL Acceleration
[ 12050.149] (==) NVIDIA(1): Disabling shared memory pixmaps
[ 12050.149] (II) NVIDIA(1): Initialized X Rendering Acceleration
[ 12050.149] (==) NVIDIA(1): Backing store disabled
[ 12050.149] (==) NVIDIA(1): Silken mouse enabled
[ 12050.157] (==) NVIDIA(1): DPMS enabled
[ 12050.158] (II) Loading sub module "dri2"
[ 12050.158] (II) LoadModule: "dri2"
[ 12050.158] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 12050.158] (II) NVIDIA(1): [DRI2] Setup complete
[ 12050.158] (==) RandR enabled
[ 12050.158] (II) Initializing built-in extension Generic Event Extension
[ 12050.158] (II) Initializing built-in extension SHAPE
[ 12050.158] (II) Initializing built-in extension MIT-SHM
[ 12050.158] (II) Initializing built-in extension XInputExtension
[ 12050.158] (II) Initializing built-in extension XTEST
[ 12050.158] (II) Initializing built-in extension BIG-REQUESTS
[ 12050.158] (II) Initializing built-in extension SYNC
[ 12050.158] (II) Initializing built-in extension XKEYBOARD
[ 12050.158] (II) Initializing built-in extension XC-MISC
[ 12050.158] (II) Initializing built-in extension SECURITY
[ 12050.158] (II) Initializing built-in extension XINERAMA
[ 12050.158] (II) Initializing built-in extension XFIXES
[ 12050.158] (II) Initializing built-in extension RENDER
[ 12050.158] (II) Initializing built-in extension RANDR
[ 12050.158] (II) Initializing built-in extension COMPOSITE
[ 12050.158] (II) Initializing built-in extension DAMAGE
[ 12050.160] (II) Initializing extension GLX
[ 12050.367] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 12050.367] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 12050.367] (II) LoadModule: "evdev"
[ 12050.367] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 12050.367] (II) Module evdev: vendor="X.Org Foundation"
[ 12050.367] compiled for 1.9.0, module version = 2.5.0
[ 12050.367] Module class: X.Org XInput Driver
[ 12050.367] ABI class: X.Org XInput driver, version 11.0
[ 12050.367] (**) Power Button: always reports core events
[ 12050.367] (**) Power Button: Device: "/dev/input/event3"
[ 12050.375] (--) Power Button: Found keys
[ 12050.375] (II) Power Button: Configuring as keyboard
[ 12050.376] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 12050.376] (**) Option "xkb_rules" "evdev"
[ 12050.376] (**) Option "xkb_model" "evdev"
[ 12050.376] (**) Option "xkb_layout" "us"
[ 12050.399] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 12050.399] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 12050.399] (**) Power Button: always reports core events
[ 12050.399] (**) Power Button: Device: "/dev/input/event2"
[ 12050.415] (--) Power Button: Found keys
[ 12050.415] (II) Power Button: Configuring as keyboard
[ 12050.415] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 12050.415] (**) Option "xkb_rules" "evdev"
[ 12050.415] (**) Option "xkb_model" "evdev"
[ 12050.415] (**) Option "xkb_layout" "us"
[ 12050.416] (II) config/udev: Adding input device UVC Camera (046d:0802) (/dev/input/event4)
[ 12050.416] (**) UVC Camera (046d:0802): Applying InputClass "evdev keyboard catchall"
[ 12050.416] (**) UVC Camera (046d:0802): always reports core events
[ 12050.416] (**) UVC Camera (046d:0802): Device: "/dev/input/event4"
[ 12050.428] (--) UVC Camera (046d:0802): Found keys
[ 12050.428] (II) UVC Camera (046d:0802): Configuring as keyboard
[ 12050.428] (II) XINPUT: Adding extended input device "UVC Camera (046d:0802)" (type: KEYBOARD)
[ 12050.428] (**) Option "xkb_rules" "evdev"
[ 12050.428] (**) Option "xkb_model" "evdev"
[ 12050.428] (**) Option "xkb_layout" "us"
[ 12050.430] (II) config/udev: Adding input device Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) (/dev/input/event5)
[ 12050.431] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[ 12050.431] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): always reports core events
[ 12050.431] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Device: "/dev/input/event5"
[ 12050.442] (--) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Found 3 mouse buttons
[ 12050.442] (--) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Found scroll wheel(s)
[ 12050.442] (--) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Found relative axes
[ 12050.442] (--) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Found x and y relative axes
[ 12050.442] (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Configuring as mouse
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): YAxisMapping: buttons 4 and 5
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 12050.442] (II) XINPUT: Adding extended input device "Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)" (type: MOUSE)
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): (accel) keeping acceleration scheme 1
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): (accel) acceleration profile 0
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[ 12050.442] (**) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[ 12050.442] (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): initialized for relative axes.
[ 12050.442] (II) config/udev: Adding input device Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) (/dev/input/mouse0)
[ 12050.442] (II) No input driver/identifier specified (ignoring)
[ 12050.444] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 12050.444] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 12050.444] (**) AT Translated Set 2 keyboard: always reports core events
[ 12050.444] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 12050.458] (--) AT Translated Set 2 keyboard: Found keys
[ 12050.458] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 12050.458] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 12050.458] (**) Option "xkb_rules" "evdev"
[ 12050.458] (**) Option "xkb_model" "evdev"
[ 12050.458] (**) Option "xkb_layout" "us"
[ 12050.459] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
[ 12050.459] (II) No input driver/identifier specified (ignoring)
[ 12057.008]
Backtrace:
[ 12057.008] 0: X (xorg_backtrace+0x28) [0x49f558]
[ 12057.008] 1: X (0x400000+0x67939) [0x467939]
[ 12057.008] 2: /lib/libpthread.so.0 (0x7f6c851f4000+0xf1c0) [0x7f6c852031c0]
[ 12057.008] 3: X (0x400000+0x130355) [0x530355]
[ 12057.008] 4: X (0x400000+0x2a2e1) [0x42a2e1]
[ 12057.008] 5: X (0x400000+0x2123e) [0x42123e]
[ 12057.008] 6: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f6c84187c4d]
[ 12057.008] 7: X (0x400000+0x20de9) [0x420de9]
[ 12057.008] Segmentation fault at address 0x4
[ 12057.008]
Fatal server error:
[ 12057.008] Caught signal 11 (Segmentation fault). Server aborting
[ 12057.008]
[ 12057.008]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 12057.008] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 12057.008]
[ 12057.019] (II) Power Button: Close
[ 12057.019] (II) UnloadModule: "evdev"
[ 12057.032] (II) Power Button: Close
[ 12057.032] (II) UnloadModule: "evdev"
[ 12057.045] (II) UVC Camera (046d:0802): Close
[ 12057.045] (II) UnloadModule: "evdev"
[ 12057.069] (II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close
[ 12057.069] (II) UnloadModule: "evdev"
[ 12057.082] (II) AT Translated Set 2 keyboard: Close
[ 12057.082] (II) UnloadModule: "evdev"
Last edited by Azriel (2010-10-06 15:09:27)Sorry this doesn't really help with the Xinerama problem, but since you are using the nvidia driver, have you considered using Twinview instead? You could do composite stuff too with Twinview - last I knew, Xinerama had problems with things that want to use compositing. I don't know how your setup is but if you're not set on using Xinerama, it might be an option to consider.
-
Limited functionality in Win 8.1 Start Screen when using Server 2012 GPO
I'm testing Windows 8.1 EE with Server 2012 for a school where I need to configure a common layout that users are unable to change. So, I have configured a start layout and exported it via Powershell to the server and it works fine across my various test
user ids apart from a couple of things.
If I create tiles on the start screen which point to specific websites such as Scratch, they only work on the user I exported the start layout from - they don't appear on other user start screens under the same GPO. I can get round this by creating a desktop
shortcut in the GPO under User Config/Prefs/Win settings/shortcuts. It's a bit crude but it works so if there is a straightforward way of creating tiles that do this I'd prefer that..
The other challenge is getting a documents tile on the start screen. I'm using roaming profiles and folder redirection as pupils could log onto any machine and once again, I can set this up and export the start layout to the server but only the user whose
start screen I exported gets the documents folder on their start screen when the GPO is applied. The other users just get a blank space. I guess when I create the tile it's pointing to the specific users folder on the server which other users won't have access
to so it needs to pick up the specific username of whoever is logged on...
Any suggestions would be appreciated... ThanksHi,
Please make sure that the .xml file with the Start screen layout must be located on shared network storage that is available to the users’ computers when they sign in (the users must have Read-only access to the file). If the
file is not available at sign-in, the Start screen is not customized during the session, and the user can make changes to the Start screen.
After you use Group Policy to import a customized Start screen layout on a computer or in a domain, you can update the layout simply by replacing the .xml file that is specified in the Start Screen Layout policy settings.
To change the Start screen layout imported by Start Screen Layout policy settings
Customize the Start screen on your test computer the way that you want it to look for users.
Run the Export-StartLayout cmdlet, with the following format, to export the new Start screen layout to an .xml file that overwrites the original file:
export-startlayout –path <path><file name>.xml -as xml
That’s all you need to do. The next time the users sign in to their computers, the GPO will import the new Start screen layout.
Kate Li
TechNet Community Support
Maybe you are looking for
-
How do I bring music back from iPod to iTunes after upgrading my computer
Unfortunately, my computer have crashed totally and all my data, music, pictures disappeared up in the blue sky. Anyway, the computer is now reestablished with XP and iTunes. But how do I get all the music from my iPod back to my computer..?? Do I ha
-
MacBook Air fails to wake and reboots instead after upgrading to Mavericks
Hi, I've got a MacBook Air, 2011, 13', that has been working fine for a few years already. I upgraded to Mavericks two days ago and so far it has been working great except for one irritating issue - it keeps rebooting my system instead of waking up t
-
Finally, after 3 mb's, 2 psu's, 2 sets of ram and 2 cpu's - the system is up!
Hi all, After almost two months of waiting for rma'd replacement parts, my new NLE is finally up and running! As it turned out, it was the new processor that went bad - all along. But i feel i need to correct some of my incorrect assumptions in my pr
-
Can't Get Images to Line Up Horizontally Within Div
I'm making a Fluid Grid Layout webpage. The bottom div contains 4 square images in a horizontal line. In the mobile mode, I want these 4 images to remain in a horizontal line and shrink to fit. I tried Block - Display - Inline-Block and I tried Block
-
Batch transcode of image sequences? Watch Folder?
I didn't see mention of this in the "what's new" information for Compressor 4, but 2 features I was really hoping for were the ability to batch transcode image sequences (e.g. DPX seqs to proRes QTs for VFX dailies) and some kind of non-kludgy watch