Using kwin 5 as lxqt window manager
Hello,
Is it possibile to point lxqt to a window manager not displayed in it's config gui? It detected Openbox and kwin 4.13 when they were installed, but I'd like to try and use kwin 4.96 from kde-unstable repo since it has less dependencies and is possibly faster, but when I browse for "/opt/bin/kf5/kwin" from lxqt session settings it boots to a blank screen with not even mouse poiter displayed.
Thanks in advance for all help.
Cheers.
Railarian wrote:Only that now I can't set wallpaper... It's selected in lxqt config, but my screen is just plain grey (like my colour theme) no matter how many times I change it. I already removed
Cheers.
I had the wallpaper issue as well. I know this is a bit late since you mentioned the issue, but I found a solution, and maybe it'll help the next person. I found that I could set the wallpaper if I installed pcmanfm-qt-git ( I don't know if the non-git version works for this or not, I didn't try it ) from the AUR.
Similar Messages
-
Using a window manager in x11 to create Desktop / taskbar
Is there anyway to create JFrame's that work with the window manager (such as openbox) to create Desktop and Taskbar elements.
I'd like to see some Swing objects to help work with the window manager.
JDesktop - a panel like element to draw the wallpaper and place desktop icons.
this needs to set XChangeProperty( NET_WM_TYPE_DESKTOP)
JTaskBar - a panel to add a menu, show active windows and system tray.
needs to provide functions to query active windows and system tray items and allow user to create them as desired with some sort of callbacks to update them.
This is not to create a window manager but to work with one that already exists.
Thanks.
I've seen jd4x but it's too complex to use.Gullible Jones wrote:
Re qtile: thanks for the pointer. It looks interesting... However, I was under the impression that the best way to learn how to program was to write your own application(s) from scratch?
Re Wayland: it's still going to be some time before it's usable for anything, no?
(Also, I have to ask: will Wayland eventually be able to run without 3D acceleration? Will it ever support dodgy video cards on older computers, e.g. S3 Savage and Via Unichrome? Will it actually provide performance and stability benefits over X11 - e.g. being able to recover from crashes without losing applications - or will it just be a less kludgy way to get eyecandy on Linux? Because if at least the first of those isn't on the menu, I think it's a nonstarter.)
I believe in the case of Wayland, the kernel is more likely to crash than Wayland itself. Wayland is a protocol and a library implementing that protocol for writing compositors. I don't think 3D is mandatory on Wayland. Take a look at this:
03:49 < mupuf> Wayland let applications render their buffers using OpenGL, that's the big news.
03:50 < mupuf> OpenGL isn't mandatory though
Last edited by diegoviola (2011-07-11 23:19:30) -
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) -
Hello!
I installed KDE on my [TEST] partition last night and gave it an 'honest' spin and I was impressed by it. I have been a die-hard kind of GNOME guy uptil now but ...
Anyways, since most of the things I liked about KDE were related to KWIN I thought about trying it in my [MAIN] GNOME setup. So I did some googling and then went through with it. I must say I did manage to do what I wanted to so I thought about sharing it with the community. My [MAIN] working install is GNOME 3 with 'Force Fallback' enabled, or GNOME Classic as some call it. Please note that your mileage may vary so don't be disappointed if it doesn't work out the way you want it to.
Here are the steps I took:
1. mounted my [TEST] partition to /media/
2. ran 'sudo pacman -S kdebase-workspace --cachedir /media/[TEST]/var/cache/pacman/pkg' ...#since I had done a fresh install just last night, this saved me about a 100MB of download :-)
3. ran Alt+F2 and 'kwin --replace' just to try it out
4. tried putting 'export WINDOW_MANAGER=kwin' in '~/.profile' but it didn't work ...#i was trying to find a way to use kwin at startup instead of metacity
5. tried creating the key '/desktop/gnome/applications/window_manager=/usr/bin/kwin' in gconf-editor but that didn't work either
6. then i thought of something very simple! I installed fusion-icon and put it in startup using gnome-session-properties and then I just had to select the Window Manager as kwin only once. Now fusion-icon automatically loads kwin at log-in. I know it isn't the most elegant way but it works!
7. well almost everything worked with that except the workspaces. The gnome-pager-plugin would only give me one workspace with no option to increase the number of workspaces. I had to logout, log back in using 'KDE Plasma Desktop' session from GDM, logout again and when i logged into GNOME session there was a 'KDE System Settings' menu entry in 'Applications > Other'. Using KDE System Settings > Workspace Behaviour > Virtual Desktops the number of desktops can be changed very conveniently.
Well thats about it. Kwin's composting is really nice in GNOME and I have found a cool Window Decorator called 'deKorator' with many nice themes. Do give it a try and let me know how it goesgeneric_ wrote:which is faster? or more configurable
they are both equally configurable. Fluxbox has a text based configuration. Openbox has an xml based configuration -- which is more or less just text - only in a particular format, with start and end tags. As for speed, you will have to use them to find out. They both use just about the same amount of memory. It all comes down to what you feel comfortable with. I have never liked the default Fluxbox themes, but there are loads of themes available which make it look real nice. Openbox too has a bunch of themes, although I tend to stick with the Onyx and Onyx-Citrus from the default ones.
generic_ wrote:Ok but if i reinstall in the future can I have Hal/fam without gnome
yes. its only a matter of
pacman -S hal fam
Last edited by Inxsible (2009-03-27 15:34:03) -
KDE Default Window Manager Setting File Location
I recently switched KDE to use Awesome instead of Kwin via the "Default Applications" configuration dialog. Unfortunately, using the same dialog to switch back to Kwin gives me a message stating that it can't start Kwin and it immediately reverts the setting back to Awesome.
I imagine somewhere under ~.kde4/share/config/ is a file that will allow me to select the window manager by hand, but I haven't been able to find it. Can someone point me in the right direction?That's what I would've expected too! It turns out it was in ksmserverrc
-
Hello,
I have an integrated webcam that has not been working for approx 6 months! I have updated the Suyin driver/software from Gateway.com. It installs with no problems. I have the webcam icon on
my toolbar and I am able to open the help menu for the software and directions on how to use the camera. However I can't open the preview window and get an error message "camera not installed or in use by another." In device manager, it shows 1.3
M webcam under imaging devices with no errors and the driver being updated. The driver is not Suyin but a Microsoft usb video driver
6.1.7601.17514 from 6/21/ 2006? I have done driver scans from multiple sites that show the webcam driver is up to date?
I have a NV53A Gateway laptop with an AMD 4200 Radeon HD Graphic Card which is updated from AMD.com with a 13.1 Cataylst Vision Engine Control Driver for my AMD VGA card. The webcam worked before with AMD updates such as 12.6.
I have windows 7 64 Home Premium SP1 Processor
AMD Phenom(tm) II N830 Triple-Core Processor, 2100 Mhz, 3 Core(s), 3 Logical Processor(s)BIOS Version/Date
Gateway V2.04, 10/25/2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Hardware Abstraction Layer Version = "6.1.7601.17514"
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.74 GB
Available Physical Memory 1.61 GB
Total Virtual Memory 7.49 GB
Available Virtual Memory 4.74 GB
DirectX:11
Device Manager Info:USB\VID_064E&PID_A219&REV_0215&MI_00
USB\Class_0e&SubClass_03&Prot_00
usbvideo{6bdd1fc6-810f-11d0-bec7-08002be2092f}\0000-driver key
\Device\00000087
000000A4
CM_DEVCAP_REMOVABLE
CM_DEVCAP_SILENTINSTALL
CM_DEVCAP_SURPRISEREMOVALOK
{9d7debbc-c85d-11d1-9eb4-006008c3a19a}-bus type guide
DevNode Status:
0180600A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
USB\VID_064E&PID_A219\HF1315-S32B-OV01-VA-R02.01.05- Parent:usbvideo.inf:Microsoft.NTamd64:USBVideo:6.1.7601.17514:usb\class_0e
00FF2002- rank of installed driver
I hope I provided enough info for you to help me? Everywhere I go I have done what I read, such as uninstall, reinstall, update driver, download from inf file, go to gateway.com,etc...
I don't know if AMD is controlling my webcam? When I click on flash it states no webcam found, the mic is found though. Skype and other sites also say no webcam found. I don't know why I can't install Suyin through device manager?
The software installed is
UVC 0.6.47.1:VIDEO Web Camera
I have multiple registry entries for suyin from the download such as regedit 5.0 Suyin which by default has this error message in many languages? There is also a USB registry that flashes when installed and
a echo@ registry entry too. These are located in the folder in Windows/ Programs/86 under Video Web Camera. What has taken over my webcamera?????
I don't know if I need a BIOS update to fix this from gateway.com??? I haven't done that because I am unsure and don't want to make this worse. I do find at the gateway site the only update is the webcam
which is 1/21/11. The others are the same from 6/24/2010, which I already have. I bought the computer in 12/2010 new. The webcam was working in 12/13 , for I had a 2 year warranty and no issues . I think this is a simple fix but I am not an expert,
only good at following logical,proper instructions to fix an error.
I'd be grateful and shocked if anyone can help me. I have no viruses and have Norton 360 running all the time and done check-ups with Malware and Superspy.
I have another user on my computer which is myself but logged off. If I deleted the other user, would my webcam work or is it my registry, AMD??? I am sooooo frustrated !!!!!! I am confused why
device manger states no errors and driver sites find no webcam updates or errors, either. There is no Suyin driver in the driver store and the inf file won't install per device manager?
Thank-you for your time and if you are unable to assist me , please advice where to go. Please let me know if you need more information.
Kindly,
VictoriaI did some googling and found alot of topics from you on this issue, to me it simply seems like on of the connectors is broken or loose.
-
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) -
Cannot use Remote Desktop host on Windows 8.1 Pro, termsrv corrupted?
Hello,
Few days ago I upgraded my home desktop machine from Windows 8.1 to Windows 8.1 Professional so I can use the Remote Desktop feature.
I enabled everything needed, checked "Allow computers to connect to this computer" from the Remote Settings, forwarded the port 3389 in my rounter and allowed it in my firewall etc...
But I still can't connect to this computer from outside my home network or inside it. The error I get trying to connect is this:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
I'm trying to connect using a laptop running Windows 7 Home Premium.
After searching around I found out that the service responsible for the RDP is called "TermService", I found it on my services but was unable to start it:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
Also, notice the description of the service. So I tried to run a System File Checker on the service's DLL (sfc /scanfile=c:\windows\system32\termsrv.dll) and got this log:
2014-10-05 14:20:41, Info CBS TI: --- Initializing Trusted Installer ---
2014-10-05 14:20:41, Info CBS TI: Last boot time: 2014-10-05 13:56:05.492
2014-10-05 14:20:41, Info CBS Starting TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Ending TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Starting the TrustedInstaller main loop.
2014-10-05 14:20:41, Info CBS TrustedInstaller service starts successfully.
2014-10-05 14:20:41, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2014-10-05 14:20:41, Info CBS Startup processing thread terminated normally
2014-10-05 14:20:41, Info CBS Starting TiWorker initialization.
2014-10-05 14:20:41, Info CBS Ending TiWorker initialization.
2014-10-05 14:20:41, Info CBS Starting the TiWorker main loop.
2014-10-05 14:20:41, Info CBS TiWorker starts successfully.
2014-10-05 14:20:41, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:41, Info CBS Universal Time is: 2014-10-05 11:20:41.783
2014-10-05 14:20:41, Info CBS Loaded Servicing Stack v6.3.9600.17246 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17246_none_fa4ae8e99b1f603c\cbscore.dll
2014-10-05 14:20:41, Info CSI 00000001@2014/10/5:11:20:41.786 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffeeace2e53 @0x7ffeeace24ac @0x7ff69a94d2df @0x7ff69a94dc97
@0x7fff02912225)
2014-10-05 14:20:41, Info CBS SQM: Initializing online with Windows opt-in: True
2014-10-05 14:20:41, Info CBS SQM: Cleaning up report files older than 10 days.
2014-10-05 14:20:41, Info CBS SQM: Requesting upload of all unsent reports.
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2014-10-05 14:20:41, Info CBS NonStart: Set pending store consistency check.
2014-10-05 14:20:41, Info CSI 00000002@2014/10/5:11:20:41.801 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffef3637fc0 @0x7ffef36380f2 @0x7ff69a94ca25 @0x7ff69a94dcae
@0x7fff02912225)
2014-10-05 14:20:41, Info CSI 00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x559943db20
2014-10-05 14:20:41, Info CSI 00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-10-05 14:20:41, Info CSI 00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x26c
2014-10-05 14:20:41, Info CSI 00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2014-10-05 14:20:41, Info CSI 00000007@2014/10/5:11:20:41.999 Beginning NT transaction commit...
2014-10-05 14:20:41, Info CSI 00000008@2014/10/5:11:20:41.999 CSI perf trace:
CSIPERF:TXCOMMIT;143
2014-10-05 14:20:42, Info CSI 00000009 CSI Store 367642371808 (0x00000055993166e0) initialized
2014-10-05 14:20:42, Info CSI 0000000a [SR] Verifying 1 components
2014-10-05 14:20:42, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:42, Info CSI 0000000c [SR] Verify complete
2014-10-05 14:20:52, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CSI 0000000d [SR] Verifying 1 components
2014-10-05 14:20:55, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000000f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000010 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000011 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000012 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000013 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 00000014 Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000015 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000016 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000017 [SR] Verify complete
2014-10-05 14:20:55, Info CSI 00000018 [SR] Repairing 1 components
2014-10-05 14:20:55, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000001a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001b [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001d [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001e [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 0000001f Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000020 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000021 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000022 [SR] Repair complete
Since it's the first time I use this tool I'm not familiar with this log file, but what I managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
My question is:
How can I repair this file? Is this even the problem preventing me from connecting to this computer via Remote Desktop?
Here's a link to my original question which contatining the images.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/cannot-use-remote-desktop-host-on-windows-81-pro/e4776239-4d9e-4934-ae2d-b87cc09f7ademanaged to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
So, the next step supposedly is
using DISM.
Coincidentally I reached that page last night from
this one, which I thought gave me a better awareness of how much manual repair might be possible. E.g. maybe the WinSxS isn't quite as fragile as we are being led to believe? (It's making me feel sort of like how I used to feel about the
registry when seeing all the caveats about using RegEdit before I got used to that tool.)
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(v=WS.10).aspx
Something else that I became aware of yesterday serendipitously is SxStrace.exe. I have never seen it used but it sounds useful. E.g. perhaps easier to interpret for supplemental clues than the ProcMon trace that I usually advocate.
Or perhaps use both and see in ProcMon when the SxStrace is writing. E.g. filter with Operation Is WriteFile.
However, what I would do first is find out what the state of your system is regarding that module. E.g. try this Powershell pipeline to list what you have.
PS C:\windows> dir -R -Fil "termsrv.dll" | sort-object FullName | ft Length, FullName -AutoSize
Note that I am giving you the whole command line, including prompt to show where the command should be started from.
C.f. another thread where doing the same diagnostic procedure seems to be finding more a problem with the Windows Update software than with the user's WinSxS cache.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3#LastReply
HTH
Robert Aldwinckle -
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. -
How can I return to use OSX (Yosemite) after installing Windows 8.1?
How can I return to use OSX (Yosemite) after installing Windows 8.1?
I cannot find Boot Camp on my iMac (late 2013) with windows installed. So I downloaded it, but I cannot run it because of an error (x64...). I tried to use my USB stick with bootcamp installed but nothing. When I turn my iMac on it starts automatically with windows. I tried to search it, but I found only the setup and it doesn't work. How can I get back to my APPLE iMac? How can I use OSX?
Excuse me for the (maybe) uncorrect language, I speak Italian.Hello!
You can start your Mac up with the [alt] (sometimes [option]) key pressed and you will get the Startup Manager. -
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). -
firefox hangs up and says it "got confused", when I try to switch from using facebook as myself to using facebook as a page I manage.
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
* Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
* Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")
In Firefox 4 you can use one of these to start in <u>[[Safe mode]]</u>:
* Help > Restart with Add-ons Disabled
* Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes -
Is it possilbe to totally disable the use of Microsoft Accounts in Windows 8.x ?
The existence and need of "Microsoft Accounts" in Windows 8.x causes many issues for corporate IT management.
1) To access Windows 8.x Mail App, Calendar App, etc, OneDrive, Skype, to upgrade from Windows 8.0 to Windows 8.1, and the Windows Store requires a Microsoft Account.
2) Not all users have or will want to have their own personal Microsoft Account
3) It is possible for the corporate IT department to create Microsoft Accounts for each of the company Users, but it is an extra burden and difficult to manage these accounts.
Potentially the simplest solution is to be able to totally disable the use of Microsoft Accounts in Windows 8.x, is this possible?Hello,
You have the choice of uninstalling the metro apps ou use the GPO to block the use of Microsoft account.
Please see the followings links:
Uninstall metro apps:
http://www.deploiementwindows.com/supprimer-les-applications-dans-windows-8-1/
GPO: Block Microsoft accounts
http://technet.microsoft.com/en-us/library/jj966262%28v=ws.10%29.aspx
http://4sysops.com/archives/control-windows-store-access-with-group-policy/
regards,
- Yannick Plavonil -
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?
/SaiTechselect 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
Maybe you are looking for
-
How to create Measures for count on Flag colums in FACT with a CONDITON
I have about 6 flag columns in my fact table and I would like to create measures in my report with count as aggregation on these flag columns with a group by on a condition. I am able to do this very easily with SQL query but am really stuck with on
-
I have upgraded to Mountain Lion and have found that some of my software no longer works, notably Image Browser and also the Epson Scanner Perfection 3490 software. Is there a 'patch' or way to allow me to use these programmes especially the scanner.
-
T42 (Type 2378) Rescue and Recovery text not showing up in GUI
I have a machine that I hit the IBM button to restore my system back to its factory settings. It loads up fine but when I hit the [Restore your system] it pulls up a new window and has 3 bullets I can select from, but there is NO text on the window.
-
Hi guys, Please any one can send me the SD (Over to Cost) structures.
-
Unable to create a folder through java code on weblogic server 10GR3
Hi, I have java code which creates a folder and writes an XML file in to it. File saveDirectory = new File(storePath); if(!saveDirectory.exists()){ System.out.println("directory doesnt exists"); boolean isDirectoryCreated = saveDirectory.mkdir(); Sys