Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peek window does not show, no errors in console #512

Open
bendavis78 opened this issue Sep 25, 2019 · 31 comments
Open

Peek window does not show, no errors in console #512

bendavis78 opened this issue Sep 25, 2019 · 31 comments
Labels

Comments

@bendavis78
Copy link

I'm running in Arch Linux, and nothing seems to happen when running peek. No window shows up, but the process seems to just hang indefinitely. When running from the terminal, I only see the output:

Using screen recorder backend gnome-shell

And nothing else. No window frame shows up at all, but the process keeps running.

@gort818
Copy link
Contributor

gort818 commented Sep 26, 2019

can you run peek like this

G_MESSAGES_DEBUG=all peek

and post the output

@phw
Copy link
Owner

phw commented Sep 27, 2019

This is pretty strange, I wonder if this is related to the window type being set to "Utility" (see #507). But I cannot reproduce this here on my system, and Arch with Gnome (on X) is kind of the default target of this app.

@bendavis78 Is Gnome running with X or Wayland?

@phw phw added the bug label Sep 27, 2019
@amirhfarzaneh
Copy link

amirhfarzaneh commented Nov 7, 2019

I have the same problem on Ubuntu 18.04 running on X11. When I run peek with app drawer the icons appears on dash but no window is shown!

when I do:
G_MESSAGES_DEBUG=all peek

nothing shows. no error no window

@tennox
Copy link

tennox commented Nov 7, 2019

@amirhfarzaneh Try the same with sudo...

Here's what's the output for me then. But still - no window showing up also not in dock:

⋊> ~ env G_MESSAGES_DEBUG=all peek  # no output
⋊> ~ sudo env G_MESSAGES_DEBUG=all peek 
(peek:15453): Gtk-DEBUG: 09:54:13.146: Connecting to session manager
(peek:15453): Gtk-DEBUG: 09:54:13.147: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
(peek:15453): Gtk-DEBUG: 09:54:13.147: Failed to get the Xfce session proxy: The name org.xfce.SessionManager is not owned
** (peek:15453): DEBUG: 09:54:13.248: desktop-integration.vala:168: Desktop: 
** (peek:15453): DEBUG: 09:54:13.249: application.vala:282: GTK theme: elementary
** (peek:15453): DEBUG: 09:54:13.249: desktop-integration.vala:168: Desktop: 
** (peek:15453): DEBUG: 09:54:13.249: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R


** (peek:15453): WARNING **: 09:54:13.250: Binding '<Ctrl><Alt>R' failed!
** (peek:15453): DEBUG: 09:54:13.250: desktop-integration.vala:168: Desktop: 
** (peek:15453): DEBUG: 09:54:13.251: utils.vala:68: Looking for executable ffmpeg (0): /usr/bin/ffmpeg

Using screen recorder backend ffmpeg
** (peek:15453): DEBUG: 09:54:13.277: application-window.vala:882: Decoration layout: close,minimize:maximize,menu
** (peek:15453): DEBUG: 09:54:13.318: recording-area.vala:38: Absolute recording area x: 80, y: 106, w: 498, h: 298
** (peek:15453): DEBUG: 09:54:13.318: recording-area.vala:45: Screen w: 3840, h: 1986
** (peek:15453): DEBUG: 09:54:13.318: recording-area.vala:58: Clipped recording area x: 80, y: 106, w: 498, h: 298
** (peek:15453): DEBUG: 09:54:13.318: recording-area.vala:69: Scaled recording area x: 80, y: 106, w: 498, h: 298
** (peek:15453): DEBUG: 09:54:13.335: recording-area.vala:38: Absolute recording area x: 80, y: 106, w: 498, h: 298
** (peek:15453): DEBUG: 09:54:13.335: recording-area.vala:45: Screen w: 3840, h: 1986
** (peek:15453): DEBUG: 09:54:13.335: recording-area.vala:58: Clipped recording area x: 80, y: 106, w: 498, h: 298
** (peek:15453): DEBUG: 09:54:13.335: recording-area.vala:69: Scaled recording area x: 80, y: 106, w: 498, h: 298

OS: elementary OS 5.0 Juno
peek: 1.4.0 from PPA (tried flatpak before, too)

@willydee
Copy link

willydee commented Nov 7, 2019

Confirming issue on Arch based system (EndeavourOS)
Some system details:

  • GNOME Version 3.34.1
  • Memory 15.5 GiB
  • Graphics Intel® HD Graphics 530 (Skylake GT2)
  • OS name EndeavourOS; Build ID: rolling
$ G_MESSAGES_DEBUG=all peek
(peek:29625): GLib-GIO-DEBUG: 11:39:12.254: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(peek:29625): Gtk-DEBUG: 11:39:12.311: Connecting to session manager
** (peek:29625): DEBUG: 11:39:12.312: desktop-integration.vala:168: Desktop: GNOME
(peek:29625): GLib-GIO-DEBUG: 11:39:12.313: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(peek:29625): dconf-DEBUG: 11:39:12.313: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(peek:29625): dconf-DEBUG: 11:39:12.313: unwatch_fast: "/org/gnome/desktop/interface/" (active: 0, establishing: 1)
** (peek:29625): DEBUG: 11:39:12.313: application.vala:282: GTK theme: Arc-Flatabulous-Darker
** (peek:29625): DEBUG: 11:39:12.313: desktop-integration.vala:168: Desktop: GNOME
(peek:29625): dconf-DEBUG: 11:39:12.313: watch_fast: "/com/uploadedlobster/peek/" (establishing: 0, active: 0)
(peek:29625): dconf-DEBUG: 11:39:12.313: watch_established: "/org/gnome/desktop/interface/" (establishing: 0)
(peek:29625): dconf-DEBUG: 11:39:12.313: watch_established: "/com/uploadedlobster/peek/" (establishing: 1)
** (peek:29625): DEBUG: 11:39:12.313: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R

** (peek:29625): DEBUG: 11:39:12.314: desktop-integration.vala:168: Desktop: GNOME
Using screen recorder backend gnome-shell
** (peek:29625): DEBUG: 11:39:12.373: application-window.vala:882: Decoration layout: menu:minimize,maximize,close
** (peek:29625): DEBUG: 11:39:12.418: recording-area.vala:38: Absolute recording area x: 24, y: 59, w: 498, h: 298
** (peek:29625): DEBUG: 11:39:12.418: recording-area.vala:45: Screen w: 7040, h: 1440
** (peek:29625): DEBUG: 11:39:12.418: recording-area.vala:58: Clipped recording area x: 24, y: 59, w: 498, h: 298
** (peek:29625): DEBUG: 11:39:12.418: recording-area.vala:69: Scaled recording area x: 24, y: 59, w: 498, h: 298
** (peek:29625): DEBUG: 11:39:12.457: recording-area.vala:38: Absolute recording area x: 24, y: 59, w: 498, h: 298
** (peek:29625): DEBUG: 11:39:12.457: recording-area.vala:45: Screen w: 7040, h: 1440
** (peek:29625): DEBUG: 11:39:12.457: recording-area.vala:58: Clipped recording area x: 24, y: 59, w: 498, h: 298
** (peek:29625): DEBUG: 11:39:12.457: recording-area.vala:69: Scaled recording area x: 24, y: 59, w: 498, h: 298
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.465: gdk_pixbuf_from_pixdata() called on:
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.465: 	Encoding raw
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.465: 	Dimensions: 14 x 14
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.465: 	Rowstride: 56, Length: 808
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.465: 	Copy pixels == false
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.472: gdk_pixbuf_from_pixdata() called on:
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.472: 	Encoding raw
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.472: 	Dimensions: 14 x 14
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.472: 	Rowstride: 56, Length: 808
(peek:29625): GdkPixbuf-DEBUG: 11:39:12.472: 	Copy pixels == false

@willydee
Copy link

willydee commented Nov 7, 2019

I think I've just discovered the source of the problem: the window opens off-screen on first launch, depending on the display configuration. My GNOME display setup is like seen below:
Screenshot from 2019-11-07 11-53-09
So, the coordinates logged above are off screen since the upper 360 pixels of display #1 are outside the visible area.

When setting display #1 as the primary, the already opened Peek window suddenly appears at the top left of the leftmost screen. On subsequent launches, the Peek window appears as expected, even if the primary display is set to #3 again.

@amirhfarzaneh
Copy link

amirhfarzaneh commented Nov 7, 2019

here is my output of G_MESSAGES_DEBUG=all peek:

(peek:3434): Gtk-DEBUG: 14:02:44.473: Connecting to session manager
(peek:3434): Gtk-DEBUG: 14:02:44.473: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
(peek:3434): Gtk-DEBUG: 14:02:44.473: Failed to get the Xfce session proxy: The name org.xfce.SessionManager is not owned
** (peek:3434): DEBUG: 14:02:44.635: desktop-integration.vala:168: Desktop: 
** (peek:3434): DEBUG: 14:02:44.635: application.vala:282: GTK theme: qogir-win-dark
** (peek:3434): DEBUG: 14:02:44.635: desktop-integration.vala:168: Desktop: 
** (peek:3434): DEBUG: 14:02:44.636: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R


** (peek:3434): WARNING **: 14:02:44.636: Binding '<Ctrl><Alt>R' failed!
** (peek:3434): DEBUG: 14:02:44.636: desktop-integration.vala:168: Desktop: 
** (peek:3434): DEBUG: 14:02:44.638: utils.vala:68: Looking for executable ffmpeg (0): /usr/bin/ffmpeg

Using screen recorder backend ffmpeg
** (peek:3434): DEBUG: 14:02:44.746: application-window.vala:884: Decoration layout: close,minimize,maximize:
** (peek:3434): DEBUG: 14:02:44.776: recording-area.vala:38: Absolute recording area x: 24, y: 54, w: 498, h: 298
** (peek:3434): DEBUG: 14:02:44.776: recording-area.vala:45: Screen w: 6200, h: 2012
** (peek:3434): DEBUG: 14:02:44.776: recording-area.vala:58: Clipped recording area x: 24, y: 54, w: 498, h: 298
** (peek:3434): DEBUG: 14:02:44.776: recording-area.vala:69: Scaled recording area x: 24, y: 54, w: 498, h: 298
** (peek:3434): DEBUG: 14:02:44.805: recording-area.vala:38: Absolute recording area x: 24, y: 54, w: 498, h: 298
** (peek:3434): DEBUG: 14:02:44.805: recording-area.vala:45: Screen w: 6200, h: 2012
** (peek:3434): DEBUG: 14:02:44.805: recording-area.vala:58: Clipped recording area x: 24, y: 54, w: 498, h: 298
** (peek:3434): DEBUG: 14:02:44.805: recording-area.vala:69: Scaled recording area x: 24, y: 54, w: 498, h: 298

the same as @tennox

@amirhfarzaneh
Copy link

I think I've just discovered the source of the problem: the window opens off-screen on first launch, depending on the display configuration. My GNOME display setup is like seen below:
Screenshot from 2019-11-07 11-53-09
So, the coordinates logged above are off screen since the upper 360 pixels of display #1 are outside the visible area.

When setting display #1 as the primary, the already opened Peek window suddenly appears at the top left of the leftmost screen. On subsequent launches, the Peek window appears as expected, even if the primary display is set to #3 again.

You're right choosing another screen as the primary and then switching back to the previous one fixes this. I am now able to launch peek. So maybe the problem is with multi-screen configurations?

@willydee
Copy link

willydee commented Nov 7, 2019

Yes, that is my assumption. It looks like the effect is reproducible in multi-display configurations if the upper edge of the leftmost display is below the top edge of the full viewport. Your viewport size {6200 x 2012 pixels) is also quite uncommon, and suggests that there is vertical offset between displays somewhere.

@amirhfarzaneh
Copy link

correct! I have a weird setup due to my office space.
layout

@nazrhyn
Copy link

nazrhyn commented Dec 3, 2019

Same thing happened to me. Fiddling with the monitor configuration fixed it.

In my case:

  • I have three monitors.
  • The central one is the largest and is my primary.
  • The leftmost one is on a non-adjustable stand and sits lower than the central one, so it has to be dragged down so that windows cross from the central monitor to the leftmost at the same visual "height".

Could Peek check to see if it's offscreen, somehow? 🤔

@gort818
Copy link
Contributor

gort818 commented Dec 3, 2019

Can you try this branch https://github.com/gort818/peek/tree/patch-2 ?
see if it fixes it for you.

@nazrhyn
Copy link

nazrhyn commented Dec 3, 2019

Can you try this branch https://github.com/gort818/peek/tree/patch-2 ?
see if it fixes it for you.

Well, for my part, unfortunately, now that I've done all of the fiddling, it starts on-screen again 😢.

@ghost
Copy link

ghost commented Dec 23, 2019

I have a similar issue. Same with both peek and peek-git for arch and the AUR.

Running the debug commands as shown above:

$ G_MESSAGES_DEBUG=all peek
(peek:13308): GLib-GIO-DEBUG: 22:21:52.797: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(peek:13308): Gtk-DEBUG: 22:21:52.891: Connecting to session manager
** (peek:13308): DEBUG: 22:21:52.892: desktop-integration.vala:168: Desktop: GNOME
(peek:13308): GLib-GIO-DEBUG: 22:21:52.892: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(peek:13308): dconf-DEBUG: 22:21:52.892: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(peek:13308): dconf-DEBUG: 22:21:52.892: unwatch_fast: "/org/gnome/desktop/interface/" (active: 0, establishing: 1)
** (peek:13308): DEBUG: 22:21:52.892: application.vala:282: GTK theme: Matcha-dark-aliz
** (peek:13308): DEBUG: 22:21:52.892: desktop-integration.vala:168: Desktop: GNOME
(peek:13308): dconf-DEBUG: 22:21:52.892: watch_fast: "/com/uploadedlobster/peek/" (establishing: 0, active: 0)
(peek:13308): dconf-DEBUG: 22:21:52.892: watch_established: "/org/gnome/desktop/interface/" (establishing: 0)
(peek:13308): dconf-DEBUG: 22:21:52.893: watch_established: "/com/uploadedlobster/peek/" (establishing: 1)
** (peek:13308): DEBUG: 22:21:52.893: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R

** (peek:13308): DEBUG: 22:21:52.893: desktop-integration.vala:168: Desktop: GNOME
Using screen recorder backend gnome-shell
** (peek:13308): DEBUG: 22:21:52.986: application-window.vala:884: Decoration layout: menu:minimize,maximize,close
** (peek:13308): DEBUG: 22:21:53.024: recording-area.vala:38: Absolute recording area x: 24, y: 58, w: 498, h: 298
** (peek:13308): DEBUG: 22:21:53.024: recording-area.vala:45: Screen w: 6400, h: 1440
** (peek:13308): DEBUG: 22:21:53.024: recording-area.vala:58: Clipped recording area x: 24, y: 58, w: 498, h: 298
** (peek:13308): DEBUG: 22:21:53.024: recording-area.vala:69: Scaled recording area x: 24, y: 58, w: 498, h: 298
** (peek:13308): DEBUG: 22:21:53.055: recording-area.vala:38: Absolute recording area x: 24, y: 58, w: 498, h: 298
** (peek:13308): DEBUG: 22:21:53.055: recording-area.vala:45: Screen w: 6400, h: 1440
** (peek:13308): DEBUG: 22:21:53.055: recording-area.vala:58: Clipped recording area x: 24, y: 58, w: 498, h: 298
** (peek:13308): DEBUG: 22:21:53.055: recording-area.vala:69: Scaled recording area x: 24, y: 58, w: 498, h: 298
$ sudo G_MESSAGES_DEBUG=all peek
(peek:13415): GLib-DEBUG: 22:23:11.762: posix_spawn avoided (fd close requested) 
(peek:13415): GLib-GIO-DEBUG: 22:23:11.783: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
** (peek:13415): DEBUG: 22:23:11.881: desktop-integration.vala:168: Desktop: 
(peek:13415): GLib-GIO-DEBUG: 22:23:11.881: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(peek:13415): dconf-DEBUG: 22:23:11.881: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(peek:13415): dconf-DEBUG: 22:23:11.881: unwatch_fast: "/org/gnome/desktop/interface/" (active: 0, establishing: 1)
** (peek:13415): DEBUG: 22:23:11.881: application.vala:282: GTK theme: Matcha-sea
** (peek:13415): DEBUG: 22:23:11.881: desktop-integration.vala:168: Desktop: 
(peek:13415): GLib-DEBUG: 22:23:11.881: posix_spawn avoided (fd close requested) 
(peek:13415): dconf-DEBUG: 22:23:11.882: watch_fast: "/com/uploadedlobster/peek/" (establishing: 0, active: 0)
** (peek:13415): DEBUG: 22:23:11.883: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R

** (peek:13415): DEBUG: 22:23:11.883: desktop-integration.vala:168: Desktop: 
(peek:13415): GLib-DEBUG: 22:23:11.883: posix_spawn avoided (fd close requested) 
(peek:13415): dconf-DEBUG: 22:23:11.884: watch_established: "/org/gnome/desktop/interface/" (establishing: 0)
(peek:13415): dconf-DEBUG: 22:23:11.884: watch_established: "/com/uploadedlobster/peek/" (establishing: 1)
** (peek:13415): DEBUG: 22:23:11.884: utils.vala:68: Looking for executable ffmpeg (0): /usr/bin/ffmpeg

Using screen recorder backend ffmpeg
** (peek:13415): DEBUG: 22:23:11.976: application-window.vala:884: Decoration layout: menu:minimize,maximize,close
** (peek:13415): DEBUG: 22:23:12.011: recording-area.vala:38: Absolute recording area x: 24, y: 58, w: 498, h: 298
** (peek:13415): DEBUG: 22:23:12.011: recording-area.vala:45: Screen w: 6400, h: 1440
** (peek:13415): DEBUG: 22:23:12.012: recording-area.vala:58: Clipped recording area x: 24, y: 58, w: 498, h: 298
** (peek:13415): DEBUG: 22:23:12.012: recording-area.vala:69: Scaled recording area x: 24, y: 58, w: 498, h: 298
** (peek:13415): DEBUG: 22:23:12.038: recording-area.vala:38: Absolute recording area x: 24, y: 58, w: 498, h: 298
** (peek:13415): DEBUG: 22:23:12.038: recording-area.vala:45: Screen w: 6400, h: 1440
** (peek:13415): DEBUG: 22:23:12.038: recording-area.vala:58: Clipped recording area x: 24, y: 58, w: 498, h: 298
** (peek:13415): DEBUG: 22:23:12.038: recording-area.vala:69: Scaled recording area x: 24, y: 58, w: 498, h: 298

Display arrangement:
image

I am using the standard copy of GNOME that comes with Manjaro.


Edit: rearranging the screens to the following makes it visible.

image

If not to fix this, please could someone techdrop a command line flag in to override the starting position to work around this? It would be greatly appreciated. The issue is that no taskbar icon shows up either so you have literally no way of finding it unless you alter your monitor settings...

@s4dio
Copy link

s4dio commented Jan 5, 2020

sudo G_MESSAGES_DEBUG=all peek
(peek:21116): Gtk-DEBUG: 09:21:05.736: Connecting to session manager
(peek:21116): Gtk-DEBUG: 09:21:05.736: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
(peek:21116): Gtk-DEBUG: 09:21:05.736: Failed to get the Xfce session proxy: The name org.xfce.SessionManager is not owned
** (peek:21116): DEBUG: 09:21:05.821: desktop-integration.vala:168: Desktop: 
** (peek:21116): DEBUG: 09:21:05.821: application.vala:282: GTK theme: Adwaita-dark
** (peek:21116): DEBUG: 09:21:05.821: desktop-integration.vala:168: Desktop: 
** (peek:21116): DEBUG: 09:21:05.822: application.vala:217: Changed keybinding_toggle_recording  => <Ctrl><Alt>R

** (peek:21116): DEBUG: 09:21:05.822: desktop-integration.vala:168: Desktop: 
** (peek:21116): DEBUG: 09:21:05.824: utils.vala:68: Looking for executable ffmpeg (0): /usr/bin/ffmpeg

Using screen recorder backend ffmpeg
** (peek:21116): DEBUG: 09:21:05.848: application-window.vala:882: Decoration layout: :menu,minimize,maximize,close
** (peek:21116): DEBUG: 09:21:05.869: recording-area.vala:38: Absolute recording area x: 27, y: 71, w: 498, h: 298
** (peek:21116): DEBUG: 09:21:05.869: recording-area.vala:45: Screen w: 6200, h: 1920
** (peek:21116): DEBUG: 09:21:05.869: recording-area.vala:58: Clipped recording area x: 27, y: 71, w: 498, h: 298
** (peek:21116): DEBUG: 09:21:05.869: recording-area.vala:69: Scaled recording area x: 27, y: 71, w: 498, h: 298
** (peek:21116): DEBUG: 09:21:05.881: recording-area.vala:38: Absolute recording area x: 27, y: 71, w: 498, h: 298
** (peek:21116): DEBUG: 09:21:05.881: recording-area.vala:45: Screen w: 6200, h: 1920
** (peek:21116): DEBUG: 09:21:05.881: recording-area.vala:58: Clipped recording area x: 27, y: 71, w: 498, h: 298
** (peek:21116): DEBUG: 09:21:05.881: recording-area.vala:69: Scaled recording area x: 27, y: 71, w: 498, h: 298

Similar issue here, and playing with screen displays fixed it (swapped primary monitor a couple of times). Since the recording area looked like it was off-display on my far left screen, setting that screen as primary monitor did the trick.

GNOME Shell 3.28.4
Ubuntu 18.04.03 LTS (5.0.0-37-generic)

@johnnygossdev
Copy link

johnnygossdev commented Jan 22, 2020

I also had this issue. I had to shift my displays to find it.

The Peek window popped up at the bottom of display 2 after moving them.

peek-bug

@KjellMorgenstern
Copy link

Ubuntu 18.04. I had a third monitor temporarily connected the day before. When starting peek with only two monitors now, no output, no dialog was shown. Moving one display like @johnnygossdev shows helped, and the issue did not appear on subsequent runs of peek anymore.

@geek-andi
Copy link

I can confirm this happens sporadically with a multi-screen setup. (Once I disconected the additional screen, peek window showed up again, after using the same setup as before, it also shows up atm)

@RichAyotte
Copy link

The problem also occurs with GNOME Calculator so this might be a larger scope issue that should be fixed at the window manager level.

@geek-andi
Copy link

The problem also occurs with GNOME Calculator so this might be a larger scope issue that should be fixed at the window manager level.

True, now that you mention it I experienced that one as well. The only difference is that there is no workaroundish shortcut for getting the window back inside the screen, like Window+Curser-Left - it doesn't work with peek.

I'm using ubuntu 16.04 btw.

@neshi47
Copy link

neshi47 commented Jan 20, 2021

is there a way to configure it to show without having to toggle settings in display? after finding this thread I found like 7 peek windows open 😅

@swhitf
Copy link

swhitf commented Mar 30, 2021

Hi there - just had the same issue on Ubuntu 20. Also found a LOT of windows after changing my display config 😂️. If it's a difficult fix perhaps for the time being just adding a known issue to the main readme with steps to workaround would do? Once I've moved the app to set its default start position it doesn't seem to have the same problem again. Otherwise really great little tool!

@SAOPP
Copy link

SAOPP commented May 25, 2021

Hi there! The same behaviour guys, but I have an 4 monitors :D

image

** (peek:19741): WARNING **: 18:32:38.648: Binding '<Ctrl><Alt>R' failed!
Using screen recorder backend ffmpeg

@raydac
Copy link

raydac commented Sep 11, 2021

also got the issue with Peek in my multi-monitor environment, looks like we will see fix not very soon so that developed some small replacement for the utility

@mlissner
Copy link

If you hit ALT + Space, you can move the window using the keyboard and make it show up. Never seen this before, but it's a pretty easy fix.

@raydac
Copy link

raydac commented Sep 24, 2021

under Ubuntu 20.04 with two monitors, ALT + SPACE doesn't work, PEEK just presented as an icon in the dash panel, any click on it make it hiding and PEEK just hangs among processes

@frankhuurman
Copy link

Same issue as @raydac on Ubuntu 20.04 with an extra monitor attached to my laptop. Doesn't launch from terminal and clicking it adds it to the dash but nothing shows up. Clicking the icon closes it again.

@frankhuurman
Copy link

image

This showed up after I unplugged the monitor from my laptop, so Peek is definitely running in the background but the extra monitor prevents it from being used until you unplug.

@dangerbrady
Copy link

I think I've just discovered the source of the problem: the window opens off-screen on first launch, depending on the display configuration. My GNOME display setup is like seen below: Screenshot from 2019-11-07 11-53-09 So, the coordinates logged above are off screen since the upper 360 pixels of display #1 are outside the visible area.

When setting display #1 as the primary, the already opened Peek window suddenly appears at the top left of the leftmost screen. On subsequent launches, the Peek window appears as expected, even if the primary display is set to #3 again.

This resolved my issue as well

@cmalard
Copy link

cmalard commented Jun 16, 2022

just just happened to me too with this config:
image
😅

@raydac
Copy link

raydac commented Jun 18, 2022

@frankhuurman I am not sure that the bug in peek will be fixed soon (it looks like that developer has not enough time to care for the great utility), if urgent needs for workaround to make gif you can try japagoge utility as a variant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests