Caps Lock issue with Colemak layout in Xorg

Apologies if this is a silly problem; I'm rather new to linux in general. I'm trying to set up the US and Colemak layouts, and be able toggle between them. Ideally, caps lock will act as a second backspace in Colemak, and as it normally does in US.
The problem seems to be strictly with the secondary layout. If Colemak is second, then caps lock backspaces as it should, but is also toggled on or off each press. If US is second, then, instead of toggling, caps lock behaves as a backspace. This occurs both in xfce4, and before, at the lxdm log-in screen.
This is how I have it set up with setxkbmap:
setxkbmap -model pc104 -layout us,us -variant colemak, -option grp:shifts_toggle
Or in an Xorg conf.:
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "us,us"
Option "XkbModel" "pc104"
Option "XkbVariant" "colemak,"
Option "XkbOptions" "grp:shifts_toggle"
EndSection

The kind people from the IRC channel suggested I add this bit at the very end of the "/etc/X11/xorg.conf" file (instead of "/etc/X11/xorg.conf.d/10-evdev.conf" - tho it would've probably worked that way too):
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "us, ro"
Option "XkbVariant" "std"
Option "XkbOptions" "grp:caps_toggle, grp_led:scroll"
EndSection
Apparently it works. I just have to hold AltGr and press s, q , a, i, t, etc to type ș â ă î ț etc. But how do I set it to ; { } ] ' ", etc, like the default behaviour in Windows... ? I would like them to correspond to this layout.
Because this is not the "standard" ("std") version...
I may have to edit the "/usr/share/X11/xkb/symbols/ro" file to map them.
Unless there's a better way ?
Last edited by DSpider (2010-12-11 13:19:16)

Similar Messages

  • [ADF-11.1.2] Locking issue with SQL 92

    I see one Locking issue with SQL92 Oracle ADF Application.
    ADF Version: [ADF-11.1.2]
    Database: Oracle 10g Express Edition
    Situation 1:
    With Following setting:
    File: Application Resource > Description > ADF META-INF > adf-config.xml
        <startup>
          <amconfig-overrides>
            <config:Database jbo.SQLBuilder="SQL92" jbo.locking.mode="optimistic"/>
          </amconfig-overrides>
        </startup>I have a page showing record 'x' of view object. I open same record on another page. Now I have same record showing on two different tabs of browser.
    1. I modify first record and save it. It worked... Got commited to database.
    2. I goto second tab and modify same record and tried to same it. It throws me an error - Another user has changed the row with primary key oracle.jbo.Key[38 ] . As expected...
    3. I then, reopen the same record on 3rd tab of browser. Modify it and tried to save it. It just hang... as if it is processing the record endlessly.
    If I see the Log:
    <BaseSQLBuilderImpl> <doEntitySelectForAltKey> [312] BaseSQLBuilderImpl Executing doEntitySelect ... (true)
    <BaseSQLBuilderImpl> <doEntitySelectForAltKey> [313] Generating new LOCK statement
    <BaseSQLBuilderImpl> <buildSelectString> [314] Built select: 'SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT'
    <BaseSQLBuilderImpl> <doEntitySelectForAltKey> [315] Executing LOCK "SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT WHERE ID=? FOR UPDATE"
    <BaseSQLBuilderImpl> <bindWhereAttrValue> [316] Where binding param 1: 38
    That's it.. nothing happens further.. If I execute above query on SQL Worksheet, it doesn't come up with the result. Just hang for something...
    SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT WHERE ID='38' FOR UPDATE I can execute above query for other record of same table but not '38'. Even if I fire commit command to database, it is not working.
    I have to restart the database services to bring everything to normal state.
    Situation 2:
    With Oracle as Database :
        <startup>
          <amconfig-overrides>
            <config:Database jbo.SQLBuilder="Oracle" jbo.locking.mode="optimistic"/>
          </amconfig-overrides>
        </startup>Everything is working file. i.e. at step 3, record is getting modified successfully with following log:
    <OracleSQLBuilderImpl> <doEntitySelectForAltKey> [27] OracleSQLBuilder Executing doEntitySelect on: ESUSER.CI_AUDIT (true)
    <ADFLogger> <begin> Entity read all attributes
    <OracleSQLBuilderImpl> <buildSelectString> [28] Built select: 'SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT CIAudit'
    <OracleSQLBuilderImpl> <doEntitySelectForAltKey> [29] Executing LOCK...SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT CIAudit WHERE ID=? FOR UPDATE NOWAIT
    <ADFLogger> <addContextData> Entity read all attributes
    <OracleSQLBuilderImpl> <bindWhereAttrValue> [30] Where binding param 1: 38
    <ADFLogger> <addContextData> Entity read all attributes
    <ADFLogger> <end> Entity read all attributes
    <ADFLogger> <end> Lock Entity
    <ADFLogger> <begin> Before posting the entity's changes
    <ADFLogger> <begin> Updating audit columns
    <ADFLogger> <end> Updating audit columns
    <ADFLogger> <end> Before posting the entity's changes
    <OracleSQLBuilderImpl> <doEntityDML> [31] OracleSQLBuilder Executing, Lock 2 DML on: ESUSER.CI_AUDIT (Update)
    <OracleSQLBuilderImpl> <buildUpdateStatement> [32] UPDATE buf CIAudit>#u SQLStmtBufLen: 210, actual=60
    <OracleSQLBuilderImpl> <doEntityDML> [33] UPDATE ESUSER.CI_AUDIT CIAudit SET COLUMN_VALUE=? WHERE ID=?
    <ADFLogger> <begin> Entity DML
    <OracleSQLBuilderImpl> <bindUpdateStatement> [34] Update binding param 1: cip7ri1
    <OracleSQLBuilderImpl> <bindWhereAttrValue> [35] Where binding param 2: 38
    <ADFLogger> <addContextData> Entity DML
    <ADFLogger> <end> Entity DML
    Can any one please tell me, what is the issue with SQL92 setting ?
    Edited by: Anandsagar Sah on Mar 11, 2012 8:10 AM

    The framework works correctly in the Situation #1. Please, note that the locking statement in this case is "SELECT ... FOR UPDATE", but not "SELECT ... FOR UPDATE NOWAIT" (as it is in the Situation #2). When you entered the 2nd tab and tried to update the row, then the framework executed the locking statement and the row was locked (and it remained locked because the framework detected that another user had modified the row, so it stopped the processing and no COMMIT operation was executed). When you entered the 3rd tab and tried to update the row, then the framework tried to lock the row againg, but the locking statement was blocked by the existign lock and it started waiting on the lock from the 2nd tab. So this is expected behaviour.
    The interesting question is why you do not get any error in the Situation #2. In my opinion you should get an error because the locking statement from the 3rd tab should fail immediately (because the row should have been locked from the 2nd tab and the locking statement is with NOWAIT option). I suspect that when the DB is Oracle and you use Oracle SQLBuilder, then the ADF issues a DB savepoint at the beginning of the DML operation and rolls back to the savepoint is a case of some failure, so the 2nd tab has not left any lock. You can check this by setting on SQL trace on the DB server.
    Dimitar

  • Issue with Report Layout

    Hi All,
    I am working on a report which display employee present or absent in the month. I have to display dynamic column as days varies as per month .
    I am done with the report design/query part, using matrix report layout. Report executes and produce expected output too.
    Problem:
    As this report consists maximum 33 columns (1 = employ name + 31=days in the month + 1=Total days present) I change Page Layout to Landscape.
    When I select report output as "pdf" it generates report in Portrait Layout.
    Could you please tell me how to fix this issue?
    regards,
    RSD

    Title of this Forum: Forms
    Title of this Thread: Issue with Report Layout
    I can't point my finger on it, but something feels wrong. Or is it just me ;) ?
    Reports has its own forum dedicated to questions related to...reports:
    Reports
    You have a good chance that you get more answers over there. Also you did not mention any version numbers (reports version, database version,...) so please add these informations over there as well as the solution to your problem may depend on the version of the product you are using.
    good luck!
    cheers

  • Serious locking issues with Main Stage 3

    Having serious locking issues with main stage 3.  I just did a music gig over the weekend with main stage 3, and the application locked up 8 times during my performance.  There were also several times where there was a delay between the time I struck a key on the midi controller and the time sound actually came out of the audio interface.  Has anyone else ran into this problem??
    10.
    I am running mountain lion 10.8.5, on a 2009 Macbook 2.53 GHz Intel Core 2 Duo. w 8 GB Ram.
    Anyone know how to fix this, if even possible?  

    Just read some reviews. There seems to be a lot of problems with the latest main stage update.  I didn't notice these latency problems until did the latest update..
    Apple please fix this quickly!!!

  • Brush edges disappearing - Not a caps lock issue!

    Hello -
    I've upgraded to CS4 and Leopard (10.5.6) within the last month or so (computer is a dual G5). Recently (sometime in the last week) I've started having a problem where my brush edges disappear as soon as I start painting: I click to paint, and the cursor gets replaced with a standard black arrow for the duration of the stroke. When I let up on the mouse button, the arrow is still visible, but as soon as I move the mouse, the normal brush borders come back. My preferences are set correctly to display brush size and this has nothing to do with the caps lock (though I did try other preferences to see if it helped).
    The actual painting functions normally, it's just impossible to do any precision work when you can't tell where the stroke is going. This is true of the regular paint brush tool as well as the clone stamp, the healing brush, the blur tool, the eraser, and presumably everything else as well. Hard-edged brushes and well as soft ones, round as well as irregular shapes. I never imported any brushes that might be corrupted - I didn't even add to the brush palette from the included supplemental brush libraries.
    Trashing preferences didn't help. I reached the point where I uninstalled the whole application and reinstalled from scratch - no difference, even before I changed any preferences or options.
    This is driving me nuts. I know I'm not going crazy, because I've got two Macs with CS4 less than 10 feet away from me (one with identical hardware to my own), and the brushes on them show up as perfectly normal. Does anyone have any suggestions?
    Thanks,
    --Bonnie

    Sorry for the delay in replying - I was out sick all last week and am only now getting caught up.
    It turns out that it seems to have been the mouse driver. I have a Macally Ice Mouse I got with the computer - it's optical with a scroll wheel, but simple and not terribly programmable, so way back when I installed the driver and promptly forgot about it. Macally currently offers a driver for system 10.4-10.5, plus an older one for 10.1-10.3. Mine was older still. Upgrading to the 10.5 driver caused the mouse to go haywire, however, and I wasted a lot of time trying to get it to work. As a last resort before replacing the mouse, I tried the 10.1-10.3 driver, and surprisingly it allows the mouse to function properly without recreating the Photoshop issue. So I'll try to keep the obsolete driver in mind next time I have an inexplicable problem, but in the meantime I'm just happy to be functioning again.
    Kudos (and thanks!) to Ann for the idea. Jim, does this help you any?
    Cheers,
    --Bonnie

  • Wireless keyboard caps lock issue (not LED related)

    i just bought an iMac last week and I'm having a weird issue with caps locks. It seems like that particular key needs to be pressed harder than the rest of the keys to register a keystroke. If I hit it lightly, the key will depress but the keystroke won't register and the LED light won't come on. Any other key, even if I hit it very lightly, as long as it was pressed down, the keystroke is registered,
    I found the right amount of force where I can press it down like 10 times and it won't register the keystrokes at all. When I'm typing fast, I'll have to go back to capitalize almost 80% of the letter that need capitalizing even though I hit the caps lock key while I was typing. All the "I"s, the first letters of every sentence and the first letters of proper names.
    I've had plenty of keyboards, some wireless and I've never had this issue, nor have I had it on my Macbook. I'm just wondering if this is how it was designed to work or if I have a faulty keyboard that I need to go and replace.

    Hi Guys
    Glad I've just found these posts. Got a new 27" iMac just before Christmas. Greatly relieved that everything worked despite all the reports of cracked screens, etc. BUT - only small problem was the Caps Lock light not always coming on. Rang Apple and got a replacement. Now today I'm having same problems - first the light froze and wouldn't go off. Then it wouldn't come on. I've now tried your advice of switching off the keyboard and taking out the batteries. Works OK now. Hopefuly it'll stay that way. Only thing is - pity Apple couldn't have given me that advice. Reading these posts, there is clearly an ongoing problem with the caps lock light on the wireless keyboard. A problem thats been around for months. Clearly Apple's poilicy, as always, is to admit nothing until it comes up with a fix. Pity that policy appears to extend to not even telling their own employees that there is a problem ...

  • Aluminum Bluetooth Keyboard - Caps Lock Issue

    I've purchased the new Apple aluminum bluetooth keyboard, and I'm noticing that the caps lock key has some issues... first off, the little light that indicates the key is on/off rarely comes on. Second, the capslock key doesn't register each time it's depressed, making typing very awkward because I'm quite the proficient typer, and I use the capslock key to type all my uppercase characters, even single characters (goofy, I know), so I often type a word or two in caps before I stop myself and go back.
    I've been using Apple laptops for several years now, so I'm quite used to the flat keys and I'm sure I'm depressing the key correctly as I type. I've also tested it quite thoroughly by carefully pressing it down, just to see if I'm certain, although these tests are somewhat hampered by the first issue (no light to indicate wether it's really on or not).
    The keyboard is brand new (it's not even a week old), and I'm not sure if it might just be a manufacturing flaw with this particular unit or if it's software related (as there has already been one patch for this line of keyboards this week). Other then that, it runs great and feels amazing (especially being used to a laptop keyboard). It's also light as a feather! However, is anyone else experiencing any issues like this?
    Alex

    New development: I've noticed my caps key (incl. light) has been working how I would describe as "as intended" for the last few hours; ever since I bumped the power key on the side of the battery tube earlier while picking up the keyboard. I'm not sure if this is the cause of my recent success, but I'll look into it.
    I'm thinking more and more this is a software related issue. Perhaps Apple will look into how the various states the keyboard can be in (I'm sure there must be a few, or perhaps in relation to the state of the system) might affect the caps key. It sounds weird, I know, but things seem to be working just fine now. I'm not sure how long that will last of course; I'll post again if/when it stops working, which my guess will be tomorrow after I've let my system go to sleep for the night, but that's speculation based on the fact that my MBP has other "wake from sleep" quirks I've learned to deal with...maybe this is one of them.
    Alex

  • HT1338 My MacBook Pro (running Leopard 10.5.8) won't allow keyboard to type an upper case 'C' using the shift key...works fine with caps lock, or, with my Typinator workaround using double-typed lower case c (not always best). Any ideas?

    My MacBook Pro keyboard won't type an upper case 'C' using the shift key... only with caps lock. Workaround has been to use Typinator by typing a double lower case c, not always the best solution. Mac is a refurbished model, which initially was fine. Apple tech helped me correct the quirk when it first appeared, but now it has returned and refuses fixes. Any ideas?

    I'm willing to bet that this has something to do with iCloud.  I've been facing a frozen computer nearly every time I go into it. 
    In Activity Monitor I have seen two programs associate with iCloud that take up about 2.5 GB of memory (I only have 4 in the computer) -- causing everything to freeze.  One of these is called "iCloud Helper" and the other one is something like "Address Book Sync helper" -- I see parts of these names in the stuff you have posted.
    I am at my wits' end with these and have written to Apple asking them to do away with these or fix them.  To get rid of the Address book sync thing I have gone into system preferences for iCloud and unchecked Contacts -- but then spontaneously it gets rechecked.  And oftentimes after I Force Quit the iCloud helper, it spontaneously turns on again.  My conclusion --- the iCloud is basically unusable.  It turns a Mac into the most useless, clogged, sluggish PC.  If this is happening to a lot of people's computers -- and I see no reason why yours or mine should be an exception -- these programs just might destroy Apple itself. 
    So -- I'm about to completely give up on iCloud, and I suspect that others will too unless this gets fixed.
    Cheers,
    Bob

  • Row locking issue with version enabled tables

    I've been testing the effect of locking in version enabled tables in order to assess workspace manager restrictions when updating records in different workspaces and I have encountered a locking problem where I can't seem to update different records of the same table in different sessions if these same records have been previously updated & committed in another workspace.
    I'm running the tests on 11.2.0.3.  I have ROW_LEVEL_LOCKING set to ON.
    Here's a simple test case (I have many other test cases which fail as well but understanding why this one causes a locking problem will help me understand the results from my other test cases):
    --Change tablespace names as required
    create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
    alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
    exec dbms_wm.gotoworkspace('LIVE');
    insert into t1 values ('1', 'name1');
    insert into t1 values ('2', 'name2');
    insert into t1 values ('3', 'name3');
    commit;
    exec dbms_wm.enableversioning('t1');
    exec dbms_wm.gotoworkspace('LIVE');
    exec dbms_wm.createworkspace('TESTWSM1');
    exec dbms_wm.gotoworkspace('TESTWSM1');
    --update 2 records in a non-LIVE workspace in preparation for updating in different workspaces later
    update t1 set name = name||'changed' where id in ('1', '2');
    commit;
    quit;
    --Now in a separate session (called session 1 for this example) run the following without committing the changes:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --Now in another session (session 2) update a different record from the same table.  The below update will hang waiting on the transaction in session 1 to complete (via commit/rollback):
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    I'm surprised records of different ids can't be updated in different sessions i.e. why does session 1 lock the update of record 2 which is not being updated anywhere else.  I've tried this using different non-LIVE workspaces with similar results.  I've tried changing table properties e.g. initrans with and still get a lock.  The changes to table properties are successfully propagated to the _LT tables but not all the related workspace manager tables created for table T1 above.  I'm not sure if this is the issue.
    Note an example of the background workspace manager query that may create the lock is something like:
    UPDATE TESTWSM.T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG.CHECKNGETLOCK(:B6 , LTLOCK, NEXTVER, :B3 , 0,'UPDATE', VERSION, DELSTATUS, :B5 ), NEXTVER = WMSYS.LT_CTX_PKG.GETNEXTVER(NEXTVER,:B4 ,VERSION,:B3 ,:B2 ,683) WHERE ROWID = :B1
    Any help with this will be appreciated.  Thanks in advance.

    Hi Ben,
    Thanks for your quick response.
    I've tested your suggestion and it does work with 2 workspaces but the same problem is enountered when additional workspaces are created. 
    It seems if multiple workspaces are used in a multi user environment, locks will be inevitable which will degrade performance especially if a long transaction is used. 
    Deadlocks can also be encountered where eventually one of the sessions is rolled back by the database. 
    Is there a way of avoiding this e.g. by controlling the creation of workspaces and table updates?
    I've updated my test case below to demonstrate the extra workspace locking issue.
    --change tablespace name as required
    create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
    alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
    exec dbms_wm.gotoworkspace('LIVE');
    insert into t1 values ('1', 'name1');
    insert into t1 values ('2', 'name2');
    insert into t1 values ('3', 'name3');
    commit;
    exec dbms_wm.enableversioning('t1');
    exec dbms_wm.gotoworkspace('LIVE');
    exec dbms_wm.createworkspace('TESTWSM1');
    exec dbms_wm.gotoworkspace('TESTWSM1');
    update t1 set name = name||'changed' where id in ('1', '2');
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    --end of original test case, start of additional workspace locking issue:
    Session 1:
    rollback;
    Session 2:
    rollback;
    --update record in both workspaces
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '3';
    commit;
    exec dbms_wm.gotoworkspace('TESTWSM1');
    update t1 set name = 'changed' where id = '3';
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;
    exec dbms_wm.gotoworkspace('LIVE');
    exec dbms_wm.createworkspace('TESTWSM2');
    exec dbms_wm.gotoworkspace('TESTWSM2');
    update t1 set name = name||'changed2' where id in ('1', '2');
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --this now gets locked out by session 1
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;
    --update record 3 in TESTWSM2
    exec dbms_wm.gotoworkspace('TESTWSM2');
    update t1 set name = 'changed' where id = '3';
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --this is still locked out by session 1
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;
    --try updating LIVE
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '3';
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --this is still locked out by session 1
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;
    --try updating TESTWSM1 workspace too - so all have been updated since TESTWSM2 was created
    exec dbms_wm.gotoworkspace('TESTWSM1');
    update t1 set name = 'changed' where id = '3';
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --this is still locked out by session 1
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;
    --try updating every workspace afresh
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changedA' where id = '3';
    commit;
    exec dbms_wm.gotoworkspace('TESTWSM1');
    update t1 set name = 'changedB' where id = '3';
    commit;
    exec dbms_wm.gotoworkspace('TESTWSM2');
    update t1 set name = 'changedC' where id = '3';
    commit;
    Session 1:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '1';
    --this is still locked out by session 1
    session 2:
    exec dbms_wm.gotoworkspace('LIVE');
    update t1 set name = 'changed' where id = '2';
    Session 1:
    rollback;
    Session 2:
    rollback;

  • Triggering program form(subroutine)  from MIGO using output types gives lock issue with Bapi_sag_change

    Hi,
    On creating the GR from MIGO tcode, based on the quantity check i am updating the field ELIKZ using BAPI_SAG_CHANGE.
    And updation logic is written in a zprogram using with in FORM XXXXX...ENDFORM XXXXX. ( FORM XXXXX is configured in the output type ).
    So the problem i am facing is on creation of the first GR with scheduling agreement number GR is posted successfully and under the output tab the i can see the green icon.
    But on creation of the second GR with same scheduling agreement its showing red icon. The following is the error message " User locked the scheduling agreement ...."
    I even tried using dequeue fm and transaction commit, but it didnt work. Please let me know how to over come the lock issue.
    Thanks & regards,
    Manojkumar K

    Solved it myself....
    Regards,
    Manoj

  • Locking issue with BAPI_GOODSMVT_CREATE in userexit_save_document

    Hello All,
    I am performing a separate goods movement for one of the materials in the delivery userexit_save_document during PGI. I have an issue. We might have multiple users trying to PGI deliveries and thereby performing the goods movement for the same material through the BAPI in the userexit_save_document.
    How do I prevent the locking issue when say two users go through the BAPI for goods movement for the same material data at the same time.
    Any answer in this regards is highly appreciated.
    Thanks,
    Mathangi

    Thanks Rich... this make work for me, but one question -
    Do you know if this function releases all lock objects for the user system wide or only for the current session? My concern is that if it is system wide, then I could be releasing lock objects for other sessions unintentionally. For example, if there are multiple RFC calls in parallel for the same function and same user then I could be destroying lock entries that I shouldn't be! I am hoping that it removes lock entries only for the current session...
    any ideas?
    Regards,
    Lee
    > I've used this BAPI in many of my programs,  and
    > always after the call, I code.....
    >
    >
    >
    >     commit work and wait.
    >     call function 'DEQUEUE_ALL'.
    >
    >
    >
    > The DEQUEUE_ALL show release any/all locks.
    >
    >
    > Regards,
    > Rich Heilman

  • 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/

  • Weird File Locking Issue with Excel 2013

    We are experiencing a strange issue whereby we are frequently unable to save Excel files; whilst working on a document a user will select Save As, change the name of the document and attempt to save, a 0KB file is created in the location and an error returned
    to the user stating that the file is in use by another user. At this point it is normally possible to save but on occasion this has also failed. It is possible to duplicate the issue on multiple machines.
    The user has Full control over the destination directory, both share & NTFS.
    File Server is running Windows Server Essentials 2012R2.
    The Users desktops are running Windows 7 sp1, all available Windows Updates have been applied.
    They have an Office 2013 Small Business Premium subscription, two of the users have a full msi based installation of Office and one the Click-to-Run version.
    They use Eset Endpoint Antivirus and Eset File Security on the server, the problem can be duplicated with both client & server antivirus disabled.
    Have disabled power saving on client & server network cards.
    Does anyone have any suggestions on how to troubleshoot this?

    Hi,
    As far as I know, if one user had opened or edited one file in File Server, the other users only could be open the file read-only. It could not be saved or other behavior.I would suggest the following:
    Turn off the Preview Pane, Details Pane and pop ups that show information about file and desktop items.
    This is a problem that has been reported to affect Windows 7 clients only, not Windows XP. The problem here may have something to do with the Windows Explorer in Windows 7. We are currently investigating this further and will post more information as it
    is available.
    In a Windows Explorer window, do the following:
    1. Right click on the Start Button.
    2. Click 'Open Windows Explorer'.
    3. At the top left click Organize > Layout 
    4. Uncheck Details Pane and Preview Pane.
    5. On a Windows menu, click on Tools > Folder Options.  In the box that opens up, click on the View tab.  Scroll down the list to
    “Show pop-up description for folder and desktop items” and clear the checkbox and then click OK. 
    http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2012/05/14/the-definitive-locked-file-post.aspx
    BTW, I recommend you
    use a shared workbook to collaborate in Excel.
    Regards,
    George Zhao
    TechNet Community Support

  • Issue with RTF layout vs. PDF layout

    I'm creating a report that needs to have output for both PDF and RTF. I have a simple request, I need to have 1 line drawn in the report. No data issues or anything else, just a simple line.
    I've used the auto-shape menu to draw a line and it appears in my PDF output but not my RTF output. I've also tried having a table be in my layout and just show the bottom or top border. The problem with that is that in the RTF output, the user will see the other lines of the table whether I like it or not.
    In the BI Pub manual it says, 'BI Publisher supports Microsoft Word drawing, shape, and clip art features. You can add these objects to your template and they will be rendered in your final PDF output.' Anyone know if this is worded this way because Oracle knows it won't work in your RTF output?
    Thanks!
    Kris Henning
    www.piocon.com

    Could you test it to be according to the following step?
    Step 1:
    You must get the following values from application.
              SELECT xt.template_code
              ,xt.application_short_name
              ,xt.application_id
              ,xt.template_type_code
              INTO l_template_code
              ,l_application_short_name
              ,l_application_id
              ,l_template_type_code
              FROM apps.xdo_templates_vl xt
              ,apps.xdo_ds_definitions_b xds
                   ,fnd_concurrent_programs fcp
                   ,fnd_concurrent_requests fcr
              WHERE xt.ds_app_short_name = xds.application_short_name
              AND xt.data_source_code = xds.data_source_code
              AND fcp.concurrent_program_name = xds.data_source_code
              AND xds.application_short_name = ( SELECT application_short_name
              FROM fnd_application
              WHERE application_id = fcp.application_id
              AND fcp.concurrent_program_id = fcr.concurrent_program_id
              AND fcr.request_id = :p_conc_request_id
              AND (xt.end_date IS NULL OR TRUNC(xt.end_date) > TRUNC(sysdate));
    Step 2:
    Submit the concurrent program in RDF. Below are the scripting codes.
              IF      l_template_code IS NOT NULL
              AND :p_conc_request_id IS NOT NULL THEN
                   l_request_id := FND_REQUEST.SUBMIT_REQUEST ( 'XDO'
              ,'XDOREPPB'
                                                                ,'XML Report Publisher'
                                                                     , TO_CHAR (SYSDATE,'YYYY/MM/DD HH24:MI:SS')
                                                                     , FALSE
                                                                     , :p_conc_request_id
                                                                     , l_application_id --l_application_short_name 
                                                                     , l_template_code
                                                                     , NULL
                                                                     , 'N'
                                                                     , l_template_type_code
                                                                     , 'PDF'
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL,NULL,NULL
                                                                     , NULL,NULL,NULL
              COMMIT;
                   ELSE
                                  srw.message(1,'Error in Fetching the Template');
                   srw.message(1,'l_template_code : '||l_template_code);
                   srw.message(1,'p_conc_request_id : '||:p_conc_request_id);
                   END IF;
    Thanks.
    Sinolee

  • BAPI_GOODSMVT_CREATE lock issue with no access to ABAP!

    Hello everyone,
    I have written a class in vb .NET that uses the BAPI_GOODSMVT_CREATE to post goods issues. I have done numerous tests myself which all were successful. However, when a colleague wanted to test my class he suddenly got the following error "The plant data of the material <XXXX> is locked by the user <XXXX>". The user specified is the standard background user we use for RFCs. So basically the user is blocking himself.
    This issue seems to be quite common as Google turns up with numerous results. They either end up with people being desperate and giving up or finding solutions in ABAP. However, my team has no access to ABAP since SAP-programming has all been outsourced to India. Getting any changes done in ABAP will be a long and tedious progress for which we simply do not have the time.
    Is there anyway to resolve this issue on our side? Maybe through other RFCs or changes in how we handle the BAPI? I am quite desperate as this problem occurred shortly before we wanted to go live and now it is not sure we can even do anything on our side.

    Hi Tom,
    If you want to call DEQUEUE_ALL from vb.net then tell your ABAP counterpart to create a new remote enabled function module and he can subsequently make a call to DEQUEUE_ALL in the custom developed function module through ABAP. You can then call the newly created custom function module using its calling parameter.
    Also, if required he can expose that newly custom created function module as a webservice that you can call from vb.net.
    I hope its clear to you now about how can you access it from vb.net.
    Regards,
    Sachin

Maybe you are looking for

  • Hp officejet pro 576 prints but won't scan

    Friends, We recently bought and installed an HP Office Jet Pro x576 dw.  After initial setup, it seemed to work fine.  Shortly afterwards, however, the scanning to computer feature has failed.  Here is what I have tried so far: I uninstalled and rein

  • XSLT Mapping Error - Split-MappingRoot-Tag missing

    Hi, I am getting "Split-MappingRoot-Tag missing" Error while using XSLT mapping. I am using 3 mappings in one Operation Mapping. 1)  Java Mapping 2) Message Mapping 3) XSLT Mapping. When I have these mappings in a BPM one after another it is working

  • Thunderbolt to VGA question

    I'm a new Macbook Air owner. I did previously use iMac at work for a couple of years. I am trying to connect it to an external monitor (Acer AL1702W), using the mac mini display port to VGA adapter. I do get a display on the external monitor, but onl

  • I dont like ios 7.0.4

    I Don't like iOS 7.0.4 Because Laggy and Slow HELP Support to DOWNGRADE iOS 7 In iPhone 4/4s look people said About iPhone 4/4s After Update iOS 7 !!

  • Sort music alphabetically on ipad 2 ios7.04

    Do not have a more tab on my music app and my music does not sort alphabetically. It sorts by artist alphabetically even though the artist tab is NOT selected.