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

Wrong D-Bus name? #960

Closed
mmahmoudian opened this issue Sep 23, 2020 · 5 comments
Closed

Wrong D-Bus name? #960

mmahmoudian opened this issue Sep 23, 2020 · 5 comments
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@mmahmoudian
Copy link
Member

Flameshot version
Flameshot v0.8.0
Compiled with Qt 5.15.0
flameshot-git r576.f34def6-1 AUR

Describe the bug
The D-Bus name seems to be old. This might be the reason of some of the reported issues.

To Reproduce
Peek 2020-09-23 15-55

Expected behavior
Have the correct name

System Information
Operating System: Manjaro Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.6-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

@RixzZ
Copy link

RixzZ commented Sep 23, 2020

My custom shortcut (configured with D-Bus) stopped working in some moment the past week. I had to change the custom shortcut to execute the command instead.

@mmahmoudian
Copy link
Member Author

@RixzZ what is the final status of your change? How does it look like?

@borgmanJeremy
Copy link
Contributor

@mmahmoudian Can this be closed since it seemed to be a pamac issue?

@mmahmoudian
Copy link
Member Author

Ok, after chatting on Slack with @borgmanJeremy and after multiple try and error, the following are the finding and the ultimate solution:

Diagnosis

Jeremy suggested to dump the strings from the binary using strings:
image
image

and there it was, already in the binary file. But it was not in the binary Jeremy had. We then checked the sha256 checksum and they were different. I was clear that something is wrong/outdated with my binary. Surprisingly enough, I ran pamac update 5 hours prior to this.

Solution

Jeremy suggested to "clean install" flameshot:

❯ pamac remove flameshot-git
❯ pamac clean
❯ rm /usr/share/zsh/site-functions/_flameshot  # because it complained once during installation that the file exists
❯ pamac install flameshot-git

and it worked fine and consequently the printscreen button not works fine (previously it was running the gui mode automaticallu and I had to activate it manually, butnow even when the D-Bus does not exist, the printscr spawns the D-Bus and then rung the flameshot in gui mode automatically:

image

P.s: pamac is doing what yay and similar software does, so you can practically replicate the solution with yay.

@RixzZ
Copy link

RixzZ commented Sep 23, 2020

Thanks for the solution. I'll change it back to that.

I'll leave a screenshot of the alternative with the command anyway:
Screenshot from 2020-09-23 17-34-07

This kind of custom shortcut is added with the New > Global Shortcut > Command/URL option.

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