Wmnice: a window manager aware process renicer.

Here is a little gambas script which makes the current window prioritized.
When the active window changes, an event is triggered, then it manages to discover the pid of the current application and renice it with "Current nice - nicestep" value (default -5).
The previous active window is then restored to the previous nice value (if it was reniced).
To exit the script, you have to hit the ENTER key so that it can restore the last window pid (or else it is left 'niced')
Also, you probably need to run [EDIT] with suid bit set or give your user the rights to set priorities under 0[/EDIT]
There is no configuration, all you need is to run the script.
Required packages:
* gambas3-gb-gui
* gambas3-gb-image
* gambas3-gb-desktop
* wmctrl
' Gambas module file
Public Extern getpriority(which As Integer, who As Integer) As Integer In "libc:6"
Public Extern setpriority(which As Integer, who As Integer, nice As Integer) As Integer In "libc:6"
Public MyDesktopWatcher As Desktopwatcher
Public LastWindowName As String
Public LastPid As Integer = -9999
Private NiceStep As Integer = 5 'niceness step value
Private Function PidFromWid(Wid As String) As Integer
Dim wmctrl As String
Shell "wmctrl -lp | grep " & wid To wmctrl
Print "-------------------"
Return Trim(Mid(wmctrl, 15, 6))
End
Public lastnice As Integer = -9999
Public Sub MakeFasterAndRestore(pid As Integer, lastpid As Integer)
'Restore last pid nice
If ((lastnice > -9999) And (lastpid <> -9999)) Then
setpriority(0, lastpid, lastnice)
Debug "RESTORE: Setpriority OK, PID=", lastpid, "NewPri=", getpriority(0, lastpid)
Endif
'Get the current pid nice and store it
lastnice = getpriority(0, pid)
'make the current pid faster
setpriority(0, pid, lastnice - NiceStep)
Debug "FASTER : Setpriority OK, PID=", pid, "NewPri=", getpriority(0, pid)
End
Public Sub Restore(pid As Integer)
If lastnice = -9999 Then Return
setpriority(0, pid, lastnice)
Debug "RESTORE: Setpriority OK, PID=", pid, "NewPri=", getpriority(0, pid)
End
Public Function ActiveWid() As String
Return Lower(Hex(Desktop.activewindow))
End
Public Sub MyDesktopWatcher_activewindow()
'raised when the active window has changed
Dim ActiveWindowName As String
Dim pid As Integer
'avoid double events:
Try ActiveWindowName = Desktop.Windows.FromHandle(Desktop.ActiveWindow).Name
If Error Then Return
If ActiveWindowName = LastWindowName Then Return
lastwindowname = ActiveWindowName
Try PID = PidFromWid(ActiveWid())
If Error Then Return
Debug "Active window caption= ", ActiveWindowName
Debug "PID", pid
If (pid <> "") Then
MakeFasterAndRestore(pid, lastpid) 'renice current pid and restore previous
Endif
LastPid = pid
Print "** hit ENTER to quit, NOT CTRL-C **"
End
Public Sub Application_read() 'ENTER key to exit
'restore last pid with priority from lastnice (global var)
Restore(PidFromWid(ActiveWid()))
Print "bye"
Quit
End
Public Sub Main()
MyDesktopWatcher = New DesktopWatcher(True) As "MyDesktopWatcher"
End
Last edited by kokoko3k (2011-10-12 17:38:33)

Interesting concept, have to try that out sometime. Though I won't use your implementation, too much/uncommon deps imho. I'm sure this concept could be quite easily done directly with some WMs, i.e. FVWM (via the Event-Intercafe).
But I'll do it less generic, i.e. I don't see the point giving f.e. my mail-client a high priority when there's things like video conversion running in the background.
There's also verynice, which I found by a quick search.
Thanks for the idea, though

Similar Messages

  • I just updated firefox TODAY 8/17/11 and after the update i can't open firefox unless i restart my computer or i delete going to windows task manager and process, also i can't open a new window, it won't allow it. please can you help me

    I just updated firefox TODAY 8/17/11 and after the update i can't open firefox unless i restart my computer or i delete firefox going to windows task manager and process, also, i can't open a new window, it won't allow it. please help me, everything works on IE, Google Chrome and Safari, everything went wrong after the update

    Hey Elaine07!
    I have an article here that can help you with that issue. This article will help you make sure you have uninstalled iTunes correctly and help you troubleshoot the launch issues you are seeing:
    iTunes for Windows Vista or Windows 7: Troubleshooting unexpected quits, freezes, or launch issues
    http://support.apple.com/kb/ts1717
    Take care, and thanks for visiting the Apple Support Communities.
    -Braden

  • ERROR MESSAGE sap system manager:work process restarted, session terminated

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue. Here are the details
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer      
    termination messages, especially those beyond their normal deletion           
    date.                                                                               
    Error analysis
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                                                                               
    System environment
    SAP Release.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi
       follow correction method suggested in this dump,
    " The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.  Save this file under another name."
    have you done this?
    with regards,
    raj.
    <i>pls, award points</i>

  • My window manager only starts 50% of the time.

    Hello all, I installed arch about a week ago and it has run perfectly.
    Unfortunately about 2 days ago I have a strange issue that I can't seem to diagnose.
    When I boot my arch install, (dual boot win8 with seperate hard drive), and login using slim, around 50% of the time everything will load up and my panel will show etc.
    The other 50% of the time the desktop brings up just my mouse, I'm using a tiling manager and the hotkeys dont work either which makes me think that .xinit isn't being executed, yet other things in there work fine.
    bspwm is my window manager, slim is my login manager, I looked in xorg.0.log a few times and couldn't find anything.  Any help would be appreciated!
    (Sorry if this is in the wrong place, also ask for any files you need)

    Trilby wrote:
    Chazza, using exec is common, but not at all necessary.  Without the exec, the parent shell process just hangs around - this is unneeded, but it does no harm.  One can even put many WMs one after the other with no exec command to run one right after the other.  Or put a few (or just one) WM in a loop with no 'exec' in order to restart the WM without restarting X (this can be seen in the dwm wiki for one example).
    Toqoz, please post (or link to) 2 xorg logs: 1 for a successful run, and one for the failed attempt.
    Heres my /var/log/Xorg.0.log file for a successful boot, couldn't find the xorg folder in ~/.local/share/xorg.
    [ 15.806]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 15.806] X Protocol Version 11, Revision 0
    [ 15.806] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 15.806] Current Operating System: Linux qhost 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
    [ 15.806] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=db8748e8-ddcb-48c6-ac0c-e8560a1c3848 rw quiet
    [ 15.806] Build Date: 14 March 2015 06:45:50PM
    [ 15.806]
    [ 15.806] Current version of pixman: 0.32.6
    [ 15.807] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 15.807] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 15.807] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 2 20:30:04 2015
    [ 15.871] (==) Using config file: "/etc/X11/xorg.conf"
    [ 15.872] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 15.872] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 16.049] (==) ServerLayout "Layout0"
    [ 16.049] (**) |-->Screen "Screen0" (0)
    [ 16.049] (**) | |-->Monitor "Monitor0"
    [ 16.050] (**) | |-->Device "Device0"
    [ 16.050] (**) |-->Input Device "Keyboard0"
    [ 16.050] (**) |-->Input Device "Mouse0"
    [ 16.050] (==) Automatically adding devices
    [ 16.050] (==) Automatically enabling devices
    [ 16.050] (==) Automatically adding GPU devices
    [ 16.084] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 16.084] Entry deleted from font path.
    [ 16.084] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 16.084] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 16.084] Entry deleted from font path.
    [ 16.084] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 16.084] Entry deleted from font path.
    [ 16.084] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 16.085] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 16.085] Entry deleted from font path.
    [ 16.085] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 16.085] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 16.085] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 16.085] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 16.085] (WW) Disabling Keyboard0
    [ 16.085] (WW) Disabling Mouse0
    [ 16.085] (II) Loader magic: 0x815d80
    [ 16.085] (II) Module ABI versions:
    [ 16.085] X.Org ANSI C Emulation: 0.4
    [ 16.085] X.Org Video Driver: 19.0
    [ 16.085] X.Org XInput driver : 21.0
    [ 16.085] X.Org Server Extension : 9.0
    [ 16.086] (EE) systemd-logind: failed to get session: PID 333 does not belong to any known session
    [ 16.086] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 16.088] (--) PCI:*(0:1:0:0) 10de:1187:3842:2765 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 16.088] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 16.088] (II) LoadModule: "glx"
    [ 16.097] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 17.059] (II) Module glx: vendor="NVIDIA Corporation"
    [ 17.059] compiled for 4.0.2, module version = 1.0.0
    [ 17.059] Module class: X.Org Server Extension
    [ 17.067] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 17.089] (II) LoadModule: "nvidia"
    [ 17.130] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 17.222] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 17.222] compiled for 4.0.2, module version = 1.0.0
    [ 17.222] Module class: X.Org Video Driver
    [ 17.232] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 17.232] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 17.233] (++) using VT number 7
    [ 17.321] (II) Loading sub module "fb"
    [ 17.321] (II) LoadModule: "fb"
    [ 17.321] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 17.347] (II) Module fb: vendor="X.Org Foundation"
    [ 17.347] compiled for 1.17.1, module version = 1.0.0
    [ 17.347] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 17.347] (II) Loading sub module "wfb"
    [ 17.347] (II) LoadModule: "wfb"
    [ 17.347] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 17.364] (II) Module wfb: vendor="X.Org Foundation"
    [ 17.364] compiled for 1.17.1, module version = 1.0.0
    [ 17.364] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 17.364] (II) Loading sub module "ramdac"
    [ 17.364] (II) LoadModule: "ramdac"
    [ 17.364] (II) Module "ramdac" already built-in
    [ 17.366] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 17.366] (==) NVIDIA(0): RGB weight 888
    [ 17.366] (==) NVIDIA(0): Default visual is TrueColor
    [ 17.366] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 17.368] (**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
    [ 17.368] (**) NVIDIA(0): Enabling 2D acceleration
    [ 18.022] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 18.024] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 760 (GK104) at PCI:1:0:0 (GPU-0)
    [ 18.024] (--) NVIDIA(0): Memory: 2097152 kBytes
    [ 18.024] (--) NVIDIA(0): VideoBIOS: 80.04.c4.00.60
    [ 18.024] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 18.033] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 760 at PCI:1:0:0
    [ 18.033] (--) NVIDIA(0): CRT-0
    [ 18.033] (--) NVIDIA(0): DFP-0
    [ 18.033] (--) NVIDIA(0): Samsung S27B370 (DFP-1) (boot, connected)
    [ 18.033] (--) NVIDIA(0): DFP-2
    [ 18.033] (--) NVIDIA(0): DFP-3
    [ 18.033] (--) NVIDIA(0): DFP-4
    [ 18.033] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 18.033] (--) NVIDIA(0): DFP-0: Internal TMDS
    [ 18.033] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
    [ 18.033] (--) NVIDIA(0): Samsung S27B370 (DFP-1): Internal TMDS
    [ 18.033] (--) NVIDIA(GPU-0): Samsung S27B370 (DFP-1): 340.0 MHz maximum pixel clock
    [ 18.033] (--) NVIDIA(0): DFP-2: Internal TMDS
    [ 18.033] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
    [ 18.033] (--) NVIDIA(0): DFP-3: Internal TMDS
    [ 18.033] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
    [ 18.033] (--) NVIDIA(0): DFP-4: Internal DisplayPort
    [ 18.033] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
    [ 18.033] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 18.033] (**) NVIDIA(0): device Samsung S27B370 (DFP-1) (Using EDID frequencies has
    [ 18.033] (**) NVIDIA(0): been enabled on all display devices.)
    [ 18.035] (II) NVIDIA(0): Validated MetaModes:
    [ 18.036] (II) NVIDIA(0): "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
    [ 18.036] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
    [ 18.103] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X config
    [ 18.103] (--) NVIDIA(0): option
    [ 18.103] (--) Depth 24 pixmap format is 32 bpp
    [ 18.103] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 18.103] (II) NVIDIA: access.
    [ 18.106] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 18.106] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 18.106] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 18.106] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 18.106] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 18.106] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 18.106] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 18.106] (II) NVIDIA(0): Config Options in the README.
    [ 18.115] (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
    [ 18.327] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 18.327] (==) NVIDIA(0): Backing store enabled
    [ 18.327] (==) NVIDIA(0): Silken mouse enabled
    [ 18.328] (**) NVIDIA(0): DPMS enabled
    [ 18.328] (II) Loading sub module "dri2"
    [ 18.328] (II) LoadModule: "dri2"
    [ 18.328] (II) Module "dri2" already built-in
    [ 18.328] (II) NVIDIA(0): [DRI2] Setup complete
    [ 18.328] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 18.328] (--) RandR disabled
    [ 18.334] (II) Initializing extension GLX
    [ 18.334] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 18.892] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 18.892] (II) LoadModule: "evdev"
    [ 18.893] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.935] (II) Module evdev: vendor="X.Org Foundation"
    [ 18.935] compiled for 1.17.1, module version = 2.9.2
    [ 18.935] Module class: X.Org XInput Driver
    [ 18.935] ABI class: X.Org XInput driver, version 21.0
    [ 18.935] (II) Using input driver 'evdev' for 'Power Button'
    [ 18.935] (**) Power Button: always reports core events
    [ 18.935] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 18.935] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 18.935] (--) evdev: Power Button: Found keys
    [ 18.935] (II) evdev: Power Button: Configuring as keyboard
    [ 18.935] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event4"
    [ 18.935] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 18.935] (**) Option "xkb_rules" "evdev"
    [ 18.935] (**) Option "xkb_model" "pc104"
    [ 18.935] (**) Option "xkb_layout" "us"
    [ 18.961] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 18.961] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 18.961] (II) Using input driver 'evdev' for 'Power Button'
    [ 18.961] (**) Power Button: always reports core events
    [ 18.961] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 18.961] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 18.961] (--) evdev: Power Button: Found keys
    [ 18.961] (II) evdev: Power Button: Configuring as keyboard
    [ 18.961] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event3"
    [ 18.961] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 18.961] (**) Option "xkb_rules" "evdev"
    [ 18.961] (**) Option "xkb_model" "pc104"
    [ 18.961] (**) Option "xkb_layout" "us"
    [ 18.961] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
    [ 18.961] (II) No input driver specified, ignoring this device.
    [ 18.961] (II) This device may have been added with another device file.
    [ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event14)
    [ 18.962] (II) No input driver specified, ignoring this device.
    [ 18.962] (II) This device may have been added with another device file.
    [ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
    [ 18.962] (II) No input driver specified, ignoring this device.
    [ 18.962] (II) This device may have been added with another device file.
    [ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event16)
    [ 18.962] (II) No input driver specified, ignoring this device.
    [ 18.962] (II) This device may have been added with another device file.
    [ 18.962] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event0)
    [ 18.962] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 18.962] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
    [ 18.962] (**) Logitech USB Keyboard: always reports core events
    [ 18.962] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event0"
    [ 18.962] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
    [ 18.962] (--) evdev: Logitech USB Keyboard: Found keys
    [ 18.962] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
    [ 18.963] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/0003:046D:C31D.0001/input/input2/event0"
    [ 18.963] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 8)
    [ 18.963] (**) Option "xkb_rules" "evdev"
    [ 18.963] (**) Option "xkb_model" "pc104"
    [ 18.963] (**) Option "xkb_layout" "us"
    [ 18.963] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event1)
    [ 18.963] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 18.963] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
    [ 18.963] (**) Logitech USB Keyboard: always reports core events
    [ 18.963] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event1"
    [ 18.963] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
    [ 18.963] (--) evdev: Logitech USB Keyboard: Found absolute axes
    [ 18.963] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to exist.
    [ 18.963] (--) evdev: Logitech USB Keyboard: Found keys
    [ 18.963] (II) evdev: Logitech USB Keyboard: Forcing relative x/y axes to exist.
    [ 18.963] (II) evdev: Logitech USB Keyboard: Configuring as mouse
    [ 18.963] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
    [ 18.963] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.1/0003:046D:C31D.0002/input/input3/event1"
    [ 18.963] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 9)
    [ 18.963] (**) Option "xkb_rules" "evdev"
    [ 18.963] (**) Option "xkb_model" "pc104"
    [ 18.963] (**) Option "xkb_layout" "us"
    [ 18.964] (II) evdev: Logitech USB Keyboard: initialized for absolute axes.
    [ 18.964] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1
    [ 18.964] (**) Logitech USB Keyboard: (accel) acceleration profile 0
    [ 18.964] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
    [ 18.964] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
    [ 18.964] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
    [ 18.964] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
    [ 18.964] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 18.964] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
    [ 18.964] (**) Razer Razer DeathAdder: always reports core events
    [ 18.964] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
    [ 19.016] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
    [ 19.016] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
    [ 19.016] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
    [ 19.016] (--) evdev: Razer Razer DeathAdder: Found relative axes
    [ 19.016] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
    [ 19.016] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
    [ 19.016] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
    [ 19.016] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
    [ 19.016] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 19.016] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.0006/input/input22/event2"
    [ 19.016] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
    [ 19.016] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
    [ 19.017] (**) Option "AccelerationScheme" "none"
    [ 19.017] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
    [ 19.017] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
    [ 19.017] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
    [ 19.017] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
    [ 19.017] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 19.017] (II) No input driver specified, ignoring this device.
    [ 19.017] (II) This device may have been added with another device file.
    [ 19.017] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
    [ 19.017] (II) No input driver specified, ignoring this device.
    [ 19.017] (II) This device may have been added with another device file.
    [ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
    [ 19.018] (II) No input driver specified, ignoring this device.
    [ 19.018] (II) This device may have been added with another device file.
    [ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
    [ 19.018] (II) No input driver specified, ignoring this device.
    [ 19.018] (II) This device may have been added with another device file.
    [ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
    [ 19.018] (II) No input driver specified, ignoring this device.
    [ 19.018] (II) This device may have been added with another device file.
    [ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
    [ 19.018] (II) No input driver specified, ignoring this device.
    [ 19.018] (II) This device may have been added with another device file.
    [ 19.019] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
    [ 19.019] (II) No input driver specified, ignoring this device.
    [ 19.019] (II) This device may have been added with another device file.
    [ 19.019] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
    [ 19.019] (II) No input driver specified, ignoring this device.
    [ 19.019] (II) This device may have been added with another device file.
    [ 19.019] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 19.019] (II) No input driver specified, ignoring this device.
    [ 19.019] (II) This device may have been added with another device file.
    [ 213.516] (II) config/udev: removing device Razer Razer DeathAdder
    [ 213.556] (II) evdev: Razer Razer DeathAdder: Close
    [ 213.556] (II) UnloadModule: "evdev"
    [ 328.612] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
    [ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 328.612] (II) No input driver specified, ignoring this device.
    [ 328.612] (II) This device may have been added with another device file.
    [ 328.612] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
    [ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
    [ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 328.612] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
    [ 328.612] (**) Razer Razer DeathAdder: always reports core events
    [ 328.612] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
    [ 328.663] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
    [ 328.663] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
    [ 328.663] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
    [ 328.663] (--) evdev: Razer Razer DeathAdder: Found relative axes
    [ 328.663] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
    [ 328.663] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
    [ 328.663] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
    [ 328.663] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
    [ 328.663] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 328.663] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.000A/input/input26/event2"
    [ 328.663] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
    [ 328.663] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
    [ 328.663] (**) Option "AccelerationScheme" "none"
    [ 328.663] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
    [ 328.663] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
    [ 328.663] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
    [ 425.481] (II) config/udev: removing device Razer Razer DeathAdder
    [ 425.513] (II) evdev: Razer Razer DeathAdder: Close
    [ 425.513] (II) UnloadModule: "evdev"
    [ 425.536] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
    [ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 425.536] (II) No input driver specified, ignoring this device.
    [ 425.536] (II) This device may have been added with another device file.
    [ 425.536] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
    [ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
    [ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
    [ 425.536] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
    [ 425.536] (**) Razer Razer DeathAdder: always reports core events
    [ 425.536] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
    [ 425.590] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
    [ 425.590] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
    [ 425.590] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
    [ 425.590] (--) evdev: Razer Razer DeathAdder: Found relative axes
    [ 425.590] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
    [ 425.590] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
    [ 425.590] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
    [ 425.590] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
    [ 425.590] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 425.590] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.000B/input/input27/event2"
    [ 425.590] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
    [ 425.590] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
    [ 425.590] (**) Option "AccelerationScheme" "none"
    [ 425.590] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
    [ 425.590] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
    [ 425.590] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
    I've tried booting with the razer service disabled, I have to plug in my mouse again to use it when booting from Windows.
    Will edit with a failed boot very soon.

  • Neither Firefox nor the profile manager will start. In my task manager, the process is using 50% of my cpu but does nothing. I love browsing with firefox, how can I fix this?

    I've tried restarting my computer, the I tried uninstalling and reinstalling, then uninstalling, erasing all firefox files and folders, then restarting and reinstalling. I've also tried opening the profile manager to change my profile. After reinstalling a few times and trying to open the profile manager before launching firef0x, I got the firefox has crashed window and the process in the task manager is still using 50% of my cpu. The most recent expunge then re-download pops up a "file is corrupt" error and won't even install the program.

    Kill those processes that you are seeing, including any plugincontainer.exe, only once firefox has stopped running should you try to update it.
    Totally unexpected instances of firefox running may sometimes be the result of malware activity.

  • [Solved] systemd/user : how to exit window manager & stop X?

    Solution: Jump to https://bbs.archlinux.org/viewtopic.php … 6#p1262166
    I have set up my system to user systemd units to start my environment (roughly following the wiki).
    My problem is that I cannot exit my window manager (using “io (exitWith ExitSuccess)” in Xmonad): the service file starting the WM (xmonad) stops/exits with success, but the xorg.service keeps
    running. I need to switch to TTY2, systemctl --user stop xorg.service by hand, then switch to TTY1, execute Ctrl-C, and then I finally get my login
    prompt back.
    This is a bit annoying, and I don't know how to fix it.
    Here are the relevant (I think) unit files:
    # xmonad.target
    [Unit]
    Description=XMonad
    Wants=xorg.target
    Wants=xinit.target
    Requires=dbus.socket
    AllowIsolate=true
    [Install]
    Alias=default.target
    # xmonad.service
    [Unit]
    Description=Starts Xmonad
    Before=xinitrc.target
    After=xorg.target
    Requires=xorg.target
    [Service]
    ExecStart=/usr/bin/xmonad
    Environment=DISPLAY=:0
    Restart=no
    [Install]
    WantedBy=xmonad.target
    RequiredBy=xorg.service
    As you can see, I have added the RequiredBy=xorg.service line at the bottom, hoping that if xmonad.service exits, so should xorg.service - but to
    no avail.
    What do I have to do in order to completely stop X and get my login prompt on TTY1 back?
    EDIT: I am of course using the user-session-units.
    Last edited by Stalafin (2013-04-22 13:54:45)

    I know it's an old thread (not really old) but I have the same problem. The question is your solution doesnt work with me. It just give me an error like this:
    Failed to issue method call: The name org.freedesktop.login1 was not provided by any .service files
    Failed to issue method call: Process /bin/false exited with status 1

  • Firefox will close when i close the window but the process doesn't shutdown ever since i had updated to FF25

    I am running Win. 8.1 and had no issues with FF 24. Since upgrading to FF 25, firefox will appear closed when i close the window but the process doesn't shutdown. I have to go into Task Manager to end the process. I can then launch it again.

    SOLUTION (possible).
    Hi all. I had this problem as well. I currently run FF26. A week or so ago, out of nowhere FF wouldn't exit - the window would close but firefox.exe process would keep running in the background using about 50% of CPU. Not sure if it's connected, but just prior to that I clicked on a link on Facebook that looked like spam website, nothing happened, site loaded (sort of, all I saw was a msg - Please Wait...) but nothing happened, I have Eset antivirus and it monitors network traffic and files for viruses, so maybe it prevented my PC getting infected...
    So, I had this problem for a few days, was searching the net for solutions, but nothing seem to help. Then, just out of luck I did something that WORKED!
    Here's what I did. I noticed that svchost.exe was using a lot of CPU alongside with FF. I ran ProcessExplorer to see what might be connected to this process, the list was long and I didn't have any idea where to start, so what I did was - Right click on svchost process, choose Debug and dismiss the warning. In a few seconds svchost process quit and after that FF started closing properly.
    I had to re-enable all my plugins and themes I disabled prior, I also lost my history and preferences which I trashed in the process of searching for solution. But heck, it worked, hopefully for good. Now if someone could point out the real cause of this and fix it for everyone - that would be great. Cheers!

  • Strategy Management Business Process Scenarios in English language

    Hi,
    Can anybody (in  SAP organisation itself , hopefully) help in providing the English version of the file Strategy Management Business Process Scenarios (DE)?
    This file is currently available in German only at the service marketplace under SSM 7.5.
    Thanks.
    With regards,
    Milan.

    Milan,
    The reason that the German version was on the Service Marketplace is because it is currently in production and not available until October.
    I was able to go to implementationcontent.sap.com/bpr
    - Clicked on SAP BusinessObjects Strategy Management
    - Click Strategy Execution
    - Click Strategy Management 7.5
    - Click BUSINESS PROCESSES
    - New window opens with Scenario "Strategy Validation"
    - On the Documentation Tab you should see "Display Document"
    - Clicking on Display Document opens a new window with the doc
    The difficulty with being internal, is that I may have different authorization levels than you and so can't guarantee that this will work for you, but it is there right now in English. And I should mention that it took a long time for the new window with Document Tab to open, again your experience may be different, but be patient.
    Regards,
    Bob
    Edited by: Bob McGlynn on Sep 24, 2009 7:23 AM
    Edited by: Bob McGlynn on Sep 24, 2009 7:50 AM

  • Desktop Window Manager high CPU utilization

    I have several Windows 2012 servers that are showing high CPU utilization (70% or higher) coming from the Desktop Window Manager.  I do not have the Desktop Experience feature installed on these machines.  The interesting thing is that the process
    for dwm.exe does not show up as a service that I can stop or restart.  I've read through the various posts about re-registering dmw.exe so that the service shows up again, but nothing has worked.  Since these are application and file servers with
    no need for regular desktop use, I don't really need any fancy desktop graphics or performance.  I have the Advanced Performance Options set to 'Background services'.  Can anyone tell me how to stop dwm.exe or at least reduce it's CPU footprint?
    Thanks,
    Joe

    Hi Joe,
    Based on my research, On Windows 8 and Windows Server 2012, DWM is used at all times and cannot be disabled.
    For more detailed information, please refer to this article:
    Desktop Window Manager is always on:
    To troubleshoot the high usage of CPU, I would like to recommend to follow this article to collect and analyse the relevant log files and dump files:
    Troubleshooting High CPU performance issues - Part 1
    If you want to analyse the dump file, I also recommend you can open case and contact Microsoft support.
    I hope this helps.

  • Themable Window Manager

    I have been switching window managers for a while now and have gotten to where I have a specific set of requirements and no contenders.  I was wondering if anyone could recommend some apps.
    I am looking for a window manager that is almost fully themable.  By this I mean full transparencies and the ability to create anything as a window border.  If is not important for me to have the window title on the sides, that aspect of theming is not too important.
    I currently am using openbox and I love every aspect of it except for the limitations on the themes.  I need the window manager to do the following things:
    keybindings (fully customizable).
    Modular.  I don't want to pull in (lots of) desktop specific libraries (IE Qt OK, KDE not-OK)
    Provide nothing but a window manager (unless it is easily turned off)
    Multiple desktops.
    I'm going to add a couple of thinks I would also like to see but shouldn't stop you from posting any,
    Not too fat
    Stacking
    Please post even if they don't fill all of the requirements and I would like to have a little explanation of why you like each window manager.  (Please no "fluxbox ftw!")

    I'm going to start off with my findings.  Many of my explanations are short and most of them are only highlighting the problems.  Please don't accuse me of hating any of the window managers as I respect each an every one.  Many just aren't for me.
    KWin really wants to find and start KDE.  Also can't bind modifier keys (Qt limitation).  KWin is also quite slow due to the effects.  If you turn them all off it speeds right up and takes a lot less memory.  Unfortunately it is still linked to the graphics libraries though so it takes a long time to start.
    Metacity has too few options.  (For example no desktop wrap around).  This is not a progress issue but a design philosophy.  Hence the logo "A WM for old people".  It does have great theming capabilities and does it's job very well.  I does not start up any gnome processes (as far as I noticed).
    Openbox and fluxbox have the theming problems.  They are great window managers though.  Openbox is simple and elegant.  The config file is awesome.  Openbox also has a strong user base if you don't want to write your own themes.  Fluxbox has a ton of extra features if you like them (I don't) such as grouping.
    xfwm wants some settings daemons. (not too bad)  I does have nice themes and is quite lightweight. It also has all of the common features.
    mutter won't start. (I'm looking into this)
    eggwm won't start (No errors or anything)  It will also probably have the same Qt problem as KWin.
    e16 is nice and themable (although it is a ton of work) but it puts too much stuff on my desktop.
    Last edited by youarefunny (2012-02-11 03:15:51)

  • Window Manager\Window Manager Group

    Based on customer requirements we need to set Bypass traverse checking rights for our Server 2012 boxes. In doing so we noticed that there is a user or group named Window Manager\Window Manager Group. I have seen references in other threads to this user
    pointing to the SID (S-1-5-90-0), but this is not documented anywhere on Microsoft website that I can find. I used Powershell to list all of the users, and I do not see a user or group on my Server 2012 box that matches this.
    Given no response from Microsoft and no documentation, I cannot effectively decide what I should do with this.
    It looks kind of shady that we are granting rights to a SID / Account that we cannot see, so I am wondering if this is some remnant for a part of Server 2012 that didn't get deployed when the code was released to manufacturing. Can some please confirm that
    it is OK to drop this user or group (not even sure which one it is) from the Bypass Traverse Checking user right?

    Hi,
    Based on my research,it is not recommended to remove the group ‘Window manager\Windows manager group’ from Bypass traverse checking or Increase a process working set.
    • Both the above user rights are utilized in windows 8/2012 for performance impacts.
    • The above mentioned group cannot be added manually to any other groups or no user can be a part of it as it does not resolve in object picker. We cannot even add ACLs to this group.
    • Due to above reasons, it is not a security breach in your environment.
    This group is a virtual group that is present on every Windows 2012 machine. The DWM.EXE that is used to manage he desktop experience runs under the security context of an account under this group and this is used to provide less privilege to the DWM.EXE.
    As such this is not documented anywhere in any of public documents. This is a design decision made by the product team which is part of the architecture of the OS. As such the practice is not to remove this group from both the user rights assignment mentioned.
    How Bypass traverse checking affects performance:
    When you try to access c:\foo\bar\baz\bletch\george.txt, “the rules” say that you need to confirm that the user has traverse access to:
              C:\foo
              C:\foo\bar
              C:\foo\bar\baz
              C:\foo\bar\baz\bletch
    If you didn’t have the “bypass traverse checking” privilege, the system would have to open each of these directories in turn and do an access check to make sure you had access to all the intermediate nodes in the path to the file.  With bypass traverse
    checking, the filesystems skip all those checks and just check to make sure you have your desired access to the file you’re opening.
    How increase a process working set affects performance:
    This settings controls who can increase the working set of a process when in memory. Working set is the data that is resending in the Ram that is visible to the process. This helps in expanding the memory a process stores in RAM thereby reducing page faults
    (paging out memory to virtual memory which will induce delays of copying the memory back to RAM).
    Given the above reasons, I strongly recommend you not to remove ‘Windows manager\Windows manager group’ from Bypass traverse checking as well as increase a process working set user rights assignment.
    Thanks.

  • How to Install Windows Management Framework 4.0 on Server 2008R2 Core

    I am trying to upgrade Server 2008R2 Core to PowerShell 4. I have carried out following steps.
    1. Installed .NET Framework 4.5.1 (NDP451-KB2858728-x86-x64-AllOS-ENU)
    2. Enabled WoW64-ServerCore, WoW64-NetFx2-Support, WoW64-NetFx2, WoW64-PowerShell
    3. Installed Windows Management Framework 4.0  (Windows6.1-KB2819745-x64.msu)
    WMF installation shows that it was successful ("Windows update "Update for Windows (KB2819745)" was successfully installed.")
    However when I restart the server following shows up on the event log ("Package KB2819745 failed to be changed to the Installed state. Status: 0xd00000bb.")
    This same process work on Server 2008R2 full version.
    Has anyone seen this before?

    Hi Aka Nugawela,
    The .NET Framework 4.5 and its point release is supported in the Server Core Role with 2008R2 SP1 or later, could you try to install SP1 then try again.
    The related KB:
    .NET Framework System Requirements
    https://msdn.microsoft.com/en-us/library/8z6watww(v=vs.110).aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • CDE Window Manager  configuration problem (Sol 8)

    Hi
    I have a strange problem with CDE. After having a proper PC instalation done, as I log in the CDE I get black background and only 2 windows ( a kind of help window and the File Manager) The windows don't have title bars, cannot be moved ot whatever. Now, I seems to me that the window manager failed to start. Since I'm new to Solaris, can anybody give me a hint where I can find the configuration scripts and error logs.
    Thanks
    Val

    if it were me I'd check /var/dt/Xerrors (Xservers log file)
    $HOME/.dt/errorlog & startlogs for clues ... this is where CDE would log
    problems.
    However you mentioned PC so I'll assume you are using ReflectionsX,
    Exceed
    or similar, all come with a log file and trace utility via the Xconfig
    screen
    which maybe worth your while looking into ?
    As to the window manager failing to start .... the process is called
    dtlogin
    and on the Solaris server you should see one parent process + 1 child per
    remote display if things are working correctly.
    Gotcha's : most likely problems are caused by either Fonts - check PC
    Xemulation log files or hostname resolution problems.

  • Looking for a light weight tiled window manager.

    Hello everyone,
    I am looking for a light weight window manager with tile support.  I am a programmer by hobby and I like to be able to maximize my screen real estate.
    I love hot key and terminal use it just speeds up the process.  I don't however want it to have a huge scripting learning curve.  Currently I am in the process of learning Android development so having to learn a new scripting language on top of it won't make matters better.
    Currently I am comfortable with bash, and python.  I can also do some work in perl but not super fluent with it yet.
    It would also help if it has dual monitor support.  My main monitor is a 23" LCD max res 1920x1080 and my second monitor is a 17" LCD max res 1440x900 until I get around to picking up another 23".

    Runiq wrote:
    Search first, post later:
    http://wiki.archlinux.org/index.php/Lig … plications
    another good wiki page is the tiler comparison, the chart shows vitals, like what they are configured in
    http://wiki.archlinux.org/index.php/Com … w_Managers
    Last edited by hume's doona (2010-10-08 12:17:51)

  • Musca (Tiling Window Manager)

    I've just come across this tiling window manager which seems to be very new, I've seen no mentions of it anywhere other than wikipedia, so I thought I'd download it and try it out. You can find it here, along with source and probably all the info you could possibly need.
    "A simple tiling window manager for X, with features nicked from ratpoison and dwm"
    http://aerosuidae.net/musca.html
    It looks to be alot like dwm in the configuring aspect, (ie. edit config.h and compile), although it also has a start file which can be used to run some internal commands.
    Anyway I've only been using it for literally the time it took me to write this post, but I thought I'd suggest that others give it a shot! I'm certainly enjoying it so far

    aerosuidae wrote:Thanks.  I've never even looked at the process for creating a package for AUR.  If you are volunteering to maintain this (? ), get on the mailing list to hear about new releases: http://mail.aerosuidae.net/mailman/list … suidae.net
    Joined
    aerosuidae wrote:No idea.  Out of interest: Why do you think it better it gets run from $HOME?
    The PKGBUILD becomes easier. Also if its in $HOME, you can make as many changes as you want and run it. You can even change the path of the executable, if you want. One disadvantage is that if you have multiple users on the computer, you will have to install for each user.
    aerosuidae wrote:Oh.  I rather like dates as they're IMHO more informative and useful than a number.  Still, I can live with that.
    Well if you use the dates, I will change the build method for every release. No big deal. Let me know which way you prefer.
    aerosuidae wrote:
    Inxsible wrote:The trouble with your shortcuts is, that I use most of those shortcuts in my Openbox setup --and in my dwm. like Mod4+r - to start rTorrent etc. I guess, I will just have to relearn all my shortcuts and not use Mod4 in the shortcuts for starting apps.
    No, don't let Musca dictate to you how to work. Customize the combinations that clash using .musca_start or config.h
    Is there a limit to how many keybindings you can add?
    I currently have all of these.
    struct keymap keymaps[] = {
    { "Mod4+Shift+h", "hsplit 1/2" },
    { "Mod4+Shift+v", "vsplit 1/2" },
    { "Mod4+Shift+r", "remove" },
    { "Mod4+Shift+o", "only" },
    { "Mod4+Shift+k", "kill" },
    { "Mod4+Shift+c", "cycle" },
    { "Mod4+Left", "focus left" },
    { "Mod4+Right", "focus right" },
    { "Mod4+Up", "focus up" },
    { "Mod4+Down", "focus down" },
    { "Mod4+Next", "use (next)" },
    { "Mod4+Prior", "use (prev)" },
    { "Mod4+Tab", "screen (next)" },
    { "Mod4+Shift+w", "switch window" },
    { "Mod4+Shift+g", "switch group" },
    { "Mod4+x", "shell" },
    { "Mod4+Shift+m", "command" },
    { "Mod4+Shift+d", "dedicate flip" },
    { "Mod4+Shift+a", "catchall flip" },
    { "Mod4+Shift+u", "undo" },
    { "Mod4+Shift+s", "stack flip" },
    { "Mod4+Control+Left", "resize left" },
    { "Mod4+Control+Right", "resize right" },
    { "Mod4+Control+Up", "resize up" },
    { "Mod4+Control+Down", "resize down" },
    { "Mod4+a", "exec lxappearance" },
    { "Mod4+b", "exec recorder" },
    { "Mod4+c", "exec conky" },
    { "Mod4+e", "exec easytag" },
    { "Mod4+f", "exec pcmanfm" },
    { "Mod4+g", "exec geany" },
    { "Mod4+t", "exec urxvt -bg black -fg white" },
    If I add one more, the pkg builds fine, installs too...but when I log in, X starts for a microsecond and bombs. Here's dmesg | tail and it says that musca segfaults.
    agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
    nvidia 0000:01:00.0: putting AGP V2 device into 4x mode
    musca[10748]: segfault at 41 ip b7eb2aa8 sp bfcb5d6c error 4 in libc-2.9.so[b7e40000+140000]
    agpgart-intel 0000:00:00.0: AGP 2.0 bridge
    agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
    nvidia 0000:01:00.0: putting AGP V2 device into 4x mode
    musca[11554]: segfault at 41 ip b7e7faa8 sp bfc82d2c error 4 in libc-2.9.so[b7e0d000+140000]
    agpgart-intel 0000:00:00.0: AGP 2.0 bridge
    agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
    nvidia 0000:01:00.0: putting AGP V2 device into 4x mode
    Just wanted to let you know. If its a bug, I will open it on your launchpad bugtracker.
    Last edited by Inxsible (2009-03-13 06:28:52)

Maybe you are looking for