Flameshot gui не работает

Troubleshooting¶

Please first read the troubleshooting steps for your operating system in this page and then if it was not solved, report the issue after reading the Issue reporting section down below:

Issue reporting¶

To report a bug or suggest a new feature, you can go to GitHub issues page and use the searchbox in the middle of the page to see if anyone else have already posted something similar. Sometimes you will find a quick solution just by reading the threads. In case of feature request, if you find someone with similar idea, just give that a thumbs-up to increase its priority/importance.

In case you didn’t find similar issue, create a new issue and explain in details what the issue is. If you can, add pictures or video recordings to clarify the situation. For bug reports, make sure to also visit issue reporting page in which we have explained how to get the information we need in each bug report.

Linux¶

In System tray area, flameshot appears duplicate icons/indicator¶

• It is currently found in Ubuntu 14.04 and 16.04 Unity environment, such problems occur. This problem does not occur with Ubuntu 17.10 Unity. #92

In Gnome the flameshot icon does not appear in the tray¶

• Gnome does not have a systray, therefore in Gnome you should install the gnome Tray icons extension. For more information, read the Tary icon section of the github repository.

In tiling window managers (e.g i3wm, dwm, bspwm) flameshot crashes when taking the screenshot¶

• most tiling window managers dows not come with a nitification daemon, and Flameshot communicates with user through notifications. This means that Flameshot is dependent on notification manager to be installed and running. Easy way to test if you have a notification manager is to try notify-send «test» in your terminal. If you see the notification, you have it, otherwise we suggest you to install a notification manager such as dunst :

Flameshot icon is visible in tray area but when I click on it nothing happens¶

First try the using the command flameshot gui in terminal. This does exactly what clicking on the tray icon does. (make sure can you see Flameshot icon in the tray area)

If the above step didn’t work:

1. Open 3 terminals
2. Kill Flameshot if it is already open using pkill flameshot
3. In the first terminal run dbus-monitor —session sender=org.flameshot.Flameshot
4. In the second terminal run flameshot
5. In the third terminal run flameshot gui
6. Copy the content of the first terminal in pastebin: https://bin.snopyta.org/
8. Post the link in the issue on Github

macOS¶

All opened applications go away and only the blank desktop is visible for selection¶

As it has been reported multiple times already (1, 2), macOS restricts applications from accessing the screen. Therefore you have to give Flameshot security permissions to «record» your desktop.

If you were still getting the following message when restarting Flameshot, try removing (using the «-» button) and then adding flameshot to the list above.

Источник

Flameshot stopped working #307

Comments

michaldybczak commented Aug 11, 2018

Describe the bug
This isn’t a bug per se since probably it only affects me. Not sure what happened (maybe an update) but when I try to use flameshot it doesn’t starts. I then checked it in terminal and there is no output, no even a single word.
I tested both flameshot-git from AUR and from Manjaro repo. Both are not working.
If that’s not the place to ask such questions, just let me know and I close this topic.

Does someone knows how to approach such issue when there is no info to debug?

To Reproduce
Open flameshot from start or with command: flameshot. Nothing happens

Expected behavior
Flameshot starts

Desktop (please complete the following information):

• OS: Manjaro KDE

The text was updated successfully, but these errors were encountered:

AlfredoRamos commented Aug 12, 2018

Try to run the following and post its output:

Or better yet, run the following (you might need to install gdb first):

And when it prompts for a command (gdb) , just type bt and post the output.

michaldybczak commented Aug 12, 2018 •

pkill flameshot — no output, terminal jumps to another line ready for next command, although this was expected?

The last one hangs as if I run a program, meaning I have to quit it to return to normal command.
It never prompted me for anything.
Arch base doesn’t have debug symbols yet. We’re waiting for them since long time. We were promised to get them but. they are still not there and I’m not sure what is the reason for that delay.

farseerfc commented Aug 12, 2018 •

Have you tried flameshot gui command to take a screenshot?

michaldybczak commented Aug 12, 2018

Wow, that did work:

So flameshot is working but the flameshot command and the launch icons stopped working then. Also, before when I was typing flameshot in start menu, I had two results, flameshot itself and its configuration utility. Now it just finds flamshot only.

hosiet commented Aug 12, 2018

Look, I’ve got a suggestion:

1. Restart your computer
2. Invoke flameshot via start menu (and yes, it seems that nothing happens, right?)
3. Click the little triangle at your KDE tray area: is the flamrshot icon hidden inside?

If yes, it’s that you misused the KDE Desktop Environment, not the bug from flameshot side. If no, please describe what did you see then.

farseerfc commented Aug 12, 2018

The plain flameshot command and icon should start in background. There should be an icon for flameshot in the KDE system tray area, but it might be hidden in the notification dropdown by default.
You can config KDE systray to always show flameshow icon like this:

michaldybczak commented Aug 12, 2018

I restarted computer many times since yesterday. and 3. You are right, flameshot does start in systray mode, which I hate and never set it that way. It had to switch to default or something. How can I change it since configuration utility isn’t findable anymore?

michaldybczak commented Aug 12, 2018 •

OK, this is weird. I discovered I can choose configuration on right-click of system tray. I disabled systray icon and now. I can’t trigger flameshot from start menu since it isn’t showing anywhere.

I guess it’s no longer a technical issue but a usability issue ;P

How can I add it to quicklaunch icon? I did it in the past somehow but I can’t remember how.

EDIT: OK, I discovered I can go to configuration by right click on the flameshot icon from menu as well and then I brought back the tray.

So it looks like flameshot simply changed how its GUI works. Previously there were like two separate launchers, one for triggering screenshot, other for configuration. Now all was squeezed into one. On one side it’s good and there is no single seperate configure launcher, but on other hand, the default launcher stopped triggering screenshots, it only launches flameshot into systray. And when systray is disabled, flameshot has no gui accessibility, which is a usability breakage.

I’d say that flameshot has awful and counter-intuitive GUI when it comes to it’s triggering. After that is fine.

So how can I restore screenshot quick-launch icon? Maybe creating dummy icon, pointing it to flameshot icon and then ascribing «flameshot gui» command to it? This seems not very user friendly thou. Isn’t there any simpler method?

Источник

Установка FlameShot в Linux

FlameShot — мультиплатформенный инструмент для создания скриншотов. Эта небольшая программа предлагает дополнительные возможности для быстрого редактирования скриншотов, которых нет в Ubuntu. Скриншоты можно создавать и стандартными средствами системы. Для этого достаточно нажать клавишу Print Screen, после чего скриншот будет сохранен в папке с изображениями.

Однако, главное преимущество FlameShot — возможность захвата выделенной области экрана и добавление к ней различных выделений и указателей. Это может быть особенно полезным для создания онлайн-инструкций. В этой статье мы рассмотрим как установить Flameshot в Linux.

Установка FlameShot в Linux

Установить приложение можно с использованием репозиториев Ubuntu в Терминале, а также с помощью Центра приложений Ubuntu Software. Ниже рассмотрим оба способа.

1. Репозитории дистрибутива

Для того, чтобы установить FlameShot в Ubuntu или Debian, откройте терминал и введите команду:

sudo apt install flameshot

Если вы используете Fedora, введите в терминале:

sudo dnf install flameshot

Введите y и нажмите Enter для подтверждения выполнения операции.

Дождитесь, пока программа будет установлена на ваш компьютер.

2. Официальный сайт

Загрузить Flameshot также можно с официального сайта разработчиков.

Для скачивания выберите, например, Hosted on Github, 64-bit. На открывшейся странице найдите версию для своего дистрибутива, например deb-пакет для 64-битной Ubuntu 20.04.

Выберите Сохранить файл и нажмите ОК.

Запустите скачанный файл в загрузках браузера.

Нажмите кнопку Установить в открывшемся окне центра загрузки приложений и введите пароль для подтверждения.

Дождитесь, пока приложение будет установлено на компьютер.

По завершению операции закройте центр установки приложений Ubuntu.

Как пользоваться Flameshot

Откройте Меню приложений в системы и нажмите на иконку Flameshot.

На экране появится всплывающее уведомление Привет, я тут! Щелкните по значку на панели задач.

Нажмите по значку на панели задач и выберите пункт Настройки.

Здесь на вкладке Горячие клавиши можно узнать, как быстрее работать с программой. При желании, можно поменять горячие клавиши на свои.

Откройте окно, которое нужно захватить и ещё раз нажмите по значку Flameshot на панели задач. На этот раз выберите пункт Сделать снимок.

Внимательно прочитайте, как использовать некоторые из функций программы.

Выделите часть окна, которую необходимо захватить. Вокруг выделенной области появятся инструменты для редактирования.

Для примера, выберите квадрат на нижней панели инструментов и выделите красным ту часть скриншота, на которую необходимо обратить внимание.

Нажмите на кнопку с изображением стрелки и нарисуйте указатель, как показано на скриншоте. Затем нажмите на кнопку Сохранить, расположенную на панели инструментов справа.

Выберите, куда необходимо сохранить файл.

Найдите файл и откройте его с помощью программы для просмотра изображений.

Выводы

Теперь вы знаете как выполняется установка Flameshot в Linux на примере Ubuntu, а также как пользоваться программой. Мы рассмотрели лишь несколько функций этой программы. В процессе использования вы можете попробовать использовать и другие. FlameShot не нагружает систему, имеет все необходимые функции редактирования и экономит кучу времени.

Источник

«flameshot config» and «flameshot gui» won’t start flameshot with recent git snapshot #123

Comments

hosiet commented Feb 22, 2018

With the git snapsnot on 20180114, I was able to start flameshot indirectly with a call of flameshot config or flameshot gui . However with today’s build (20180221), flameshot won’t start (or pop-up config window) unless I start flameshot in advance. Otherwise plain call to flameshot config would only return with exit code 0, nothing else happens.

Perhaps we need git bisect to find out which commit introduced this bug?

The text was updated successfully, but these errors were encountered:

lupoDharkael commented Feb 22, 2018

Some users have been reporting this issue from multiple distros, but not every user is having this problem.

It could be a problem in the service configuration.
I have 2 service files:
This one is configured to be used when you define the qmake variable for packaging https://github.com/lupoDharkael/flameshot/blob/master/dbus/package/org.dharkael.Flameshot.service
The second is used by default and points to the binary in /usr/local/bin https://github.com/lupoDharkael/flameshot/blob/master/dbus/make/org.dharkael.Flameshot.service

Using this file the service should be launched when you send a dbus call and the target receiver isn’t running.

Does it work as before if you use an older version?

lupoDharkael commented Feb 23, 2018 •

hey @hosiet, does the journal say something? It looks like an error in the dbus daemon tring to start flameshot before the dbus call.
Try to launch it and check journalctl

hosiet commented Feb 24, 2018

@lupoDharkael yes, there are some error messages.

Источник