CS4 Windows window management

Upon upgrading to CS4 for Windows, I find a new, fatiguing "feature" of PS. Any time I drag a file from a Windows directory into Photoshop, it immediately opens as a maximized window. Only by right-clicking on the tab and choosing "Open in New Window" option can I get the document open in a free-floating window.
I've looked into preferences, but can't seem to find an option for having documents open in scaled view. In that I work with dozens of images at once, this feature is a pain.
Suggestions?
Thanks!
Tim

Instead of dragging from Explorer, use the right-click context menu to open it.
If it's a PSD or TIFF you only have to double-click it.
I think drag and drop is always error-prone, especially if you have to "aim" at the drop zone.

Similar Messages

Dreamweaver CC trial - no menu "commands - manage extensions" or "window - manage commands"

Hi,
I just installed the trial of DW CC as well as Extension Manager CC. I activated some extensions (zxp) but I don't see an extension bar or a menu "commands - manage extensions", both I know from DW CS4. Also no "window - manage extensions". Is this a limitation of the trial? I would really need to test my extensions.
Thank you.

Hi spryotone:
See Dreamweaver Help | Add-Ons for installing extensions in DW CC 2014. If you have problems viewing your add ons later, see Newly installed add-ons not loaded | Dreamweaver CC 2014 to troubleshoot.
Thanks,
Preran

Upgrade from InDesign Mac to InDesign CS4 Windows, Is this possible?

Hi all, I have Indesign CS2 Mac, now I am switching to Windows platform and i want to upgrade to Indesign CS4 Window. Is this possible from my copy and serial number of InDesign CS2 Mac.

MWHebert wrote:
You had better hurry, as when CS5 comes out (sometime in April or early May) there is a very short grace period to do this. I found out the hard way and was too late and had no other choice than to pay to get CS4.
It's not certain when InDesign CS5 might be released, until Adobe makes a formal announcement. You might want to discuss with an Adobe customer service SUPERVISOR whether you can make the cross-grade after CS5 is formally announced (not released, just announced), and also ask the SUPERVISOR whether your purchase of the cross-grade after the announcement will qualify for a free upgrade to CS5.
Sometimes policies change, but, I believe that there's a period after announcement of a new release, before it's shipping, that by purchasing the outgoing release, you get a free upgrade to the announced release. I think there's a charge for a boxed product, but not for the downloaded product.
I'm suggesting SUPERVISOR, because information of this kind often isn't made completely clear to regular customer-support folks. If a supervisor can't give you certain info, ask for the supervisor's MANAGER. Get the name of the person who gives you the info, so you have someone to work with if a problem arises.
Buying an expiring product in the brief period between announcement of the next release and its actual shipping date, usually results in such a free upgrade. It's important for you to get accurate information about whether upgrading a product in this period works the same way..
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Maximize Application without Window Manager

What I'd like to do is use xwininfo and wmctrl to maximize an application in X without a window manager. Here is what I've worked out:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
MAXIMIZE_ID=$(xwininfo -root -child | grep "st-256color" | grep -o "^[[:space:]]*0x[[:alnum:]]*" | grep -o "0x[[:alnum:]]*")
MAXIMIZE_WIDTH=$(xwininfo -root | grep "Width" | grep -o "[[:digit:]]*")
MAXIMIZE_HEIGHT=$(xwininfo -root | grep "Height" | grep -o "[[:digit:]]*")
while [ "$MAXIMIZE_ID" = "" ]
do
MAXIMIZE_ID=$(xwininfo -root -child | grep "st-256color" | grep -o "^[[:space:]]*0x[[:alnum:]]*" | grep -o "0x[[:alnum:]]*")
if [ "$MAXIMIZE_ID" != "" ]
then
wmctrl -i -r $MAXIMIZE_ID -e 0,0,0,$MAXIMIZE_WIDTH,$MAXIMIZE_HEIGHT
fi
done &
exec st
As intended it maximizes the st terminal. However, the terminal simply hangs there, I can provide it with no input, any clues as to what I'm missing and/or doing incorrectly? I realize st uses the geometry parameter, I'm only using it here as an example application as not all applications support that parameter.
Last edited by grimpirate (2014-08-12 19:20:00)

It's much more complex than that. Wmctrl requires a EWMH compliant window manager. Many of the lightest weight WMs are not EWMH compliant.
Is this just for st, or do you want all windows maximized? Does st have a 'geometry' flag?
You could write a WM that does nothing but fullscreen every window that is mapped in about a dozen lines of code. Note, however, that without a WM, windows will generally not properly be assigned the input focus - one result is that cursors on most terminals will remain 'hollow'. For the cost of one or two more lines of code, this new WM could also set input focus appropriately.
EDIT: st does have a geometry flag, just use that.
Also, your 'grep | grep' pipe could just be "awk '/Width/ { print $2;}'", or two get both width and height in one go:
xwininfo -root | awk '/Width/ { printf "%s", $2;} /Height/ {printf "x%s", $2;}'
Though this wouldn't be quite right for a st geometry string as that takes rows and columns, not pixels.
EDIT2: your solution will also fail miserably for two other reasons. There is not point in initializing the MAXIMIZEID variable before the loop starts - because if there actually are any windows there, the while loop will never run. Also, without a sleep command, or something, all that while loop will be very good for will be to turn your cpu into a frying pan (100% cpu use -> heat).
Here's a very plain WM that will do the same thing without melting your CPU:
#include <X11/Xlib.h>
int main(void) {
Display *dpy;
if(!(dpy = XOpenDisplay(0x0))) return 1;
XEvent ev;
int scr = DefaultScreen(dpy);
int sw = DisplayWidth(dpy, scr);
int sh = DisplayHeight(dpy, scr);
Window w, root = RootWindow(dpy, scr);
XSelectInput(dpy, root, SubstructureRedirectMask);
while (!XNextEvent(dpy, &ev)) {
if (ev.type == MapRequest && (w=ev.xmaprequest.window)) {
XMoveResizeWindow(dpy, w, 0, 0, sw, sh);
XMapWindow(dpy, w);
XSetInputFocus(dpy, w, RevertToPointerRoot, CurrentTime);
XFlush(dpy);
return 0;
Last edited by Trilby (2014-08-13 13:03:59)

WINDOWS MANAGEMENT FRAMEWORK 4.0 - A required certificate is not within its validity period

Hello,
I can't figure out if this is because the Root Certificates were updated in April 2014 then apparently expired by Microsoft or if the PowerShell installer signed this file with a bad software release signature??
We were deploying PowerShell 4.0 (Windows6.1-KB2819745-x64-MultiPkg.msu) with ConfigMgr 2012 with a dependency of .NET Framework 4.5.1. Everything was working fine until sometime around April 24 (exact date unknown). Now any
Win 7 SP1 machines I try to update will not install WMF 4.0. They installed .NET 4.5.1 without any trouble..
The digital signature on it it states it was signed Sept 27 2013 and the certificate expires 4/24/2014.
Even if we change the system clock to April 1 2014 it still will not install.. but this shouldn't matter anyway. They just can't sign new software with that certificate.. surely I can install it..
As for a log... If I run as C:\Windows\ccmcache\3>wusa.exe Windows6.1-KB2819745-x64-MultiPkg.msu /log:c:\windows\ccmcache\3\broken.txt
In the broken.txt I see:
Install Worker.01194: Operation Result Code of the installation: 0X4 HRESULT of the installation: 0X80240022 Operation
Result Code of the update:0X4 HRESULT of the update: 0X800b0101
Install Worker.01243: Failed install update Update for Windows (KB2819745)
Install Worker.01287: Exit with error code 0X800b0101 (A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.)
WINDOWS MANAGEMENT FRAMEWORK 4.0 FOR MICROSOFT OPERATING SYSTEM PRODUCTS
Windows6.1-KB2819745-x64-MultiPkg.msu
I also see this same event information in Setup event log..
I don’t know what to do here. Anyone else having this problem?

Hi,
Have you ever seen this article?
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server
http://support.microsoft.com/kb/2328240/en-us
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

New window manager (with prototype!) [wmii-like] --- looking for help

I have a prototype for a new window manager in the style of wmii. It is called
cakewm. I currently have a prototype version implemented in pygame, and would
like help moving this to use X---making it a real window manager.
Disclaimer: I have a very limited knowledge of X11 and window manager
development. The most I've done is add a couple new features to wmfs.
To get the code
> git clone git://github.com/saikobee/cakewm.git
Then run main.py. cakewm depends on pygame.
Upon running, press Alt-Enter to fullscreen cakewm and intercept keybinds, or
Alt-Space to just intercept keybinds. Press Alt-Esc to quit. The window
manager related keybinds are listed in the file binds.conf.
Config note: <WSCA-x> means Windows-Shift-Control-Alt-x
Implementation note: pypixel.py is a large and mostly useless dependency. I
forked a library I made previously rather than coding straight in pygame.
cakewm's goals are to be similar to wmii, but with more functionality, easier
configurability, and saner defaults.
- cakewm is fully functional using the keyboard. Mouse support can come later.
- cakewm provides 9 workspaces per monitor.
- cakewm manages each workspace as a group of columns. Each column is like a
wmii default split, except each window can have other windows "stacked" on
top of or behind it.
- cakewm manages column sizes (and window sizes within columns) using a
master/slave paradigm, with the ability to adjust the size ratios.
- cakewm's configuration file is simple key=val pairs, with the ability to
include other files like in C.
- cakewm has a slightly larger emphasis on window decorations (adjustable
size---even in tiled mode) and themes (nothing bloated, like pixmaps or
gradients---it's all still simple colors).
- cakewm will have proper support for international text (Japanese text in
window titles or the wmii status bar generally render as boxes) through the
use of a more advanced text library such as Pango.
Please let me know if you have comments, questions, or concerns. If you are
interested in helping, get in touch with me. If you know somewhere better to
look for volunteers, please let me know.

m4co wrote:
Wow is this forum active. Makes me feel welcome here
The thing about wireless, I actually like command line, but there are a few things that are worth having a applet or something.
And wireless is one of those. I guess I can take a look on wicd.
It's a good idea to have compiz as the WM actually. Would it be lightweight to have it like that?
Is there anybody here that uses compiz as a WM?
For the xfce4-panel, is it possible to get transparency on it? That's probably the only thing holding me back with xfce4-panel.
If "able to run compiz" wasn't a requisite, what other WM would you suggest for my "profile" ?
I would like to hear other users opinions who like to customize everything on a WM.
I recommend running Compiz by itself. There is a good wiki page on it in the Arch wiki. Some apps you'll want to go with it are:
LXAppearance --change GTK/icon theme
Feh or Nitrogen --Set Wallpaper
Xfce4-panel --The lightest one that works with Compiz properly
Or, if you don't want a panel: stalonetray
Compiz-deskmenu --For a customizable right-click main menu
Gmrun --Run dialog (Alt+F2 in most DEs)
And this helped me a lot.
Thank you all for the replies. I appreciate.
Xfce4-panel can have transparency. The only problem is that everything become transparent: text, icons, everything.
I use Compiz as a standalone WM and it is much lighter than DE+Compiz. My Compiz setup uses about 30MB(out of 1GB) more RAM than my Openbox setup (which are both the same except for the WM).

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.

Looking for a new window manager

Hello all!
My first post here and I'd like to share a little discussion.
So I have this idea of "perfect desktop" in my mind:
- It must be lightweight
- Very clean.
- No menus
- Highly customizable.
- Able to run compiz
I've come to Enlightenment 17 on Fedora and that was close to perfection.
I just loved, everything I wanted. Nice animations, clean, and man you can change absolutely everything there.
But then I started getting frustrated with bugs since it's not stable and I had to move on.
Then I came to XFCE4.6. Great, fairly customizable. Fewer bugs that you can live with it.
And I could run compiz. I just love using compiz here and got used to it. I use compiz to be more productive with the desktops , shortcuts and just a few animations.
But I few like trying something new. XFCE is just here for a lack of a better choice. It doesn't feel it fits me.
So maybe someone could recommend a new Window Manager for me?
I am interested in OpenBox and FluxBox.
I'm astonished with some OpenBox screenshots where you don't have anything, just the right-click menu and some apps running.
That's exactly what I would want.
But then, things like NetworkManager. How do you connect to internet (wireless)? On the command line?
What if I'd need to scan for open wireless networks..everything would have to be on command line?
Laptop Battery widget that warns when it's almost over, etc..
Are those WM really that raw or am I missing a few hidden goodies?
Would LXDE be a better choice?

m4co wrote:
Wow is this forum active. Makes me feel welcome here
The thing about wireless, I actually like command line, but there are a few things that are worth having a applet or something.
And wireless is one of those. I guess I can take a look on wicd.
It's a good idea to have compiz as the WM actually. Would it be lightweight to have it like that?
Is there anybody here that uses compiz as a WM?
For the xfce4-panel, is it possible to get transparency on it? That's probably the only thing holding me back with xfce4-panel.
If "able to run compiz" wasn't a requisite, what other WM would you suggest for my "profile" ?
I would like to hear other users opinions who like to customize everything on a WM.
I recommend running Compiz by itself. There is a good wiki page on it in the Arch wiki. Some apps you'll want to go with it are:
LXAppearance --change GTK/icon theme
Feh or Nitrogen --Set Wallpaper
Xfce4-panel --The lightest one that works with Compiz properly
Or, if you don't want a panel: stalonetray
Compiz-deskmenu --For a customizable right-click main menu
Gmrun --Run dialog (Alt+F2 in most DEs)
And this helped me a lot.
Thank you all for the replies. I appreciate.
Xfce4-panel can have transparency. The only problem is that everything become transparent: text, icons, everything.
I use Compiz as a standalone WM and it is much lighter than DE+Compiz. My Compiz setup uses about 30MB(out of 1GB) more RAM than my Openbox setup (which are both the same except for the WM).

[SOLVED!] KDE 4.11 - Window Manager seems not to be running?

Greetings,
I still seem unable to fix the fact that systemsettings will run. However it will run if you do kdesu systemsettings.
Doing so I started checking around in it and thought I'd look at the desktop effects, when I was greeted with this:
So, I am guessing that the window borders and buttons are a figment of my imagination....
This is after me pretty much starting over with KDE, removing the .kde and .kde4 folders.
Help?
Edit: That pic seems to not link right. Yay. Basically it says that effects can not be activated or whatever because a window manager seems not to be running. The irony of it is you can see the fact that there are window borders and buttons and such, evidence of a WM...
I wonder if there is something here that is related to me not being able to run systemsettings... yet systemsettings will run fine in any other environment - including Gnome Shell.
Another thing, KDE 4.11 ran great in testing and kde_unstable. Once it went to extra, things happened. I find that odd. Maybe something is missing on my end that most archers already have?
Edit2: fixed image link
Last edited by mythus (2013-08-25 20:49:38)

No omeringen, Nvidia user.
I can try again Thaodan since I've had some updates come through (and weeded out some dot files). Last time I tried I saw OpenGL 2 selected. Trying to change to 3 or anything else also got the screenshot in my OP.
I'll log into KDE and see if it still does the same, after a brief check for last minute updates.
EDIT: OK, so I can mark this as solved. I found an odd dot file, who's name excapes me but deals with kde sessions, just sitting around in the home folder. Once I deleted it and restarted, I found that not only System Settings finally ran again as a user, but I could also change and apply desktop effects. Peculiar. I thought that maybe it was a dot file that was causing the problem, that wasn't in the .kde or .kde4 folder. It just took finding it and removing it.
I wish I knew more to tell, but this at least solves my issue, and the issue with the non-running-as-user system settings I had posted in another thread (thinking that they were separate events. Thanks again for all your help guys!
Last edited by mythus (2013-08-25 20:49:05)

Desktop Window Manager Service on Windows 7 Starter - Any Reason to Leave It Running?

Hello everyone,
-As per title, I'd like to know whether is it better to turn off Desktop Window Manager Session Manager (UxSms) service on Windows 7 Starter - or not. I mean changing the service's default startup type from Automatic to Manual (or Disabled).
-In Windows 7 Starter, the Aero theme and desktop composition are not available at all (not even a basic/partial one), so letting Desktop Window Manager (DWM.exe) to continuously run is useless as it does absolutely nothing. Is my deduction correct?
-All opinions and suggestions are welcomed, thank you very much.
Regards,
-Musafir_86.

Please read the information posted @
http://msdn.microsoft.com/en-us/library/windows/desktop/aa969540%28v=vs.85%29.aspx
Desktop Window Manager
The desktop composition feature, introduced in Windows Vista, fundamentally changed the way applications display pixels on the screen. When desktop composition is enabled, individual windows no longer draw directly to the screen or primary display
device as they did in previous versions of Windows. Instead, their drawing is redirected to off-screen surfaces in video memory, which are then rendered into a desktop image and presented on the display.
Desktop composition is performed by the Desktop Window Manager (DWM). Through desktop composition, DWM enables visual effects on the desktop
as well as various features such as glass window frames, 3-D window transition animations, Windows Flip and Windows Flip3D, and high resolution support.
The Desktop Window Manager runs as a Windows service. It can be enabled and disabled through the Administrative Tools Control Panel item, under Services, as Desktop Window Manager Session Manager.
Many of the DWM features can be controlled or accessed by an application through the DWM APIs. The following documentation describes the features and requirements of the DWM APIs.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

PHOTOSHOP CS4, windows 7, error 148:3Cannot uninstall or reinstall from disk?

PHOTOSHOP CS4, windows 7, error 148:3Cannot uninstall or reinstall from disk?

PHOTOSHOP CS4, windows 7, error 148:3Cannot uninstall or reinstall from disk?

Collection query for computers with windows management framework 3.0

Hi,
collection query for computers with windows management framework 3.0, but I cant found a way. I cant see that it is in the inventory data for SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName.
So any way to get computers with windows management framework 3.0?
/SaiTech

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SoftwareProduct on SMS_G_System_SoftwareProduct.ResourceId
= SMS_R_System.ResourceId where SMS_G_System_SoftwareProduct.ProductName like "Windows Management Framework 3.0%"
That won't work because as mentioned, it doesn't appear in ARP.
Torsten's suggestion will work or you can resort to software/hardware inventory using the info at
http://serverfault.com/questions/555100/methods-to-detect-version-of-windows-management-framework
Jason | http://blog.configmgrftw.com

[Solved]Cannot execute i3 window manager

I installed i3 tiling window manager along with kde(kde could be executed),and follow the step written in i3's wiki:
Edit ~/.xinitrc and add:
exec i3
exec i3 -V >>~/.i3/i3log >&1
and cp /etc/i3/config ~/.i3/config,after these steps I still cannot execute i3 wm, could anyone tell me what I missed?
appreciate your reply.
Last edited by tomisacat (2012-07-20 05:14:29)

hesse wrote:
tomisacat wrote:
I installed i3 tiling window manager along with kde(kde could be executed),and follow the step written in i3's wiki:
Edit ~/.xinitrc and add:
exec i3
exec i3 -V >>~/.i3/i3log >&1
You should add just one of the above exec statements by the way, and it should be on the last line in ~/.xinitrc. The second line is preferred if you want to log messages from i3 while it's running. To start a window manager manually from a console use
xinit /full/path/to/i3
Thank you,it seems worked.

[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

Window manager that can scale individual window or virtual desktop?

Xfig doesn't work well on high DPI screens, especially for users whose vision is not that great. The problem is that there is no configuration option to scale elements such as lines.
I see two ways to solve the problem:
Scale the Xfig window.
Scale the virtual desktop on which Xfig is running. Other applications would be running on virtual desktops that are not scaled.
Following a suggestion in the awesome mailing list, I looked into Wayland plus a compositing window manager. However, XWayland, the X compatibility layer, has issues with Xfig. So I guess that for now I’m stuck with X.org, and a window manager compatible with the X composite extension.

Possible solutions:
Pervert: Set up a virtual machine just for Xfig, then use xrandr to scale the desktop inside of the virtual machine.
Saner: Run Xfig in a VNC server (or NX), then connect with a client that supports scaling, e.g. gtk-vnc.
Could be nice: Run Xfig within Xephyr, an X server that runs in a window within X. However, scaling with xrandr doesn't work.
Untested: Use the Compiz Ezoom plugin to scale part of the screen. One would somehow need to prevent windows from being positioned outside of the zoomed area, and also restrict mouse movement.
Last edited by feklee (2015-04-06 11:27:07)

Looking for "Window Manager\Window Manager Group" SID

Hi. I am trying to find the SID for "Windows Manager\Window Manager Group". If anyone has that, I'd appreciate it. I am trying to build my "base build" Security Template for Server 2012, and I need to assign the default User Rights to that group, as it is
out-of-the-box. Problem is that the GUI does not accept that group name as valid, but I can see that the group is assigned user rights in the Local Security Policy. I typically just use a file ACL to do this (add the ACE and then run
icacls to get the SID), but that group name is not valid within that tool either. My guess if that this new "Windows Manager\Window Manager Group" group is a well-known SID. Thanks.

Ironically the SID is not listed on Microsoft's web page for well know
SIDs. I also noticed that when I dump the local users using powershell, every group and user is listed that I would expect to see, but this one is not in that list. It seems like it should be pretty easy for Microsoft to say what this does and when it can
be safely removed...
I figure one of two possibilities. Either this only matters when a specific feature is installed / active, or it is some remnant from development for a feature or implementation that didn't make it into the release to manufacturing. What ever the case it
would be nice if we could get clarification.

CS4 Windows window management

Similar Messages

Maybe you are looking for