Re: [i3] full screencapture with xwd not working only in i3
On 11/15/15, Ingo Bürk wrote: > Hi, > > the command works fine for me. What version if i3 are you running? ii i3 1:201510302301+git36-minos~ubuntu14.04.1amd64 metapackage (i3 window manager, screen locker, menu, statusbar) ii i3-wm 1:201510302301+git36-minos~ubuntu14.04.1amd64 improved dynamic tiling window manager ii i3lock 1:201502121131+git3-minos~ubuntu14.04.1 amd64 improved screen locker ii i3status2.9-2~~trusty1 amd64Generates a status line for dzen2, xmobar or i3bar > Is > your Xorg up to date? For Ubuntu 14.04, yes! ii xserver-xorg1:7.7+1ubuntu8.1 amd64X.Org X server > Also, judging from the xwd source code, maybe you can try adding > "-icmap" to the arguments. I shall try with that flag. however it works fine with other WMs except i3. > > > Ingo > > On 11/15/2015 09:47 AM, Zenny wrote: >> Hi, >> >> I am having problem to take screenshot with xwd*** only in a full >> screenshot mode (but selective screenshot works). This only happens >> with i3, but not with other window managers. Please find the log >> below, fyi. >> >> >> ***PS: I am aware of other tools like scrot, maim and what not, but I >> need this specific xwd to capture a virtual screen running in a >> frambuffer with xvfb which others do not support, if you have any >> tools that can screencapture a virtual x server, let me know. >> Apprexciate that. >> >> >> USER@MACHINE:~/Downloads/xwd$ xwd -root -out i3screenshot_xwd.xwd >> X Error of failed request: BadColor (invalid Colormap parameter) >> Major opcode of failed request: 91 (X_QueryColors) >> Resource id in failed request: 0x0 >> Serial number of failed request: 166 >> Current serial number in output stream: 166 >> USER@MACHINE:~/Downloads/xwd$ xwd > i3screenshot_xwd_frame.xwd >> USER@MACHINE:~/Downloads/xwd$ ls -la i3screenshot*.xwd >> -rw-rw-r-- 1 USER USER 3995469 Nov 15 08:33 i3screenshot_xwd_frame.xwd >> -rw-rw-r-- 1 USER USER 0 Nov 15 08:33 i3screenshot_xwd.xwd >> >> Any inputs appreciated! >> >> Cheers. >> /z > >
[i3] full screencapture with xwd not working only in i3
Hi, I am having problem to take screenshot with xwd*** only in a full screenshot mode (but selective screenshot works). This only happens with i3, but not with other window managers. Please find the log below, fyi. ***PS: I am aware of other tools like scrot, maim and what not, but I need this specific xwd to capture a virtual screen running in a frambuffer with xvfb which others do not support, if you have any tools that can screencapture a virtual x server, let me know. Apprexciate that. USER@MACHINE:~/Downloads/xwd$ xwd -root -out i3screenshot_xwd.xwd X Error of failed request: BadColor (invalid Colormap parameter) Major opcode of failed request: 91 (X_QueryColors) Resource id in failed request: 0x0 Serial number of failed request: 166 Current serial number in output stream: 166 USER@MACHINE:~/Downloads/xwd$ xwd > i3screenshot_xwd_frame.xwd USER@MACHINE:~/Downloads/xwd$ ls -la i3screenshot*.xwd -rw-rw-r-- 1 USER USER 3995469 Nov 15 08:33 i3screenshot_xwd_frame.xwd -rw-rw-r-- 1 USER USER 0 Nov 15 08:33 i3screenshot_xwd.xwd Any inputs appreciated! Cheers. /z
Re: [i3] binding the same key to revert the command?
Hi Sege, On 11/8/15, Serge van Ginderachter wrote: > I have a script that does that, to pause dunst (whilst locking) and/or > disabling the autolock screensaver (for a presentation mode). > > The trick is to be able to check for a state, which I do by using gtrayicon > to visually show the current state, so the script can check whether to > enable or disable the mode. > > See https://github.com/srvg/dotfiles/blob/master/bin/presentation-mode Thanks for the input. Can you explain the usage in my case in particular. Cheers, /z > > On 8 November 2015 at 10:16, Zenny wrote: > >> Hi, >> >> I am trying to use a keybinding to pause a process temporily, >> >> bindsym $mod+p exec pkill -SIGSTOP >> >> But I could not figure out how to make pressing to same keybinding to >> restart the process? >> >> Currenlty I am using, >> >> bindsym $mod+c exec pkill -SIGCONT >> >> Instead, I want something like re-pressing $mod+p executes pkill >> -SIGCONT . >> >> Thanks! >> >> /z >> >
[i3] binding the same key to revert the command?
Hi, I am trying to use a keybinding to pause a process temporily, bindsym $mod+p exec pkill -SIGSTOP But I could not figure out how to make pressing to same keybinding to restart the process? Currenlty I am using, bindsym $mod+c exec pkill -SIGCONT Instead, I want something like re-pressing $mod+p executes pkill -SIGCONT . Thanks! /z
Re: [i3] Mouse capture problem i3 and OBS
I tried with others and with the same effect. So the culprit lies in OBS, I guess. Sorry for the false alarm. On 10/1/15, Michael Stapelberg wrote: > Have you tried reproducing this problem with any other window manager that > offers a tabbed mode? > > On Thu, Oct 1, 2015 at 12:36 PM, Zenny wrote: > >> Hi, >> >> Having problem with redundant mouse capture in OBS running with i3-wm. >> >> When the mouse is moved to change some recording settings in the OBS >> interface at the bottom or in the canvas, the mouse movement for those >> modifications gets displayed in the canvas and gets recorded in the >> final input, even when there is no source of screen capture of the >> machine in which OBS is running. >> >> This problem is only when in the tabbed mode, but not in the tiling >> mode of i3-wm. By changing the tabbed mode ($MOD+w) to tiling mode >> ($MOD+e), the mouse movements for OBS settings modifications >> disappears and that is what actually desired. >> >> Posted a bug report to OBS guys: >> https://obsproject.com/mantis/view.php?id=340 and posting here if that >> has to anything with i3-wm? >> >> Thanks! >> >> /z >> > > > > -- > Best regards, > Michael >
[i3] Mouse capture problem i3 and OBS
Hi, Having problem with redundant mouse capture in OBS running with i3-wm. When the mouse is moved to change some recording settings in the OBS interface at the bottom or in the canvas, the mouse movement for those modifications gets displayed in the canvas and gets recorded in the final input, even when there is no source of screen capture of the machine in which OBS is running. This problem is only when in the tabbed mode, but not in the tiling mode of i3-wm. By changing the tabbed mode ($MOD+w) to tiling mode ($MOD+e), the mouse movements for OBS settings modifications disappears and that is what actually desired. Posted a bug report to OBS guys: https://obsproject.com/mantis/view.php?id=340 and posting here if that has to anything with i3-wm? Thanks! /z
Re: [i3] windows are not selectable with obs-studio with i3-wm
Hi Tony, Thanks for the pointer, the standard ubuntu has i3 at 4.7. I upgraded to 4.10.x following suit to your advice. However, the xcomposite windows are detected, but only selectable from the same i3 workspace where OBS is running. The xcomposite windows from other windows are listed, but once selected, it replaces with a red area instead of the window itself. /z On 9/14/15, Tony Crisci wrote: > Hey, > > I can't reproduce this. I can select the windows perfectly well. Please > update to the latest version of i3 and try again. > > On 09/13/2015 08:02 PM, Zenny wrote: >> Hi, >> >> i3 has been a default wm for me for a long time! >> >> Having a problem similar to what has been discussed here: >> >> https://obsproject.com/forum/threads/tiling-window-managers-xcomposite-no-windows-found.34708/ >> >> The xcomposite windows cannot be selectable even under i3 like in >> Xmonad, however the second reply confirms that it worked fine with >> Awesome. >> >> Seems like it is more a problem of the window manager than the >> application (obs-studio)! Any inputs?! >> >> Thanks! >> >> /z > >
[i3] windows are not selectable with obs-studio with i3-wm
Hi, i3 has been a default wm for me for a long time! Having a problem similar to what has been discussed here: https://obsproject.com/forum/threads/tiling-window-managers-xcomposite-no-windows-found.34708/ The xcomposite windows cannot be selectable even under i3 like in Xmonad, however the second reply confirms that it worked fine with Awesome. Seems like it is more a problem of the window manager than the application (obs-studio)! Any inputs?! Thanks! /z
