Problem in Payslip Layout format

Hi All,
Our payslip format in ESS have been changed automatically. Half of of the page on right side of the Payslip have been truncated. the following are changes I found on the payslip
1. Font Size of the Payslip became larger
2. Layout of the payslip also become larger
Right side of the (25%) is getting truncated and is not getting displayed and even the scroll bar on the PDF is disabled.
Did anyone faced the same problem can help me
Regards
Ponnusamy

How did you solve this problem? Can you share with us?

Similar Messages

Payslip - problems in the layout

Hi all,
IN THE standard Indian Payslip layout the DEDUCTIONS amount appears one digit less than it should ...
For eg my deductions in the PAYSLIP is Rs 21,221.00 but it appears as Rs 2,122.10
What changes should I make in the Form editor PE51 to get the correct values??
kindly reply its very urgent
uday

Hi Ram,
In PE51 are u talking about Cumulations ID's ?cos there's no option for C Type as u have said..
There are entries like Symbols,Conversions,Rules,DSplits,Splits and Differences but there's no entry like Ctype ??
kindly help
Edited by: Udaya Kumar on Jan 9, 2008 8:43 AM

Problem with Excel output format

Hi Guys,
I am creating a report in XML Publisher (not standalone). I am facing some problems could anyone please help me to figure out the issues.
Is it possible to have all three output format (PDF, HTML & EXCEL) exact (same aligned) only by creating a single RTF Template? I am facing the problem with Excel output format the output format of excel is taking excels cell formatting.
Example Numeric fields --> Right Aligned, text fields --> Left Aligned
One more issue with excel is -ve(negative) values are getting displayed in red and in brackets like ($13) (with red color).
Our client want excel output on priority.
Is there any limitation for excel output format of reports?
It is very urgent for us please help.
Any help would be highly appreciated.
Thanks,
Pragati
Edited by: user11237443 on Aug 27, 2009 1:22 AM

Hi Mahi,
Thanks for your response. But i could not understand how can we write wrapper program could you please give some light on this or provide some link it would be helpful for me:-)
I have read that blog for excel limitations but i have more question?
1) What about the negative values?
if any field is displaying negative amount then excel not displaying right value for that:(
2)How can we align header or data?
Do XMLP with EBS provide any solution for formatting in excel?
3) If for the alignment of numeric value we concatenate them with any special character then how can we perform calculation that field?
Here are so many formatting issues do we need to write any code in xml for that?
Please help.
Many Thanks,
Pragati

So I have been creating a logo for my company and it came out great. The problem is, when I format it for PNG or when I want to use it on freshbooks or my webpage, the image becomes blurred and the text is not as clear. How do I fix this?

So I have been creating a logo for my company and it came out great. The problem is, when I format it for PNG or when I want to use it on fresh books or my webpage, the image becomes blurred and the text is not as clear. How do I fix this? Is it because the text get shrunk?

This is how it looks on adobe illustrator

I am unable to print a proper playlist in the jewel case format. Lines print on top of one another. No problem with other print formats

I am unable to properly print a playlist in the jewel case format. All lines bunch together. I have no problem with other print formats. Help please.

If it is a USB powered external, no AC adpater, that may be the reason. Mac notebooks are known to have low powered USB ports. You can get around that with a Y USB cable to connect to 2 USB ports at the same time.

Please point to ebooks in fixed layout format with javascript animation and interactivity

Hi! I am a danish children's author and want to create an ebook in "Fixed layout" for the ibookstore. I want the ebook to have simple interactive and animated features triggered by javascript. I would like more knowledge about what is and isn't possible with the javascript and CSS in apples fixed layout format. I have already viewed the "Yellow Submarine" ebook and Apples sample ebook "Sonnet 18". Are there more examples available?
Please do not point me to apps. There are great interactive book-apps for children - but for this project I am only interested in the Fixed layout format for the ibookstore.
All replies will be greatly appreciated, thanks!

if I can help, let me know...
check out the new series to help create publications. just search in the iTunes Store for An iBuild Opportunity

Allowing a User to choose the ALV layout format on selection-screen

Hi all,
I would like to know how i can add a parameter to my selection-screen which would allow the User to choose a saved ALV layout format before pressing F8 rather than after. As used in CO15 or MB51.
Thanks femi.

yes , You can check the program BCALV_TEST_FULLSCREEN_LAYOUT to check how F4 help is to be used .
to check existene of variant is pretty simple.
Pass the variant name in the ALV display FM .

Problem with input data format - not "only" XML

Hi Experts,
I have problem with input data format.
I get some data from JMS ( MQSeries) , but input format is not clear XML.
This is some like flat file with content of XMLu2026.
Example:
0000084202008-11-0511:37<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:xsd:test.01" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance Sndr="0001" Rcvr="SP">
...content....
</Document>000016750
Problems in this file is :
1. data before parser <? xml version="1.0"> -> 0000084202008-11-0511:37
2. data after last parser </Document> -> 000016750
This data destroy XML format.
Unfortunately XI is not one receiver of this files and we canu2019t change this file format in queue MQSeries ( before go to XI) .
My goal is to get XML from this file:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:xsd:test.01" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance Sndr="0001" Rcvr="SP">
...content....
</Document>
My questions:
1. Is any way or technique to delete this data 0000084202008-11-0511:37 in XI from this file ?
2. Is any way to get only XML from this file ?
Thanx .
Regards,
Seo

Hi Buddy
What is the XI adapter using?
If you use inbound File adapter content conversion you could replace these values with none and then pass it to the scenario.
Does that help?
Regards
cK

Problems with the Layout Priority in KM

Hello, I have some problems with the Layout Priority in KM..
I'm using a KM Navigation Iview with "Layout Set"=NewsBrowser (this Layout Set uses a Collection renderer that sorts the folder's contents by "last modified") and "Layout Set Mode"=exclusive.
In the KM folder I setted in Details->Settings->Presentation as "rndSortProperty"=name because I need to order my files by FileName property.
Despite that in see that the contents showed in my iview are ordered by Last Modified...
The "Layout Set Mode" exclusive gives the higher priority to the Folder Settings..
I don't understand..
Thank you in advance.

Thank you Shyja,
your post was helpful, but another issue is occurred.
Maybe en example could be useful..
My scenario:
- I need to show a km folder with layout set "ConsumerExplorer" on root folder (no "property of sorting" setted on its collection renderer) and "TabExplorer" (no "property of sorting" setted on its collection renderer).
- I need to sort files and folders by "last modified". By default seems that they are sorted by "name".
- With my administrator user I open my folder details (in Content Admin->KM Content is used the Layout "AdminExplorer"), and in "Settings->Presentation->Additional Parameters" I add two parameters "rndSortOrder=descending" and "rndSortProperty=modified" (the others are parameters of AdminExplorer Layout).
- Then I check "Apply Settings to All Subfolders" and "Use Settings for All iViews (Preferred Presentation)".
result:
I see the "ConsumerExplorer" on root folder, the subfolder are sorted by "last modified" (everything ok).
I click on a subfolder, the "TabExplorer" si showed, the Tabs and the content are sorted by "last modified" BUT..
.. into the tabs are showed nameFolders (in link style), the action command, and the properties of "author" and "last modified" (normally into the tabs are showed just the folderNames in text style)...
Why?? Is possible that the "AdminExplorer" parameters of the km folder affect the Tab component??
Thank you

Problem with downloading 2007 formats

I have a problem with downloading 2007 format files in my application. We can upload the 2007 formats without any problem. But, When we try to download them, we are receiving a 'Page cannot be displayed' error.
When we add the corresponding MIME-TYPES into IIS(Version 6.0) of the system(Test Environment), the problem got resolved. But there was a constraint to add the MIME-TYPES in the Production Box.
Can you please provide any alternate solution using CF code. I am pasting my sample code that my system is using for this.

For CF to set the MIME type for those files, it would have to be configured as a handler for those file extensions. By default, CF doesn't process requests for files other than .cfm, .cfc, etc.
You could write a download application that uses CFCONTENT to push files to the client, but the user would have to request your CF page, which might have a URL like this:
http://yourserver/download.cfm?file=myfile.docx
Or, you could map those file extensions to CF, but that would be a bad idea for several reasons. Even if it wasn't a bad idea, it would be harder to change on the server than the MIME types in IIS.
Frankly, you should fix this the right way - by having the server administrator add the correct MIME types.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

I can't sync my iPad to the iTunes it's give me an unknown error message 0xe8000012 I don't know how to fix it and where is the problem could be need format or the problem is in the charging port please can any one help me

I can't sync my iPad to the iTunes it's give me an unknown error message 0xe8000012 I don't know how to fix it and where is the problem could be need format or the problem is in the charging port please can any one help me

Unknown Error containing "0xE" when restoring
To resolve this issue, follow the steps in iPhone, iPad, iPod touch: Unknown error containing '0xE' when connecting. If you have a Windows computer with an Intel® 5 series/3400 series chipset, you may need updates for your chipset drivers. See iTunes for Windows: Issues syncing iOS devices with P55 and related Intel Chipsets for more information.
From Here > http://support.apple.com/kb/TS3694

Problem Printing to Large Format Printers From SGD

I am having a problem printing to large format printers when using the PDF printing option for SGD. The SDG Universal PDF Viewer recognizes the print format that I specify but on the client device side the pdf that is produced is always Letter size. If a larger format is speciied the client side pdf displays a small portion of it - almost as if it were clipped at the Letter size. Has anyone experienced this. Is it an SGD problem per se or is it an issue with the Ghostscript configuration and if so is ther a way I can change the config?
I am running 4.6.2 in an RHEL5 environment. The application server I am primarily working with is Windows Server 2008. The printers I have tried to print larger formats to are HP CLJ 2800 PS (Tabloid size), HP Designjet Z6100 (E size), and HP DesignJet 4020ps(E size). In all cases the plot appears to have been clipped into a Letter size format on the client device side.
Thanks,
Edited by: Odog314 on Jul 12, 2012 3:15 PM

You may have encountered a limitation with the GARO driver, especially if it is connected to the USB port of the Express. We have an iPF8100 but it is connected directly to our network via Ethernet so I've never tested the printer via USB. But if the driver is anything like the consumer inkjet drivers, there is often issues with the driver determining the printer model on the end of the USB and this stops the printer queue creation.
Have you tried connecting the printer via Ethernet to the Express and then seeing if you can add the printer queue? You will have to set an IP address in the machine if DHCP is not enabled.
PaHu

Reports layout/format problem when called from forms

hi,
using forms and reports builder 10g OS winxp
i have created web and paper layout report with pre-defined template gray (rdf). when i run the web layout there is no problem.
when i call this report from form using
web.show_document('http://machine:8889/reports/rwservlet?report=mail_report.rdf&destype=cache&desformat=HTML&userid=abc/xyz@dbname&para1='||:parameter1, '_blank');
the layout (cell bgcolors of the table) does not appear.
pl guide what am i missing out.
thanks

Hi,
that has nothing to do with forms. Your call inside web.show_document is a servlet-call. With this you get the paper layout of a report. If you want to get the web-layout, you have to call the report with a jsp-call. In your case that might look like http://machine:8889/reports/mail_report.jsp?userid=.....
If you store your report as jsp-file, you can use it for paper & web-layout, as rdf only paper-layout is possible.
http://download.oracle.com/docs/cd/B25016_08//doc/dl/bi/B14048_02/pbr_arch.htm#i1005927
http://download.oracle.com/docs/cd/B25016_08//doc/dl/bi/B14048_02/pbr_run.htm#g1022421
Regards
Rainer

10.9.1: Mail 7.1 screws up Print layout / formatting

Mail 7.1 in Mac OS X 10.9.1 screws up the layout of Messages you try to Print.
The two most common symptoms are that:
1) Blank space is inserted after the Headers and before the first line of the body of the message, so that the body of the message starts on the 2nd page. These are apparently blank lines (not a Page Break) because if you reduce the scaling below 100% the body of the message starts to show on the bottom of the 1st page, but still with a large chunk of bogus, blank space between it an the headers. And,
2) Extra blank pages are printed at the end of the message. This could be 1 to several blank pages. The number of extra blank pages is constant for each message, but differs between messages. These DO appear to be Page Breaks -- not simply a large chunk of blank lines.
These problems happen regardless of which printer is selected -- even happening if you Print via "Save As PDF".
These problems are NOT cured by Resetting the Printing System and then re-installing the printers.
For problem (1), the error seems to be uniquely associated with the use of "US Letter" Paper Size -- and only when used in Portrait orientation. If you switch to Landscape orientation, or if you use Portrait orientation with either US Legal Paper Size (which is larger) or A4 Paper Size (which is smaller) the bogus blank space after the Headers goes away.
However, problem (2) is NOT altered by switching either Paper Size or orientation. You still get the same number of bogus, blank pages at the end.
So far, I've only seen problem (1) when attempting to print Messages saved in my Sent folder. Problem (2) appears both with messages in the Inbox and Sent folders.
These problems only ever appear when the Message is printed. Messages viewed on screen have no such issues. The print formattting problems appear regardless of whether you Print the Message directly from the list of Messages in the Mail folder, or if you first double click on the Message to open it in its own window and THEN Print it.
Note that I have "Organize by Conversation" *NOT* selected in the view menu, so Reply and Forward messages include the prior text attached at the end -- forming one, longer Message. However, both problems (1) and (2) are exhibited on Messages which are comprised of a single Message *AND* Messages which included embedded text from prior Messages in their Reply or Forward chains. NOTE: Problem (1) only seems to show between the FIRST Headers and the start of the Message body -- not between any embedded Headers and the following text of their attached, Reply or Forward content.
Both problems also show both on Messages with attachments and Messages without attachments.
Has anyone found a way to cure these two problems?
Of course you can workaround problem (2) by adjusting the Print dialog to only print the non-blank pages. And you can kinda sorta work around problem (1) by selecting a Paper Size other than US Letter and then making judicious application of scaling in the Paper Handling sub-portion of the Print dialog, but these are manual steps you need to do DIFFERENTLY for EACH Message you want to print.
Deep sigh....
--Bob

I should add that these Print formatting issues do *NOT* show on every Mail 7.1 message in Mavericks 10.9.1.
So far, I've not been able to ferret out just what it is about a Message that cause Print formatting to screw up. Things I believe I've ELIMINATED include:
1) Newly created Messages vs. old Messages.
2) Messages with or without attachements
3) Messages with or without signatures
4) Messages which include prior Messages in a Reply or Forward string, or not (i.e., single, original Messages)
5) Mesages with multiple recipients or not or with CC: recipients in the Header or not.
However this problem is by no means "random". Any Message that shows one of the Three Problems I've detailed above will exhibit that Problem every single time you try to Print it. Any Message which Prints cleanly, will continue to Print cleanly every time as well. So there is SOMETHING about the data in the failing Messages which is triggering this problem.
One new behavior I've noted is that for some Messages a new notice appears on screen -- briefly -- the first time you try to Print them. It appears so briefly that I may have the exact text wrong, but it is something like "Generating Print Content". I'm beginning to suspect the Printing problems show ONLY on Messages that need to go through that "extra step" the first time you try to Print them. But I don't know what that Message implies -- i.e., is there a new, "printable" file being generated by Mail specific to that Message which might persist across different Print attempts? If so, the error may be due to how THAT file is created.
This new notice only seems to appear the FIRST time you try to Print a Message -- and evidently not on every Message (or pehaps it is so brief on some Messages that I just don't see it).
--Bob

Problem with changing layouts in xorg

Hi,
After installing new system (latest) i cant change layouts from keyboard
/etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.60 ([email protected]) Sun Oct 14 21:34:47 PDT 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
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"
Option "XkbOptions" "grp:ctrl_shift_toggle"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
/etc/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbVariant" ","
Option "XkbLayout" "us,ru"
Option "XkbOptions" "grp:ctrl_shift_toggle"
# Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
EndSection
Xorg log
[ 3949.901]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 3949.901] X Protocol Version 11, Revision 0
[ 3949.901] Build Operating System: Linux 3.6.2-1-ARCH x86_64
[ 3949.901] Current Operating System: Linux Hybrid 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64
[ 3949.901] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=34540cd4-1fc1-4e6d-815f-f26b49fd0ffd ro quiet
[ 3949.901] Build Date: 19 October 2012 03:54:56PM
[ 3949.902]
[ 3949.902] Current version of pixman: 0.26.2
[ 3949.902] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3949.902] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3949.902] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 7 15:47:17 2012
[ 3949.902] (==) Using config file: "/etc/X11/xorg.conf"
[ 3949.902] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3949.902] (==) ServerLayout "Layout0"
[ 3949.902] (**) |-->Screen "Screen0" (0)
[ 3949.902] (**) | |-->Monitor "Monitor0"
[ 3949.902] (**) | |-->Device "Device0"
[ 3949.902] (**) |-->Input Device "Keyboard0"
[ 3949.902] (**) |-->Input Device "Mouse0"
[ 3949.902] (==) Automatically adding devices
[ 3949.902] (==) Automatically enabling devices
[ 3949.902] (==) Automatically adding GPU devices
[ 3949.902] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3949.902] Entry deleted from font path.
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3949.902] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3949.902] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3949.902] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 3949.902] (WW) Disabling Keyboard0
[ 3949.902] (WW) Disabling Mouse0
[ 3949.902] (II) Module ABI versions:
[ 3949.902] X.Org ANSI C Emulation: 0.4
[ 3949.902] X.Org Video Driver: 13.0
[ 3949.902] X.Org XInput driver : 18.0
[ 3949.902] X.Org Server Extension : 7.0
[ 3949.904] (--) PCI:*(0:1:0:0) 10de:11c0:1043:8423 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3949.904] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3949.904] Initializing built-in extension Generic Event Extension
[ 3949.904] Initializing built-in extension SHAPE
[ 3949.904] Initializing built-in extension MIT-SHM
[ 3949.904] Initializing built-in extension XInputExtension
[ 3949.904] Initializing built-in extension XTEST
[ 3949.904] Initializing built-in extension BIG-REQUESTS
[ 3949.904] Initializing built-in extension SYNC
[ 3949.904] Initializing built-in extension XKEYBOARD
[ 3949.904] Initializing built-in extension XC-MISC
[ 3949.904] Initializing built-in extension SECURITY
[ 3949.904] Initializing built-in extension XINERAMA
[ 3949.904] Initializing built-in extension XFIXES
[ 3949.904] Initializing built-in extension RENDER
[ 3949.904] Initializing built-in extension RANDR
[ 3949.904] Initializing built-in extension COMPOSITE
[ 3949.904] Initializing built-in extension DAMAGE
[ 3949.904] Initializing built-in extension MIT-SCREEN-SAVER
[ 3949.904] Initializing built-in extension DOUBLE-BUFFER
[ 3949.904] Initializing built-in extension RECORD
[ 3949.904] Initializing built-in extension DPMS
[ 3949.904] Initializing built-in extension X-Resource
[ 3949.904] Initializing built-in extension XVideo
[ 3949.904] Initializing built-in extension XVideo-MotionCompensation
[ 3949.904] Initializing built-in extension XFree86-VidModeExtension
[ 3949.904] Initializing built-in extension XFree86-DGA
[ 3949.904] Initializing built-in extension XFree86-DRI
[ 3949.904] Initializing built-in extension DRI2
[ 3949.904] (II) LoadModule: "glx"
[ 3949.904] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3949.914] (II) Module glx: vendor="NVIDIA Corporation"
[ 3949.914] compiled for 4.0.2, module version = 1.0.0
[ 3949.914] Module class: X.Org Server Extension
[ 3949.914] (II) NVIDIA GLX Module 304.60 Sun Oct 14 20:44:54 PDT 2012
[ 3949.914] Loading extension GLX
[ 3949.914] (II) LoadModule: "nvidia"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 3949.915] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 3949.915] compiled for 4.0.2, module version = 1.0.0
[ 3949.915] Module class: X.Org Video Driver
[ 3949.915] (II) NVIDIA dlloader X Driver 304.60 Sun Oct 14 20:24:42 PDT 2012
[ 3949.915] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 3949.915] (++) using VT number 1
[ 3949.915] (II) Loading sub module "fb"
[ 3949.915] (II) LoadModule: "fb"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 3949.916] (II) Module fb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "wfb"
[ 3949.916] (II) LoadModule: "wfb"
[ 3949.916] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 3949.916] (II) Module wfb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "ramdac"
[ 3949.916] (II) LoadModule: "ramdac"
[ 3949.916] (II) Module "ramdac" already built-in
[ 3949.916] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 3949.916] (==) NVIDIA(0): RGB weight 888
[ 3949.916] (==) NVIDIA(0): Default visual is TrueColor
[ 3949.916] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 3949.916] (**) NVIDIA(0): Enabling 2D acceleration
[ 3950.393] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.393] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.403] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 660 (GK106) at PCI:1:0:0 (GPU-0)
[ 3950.403] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 3950.403] (--) NVIDIA(0): VideoBIOS: 80.06.10.00.0e
[ 3950.403] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 3950.403] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 3950.406] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 660 at PCI:1:0:0
[ 3950.406] (--) NVIDIA(0): CRT-0
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-1
[ 3950.406] (--) NVIDIA(0): DFP-2
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-4
[ 3950.406] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 3950.406] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.406] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.406] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.408] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.408] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.408] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.408] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.408] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.408] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.408] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.408] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.409] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.409] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.409] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.409] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.409] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 3950.410] (==) NVIDIA(0): will be used as the requested mode.
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (II) NVIDIA(0): Validated MetaModes:
[ 3950.410] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.410] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[ 3950.443] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 3950.443] (--) NVIDIA(0): option
[ 3950.443] (--) Depth 24 pixmap format is 32 bpp
[ 3950.443] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 3950.443] (II) NVIDIA: access.
[ 3950.445] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 3950.445] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 3950.445] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 3950.445] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 3950.445] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 3950.445] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 3950.445] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 3950.445] (II) NVIDIA(0): Config Options in the README.
[ 3950.448] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.551] Loading extension NV-GLX
[ 3950.608] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 3950.608] (==) NVIDIA(0): Backing store disabled
[ 3950.608] (==) NVIDIA(0): Silken mouse enabled
[ 3950.608] (**) NVIDIA(0): DPMS enabled
[ 3950.608] Loading extension NV-CONTROL
[ 3950.609] Loading extension XINERAMA
[ 3950.609] (II) Loading sub module "dri2"
[ 3950.609] (II) LoadModule: "dri2"
[ 3950.609] (II) Module "dri2" already built-in
[ 3950.609] (II) NVIDIA(0): [DRI2] Setup complete
[ 3950.609] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 3950.609] (--) RandR disabled
[ 3950.611] (II) Initializing extension GLX
[ 3950.643] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 3950.643] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.643] (II) LoadModule: "evdev"
[ 3950.643] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3950.643] (II) Module evdev: vendor="X.Org Foundation"
[ 3950.643] compiled for 1.13.0, module version = 2.7.3
[ 3950.643] Module class: X.Org XInput Driver
[ 3950.643] ABI class: X.Org XInput driver, version 18.0
[ 3950.643] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.643] (**) Power Button: always reports core events
[ 3950.643] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 3950.643] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.644] (--) evdev: Power Button: Found keys
[ 3950.644] (II) evdev: Power Button: Configuring as keyboard
[ 3950.644] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 3950.644] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3950.644] (**) Option "xkb_rules" "evdev"
[ 3950.644] (**) Option "xkb_model" "evdev"
[ 3950.644] (**) Option "xkb_layout" "us,ru"
[ 3950.644] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 3950.663] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.663] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.663] (**) Power Button: always reports core events
[ 3950.663] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 3950.663] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.663] (--) evdev: Power Button: Found keys
[ 3950.663] (II) evdev: Power Button: Configuring as keyboard
[ 3950.663] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 3950.663] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 3950.663] (**) Option "xkb_rules" "evdev"
[ 3950.663] (**) Option "xkb_model" "evdev"
[ 3950.663] (**) Option "xkb_layout" "us,ru"
[ 3950.663] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 3950.663] (II) No input driver specified, ignoring this device.
[ 3950.663] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device UVC Camera (046d:0821) (/dev/input/event6)
[ 3950.664] (**) UVC Camera (046d:0821): Applying InputClass "evdev keyboard catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'UVC Camera (046d:0821)'
[ 3950.664] (**) UVC Camera (046d:0821): always reports core events
[ 3950.664] (**) evdev: UVC Camera (046d:0821): Device: "/dev/input/event6"
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Vendor 0x46d Product 0x821
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Found keys
[ 3950.664] (II) evdev: UVC Camera (046d:0821): Configuring as keyboard
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/input/input6/event6"
[ 3950.664] (II) XINPUT: Adding extended input device "UVC Camera (046d:0821)" (type: KEYBOARD, id 8)
[ 3950.664] (**) Option "xkb_rules" "evdev"
[ 3950.664] (**) Option "xkb_model" "evdev"
[ 3950.664] (**) Option "xkb_layout" "us,ru"
[ 3950.664] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.664] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event3)
[ 3950.664] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev pointer catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.664] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event3"
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found 11 mouse buttons
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found x and y relative axes
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/input/input3/event3"
[ 3950.664] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: MOUSE, id 9)
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/mouse0)
[ 3950.665] (II) No input driver specified, ignoring this device.
[ 3950.665] (II) This device may have been added with another device file.
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event4)
[ 3950.665] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.665] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event4"
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found 1 mouse buttons
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found absolute axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found keys
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as keyboard
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.1/input/input4/event4"
[ 3950.665] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: KEYBOARD, id 10)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.665] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (WW) evdev: Razer Razer Mamba Charging Dock: ignoring absolute axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2010 (/dev/input/event5)
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2010'
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: always reports core events
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: Device: "/dev/input/event5"
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Vendor 0x46d Product 0xc52b
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found 1 mouse buttons
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found scroll wheel(s)
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found relative axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found absolute axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found keys
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as mouse
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as keyboard
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Adding scrollwheel support
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.2/0003:046D:C52B.0005/input/input5/event5"
[ 3950.665] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2010" (type: KEYBOARD, id 11)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.666] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.666] (II) evdev: Logitech Unifying Device. Wireless PID:2010: initialized for relative axes.
[ 3950.666] (WW) evdev: Logitech Unifying Device. Wireless PID:2010: ignoring absolute axes.
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) keeping acceleration scheme 1
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration profile 0
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration factor: 2.000
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration threshold: 4
[ 3950.666] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.702] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.702] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.702] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.702] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.702] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.702] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.702] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.702] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.702] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.702] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.703] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.703] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.703] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.703] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.703] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.714] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.714] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.714] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.714] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.033] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3951.033] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.033] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.033] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3951.033] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.033] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.033] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.033] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.033] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.033] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.034] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.034] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.034] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.034] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.044] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3951.044] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.044] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.044] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3951.044] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.044] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.044] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.044] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.044] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.044] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.045] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.045] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.045] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.045] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.045] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.685] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3961.685] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.685] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.685] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3961.685] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3961.697] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.697] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.697] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3961.697] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.080] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3963.080] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.080] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.080] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3963.080] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.080] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.080] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.080] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.080] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.080] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.081] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.081] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.081] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.081] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.091] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3963.091] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.091] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.091] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3963.091] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.091] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.091] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.091] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.091] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.091] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.092] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.092] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.092] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.092] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.092] (WW) NVIDIA(GPU-0): for mode "1920x1080".
Output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
variant: ,
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)" };
xkb_geometry { include "pc(pc104)" };
But this comand helps:
setxkbmap -layout "us,ru" -option "grp:ctrl_shift_toggle"
New output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
options: grp:ctrl_shift_toggle
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)" };
xkb_geometry { include "pc(pc104)" };
This config is still not changing visualistaion of layout (right top corner of gnome), but triggering is ok
If it helps - keyboard is Logitech K800, desktop - gnome 3
Thanks for attention and sorry for my bad english
UPD: Solved by Gnome settings, not Xorg
Last edited by fu2re (2012-11-12 09:44:01)

I have re-checked the issue and I found that the problem is with JPG file.
I wasn't even aware you could save a path to a jpeg file (always use PSD because of wanting to keep the Alpha Channel, jpeg only can contain 1 layer and no alpha channels and/or transparency).
However I tried it on a file with a simple path and one with a complex path. It seems indeed you have found a bug. The simple path is no problem but the more complex path is indeed disappearing.
It is not only label but also rate or adding IPTC in the description field. The moment metadata is saved to this jpeg file and reopened the earlier present work path of a more complex path is gone.
Despite the fact that to my opinion a jpeg is not the most suitable file format for saving a work path this should not happen. If a work path is saved to a jpeg then it should be kept saved after just altering metadata in Bridge.
It still is the same behavior in Bridge CC because that is what I use. Don't know when it started but it still needs to be repaired
Here is the link for filing a problem or bug:
http://feedback.photoshop.com/photoshop_family/

Problem in Payslip Layout format

Similar Messages

Maybe you are looking for