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

Can't start flameshot #2154

Closed
VG08 opened this issue Dec 10, 2021 · 4 comments
Closed

Can't start flameshot #2154

VG08 opened this issue Dec 10, 2021 · 4 comments
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@VG08
Copy link

VG08 commented Dec 10, 2021

Flameshot Version

v0.10.2

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

arch linux

Description

the problem I am having is that when i run flameshot gui it does nothing and exits instantly and when I do flameshot it gives me this error
QSettings::value: Empty key passed QSettings::value: Empty key passed QSettings::setValue: Empty key passed QSettings::value: Empty key passed QSettings::setValue: Empty key passed

Steps to reproduce

I don't remember doing anything special because of this is happening but it is giving me what I told above.

Screenshots or screen recordings

maim-region-20211210-084328

System Information

I am using arch linux. dwm with xorg

@VG08 VG08 added the Unconfirmed Bug The bug is not confirmed by anyone else. label Dec 10, 2021
@mmahmoudian
Copy link
Member

@VG08 dwm does not ship with two important things: notification manager and systray. There is a patch for systray and for notification you can install something like dunst.

But if you really don't want to have these on your system, you can turn off the systray and notifications options in the Flameshot config before launching flameshot.

If you have sort them out (either by installing or disabling) and you still have issues, please try the following and give us the output:

  1. Open two terminals
  2. In the first one run
pkill flameshot
flameshot
  1. In the second terminal run
flameshot gui

@mmahmoudian mmahmoudian added the Waiting For Info Addressing the issue or merging the PR is halted and we are waiting for more info to be provided. label Dec 10, 2021
@VG08
Copy link
Author

VG08 commented Dec 12, 2021

@mmahmoudian I have dunst for for notifs no systray tho, I did what you said and flameshot gui opens up flameshot, I actually thought that flameshot gui runs without flameshot running in bg, also I used trayer to check for systray and flameshot shows up there, also sorry for late reply.

@mmahmoudian
Copy link
Member

mmahmoudian commented Dec 12, 2021

@VG08 in newer version the idea is to reduce dependency to dbus and therefore much much less need for background process.

Checkout #2003

@VG08
Copy link
Author

VG08 commented Dec 13, 2021

oh ok thanks, imma put flameshot into my startup

@mmahmoudian mmahmoudian removed the Waiting For Info Addressing the issue or merging the PR is halted and we are waiting for more info to be provided. label Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.
Projects
None yet
Development

No branches or pull requests

3 participants