When DBusActivatable (with some applicaitons) is set to "true", you can't run them from budgie-run-dialog #658
Comments
JannikHv
changed the title
JannikHv
changed the title
|
Buh. |
|
So I thought I fixed this. Basically when dbus activatable is true the API just completely lies about when it is and isn't launched, so then we quit before the message gets across dbus... |
|
It's just really, really weird. When dbus activatable is true and i open, for example gedit, 2 fast times in a row, it opens. But just after the second try when there wasn't much time (let's say about 5 Seconds) in between those 2 tries. It's really not a huge deal IMO, just really strange, especially because it just applies to specific types of applications. Edit: Just for no misunderstanding, everything here is only related to budgie-run-dialog, not any other application launching. :) |
|
Actually, it's still happening (tested with gedit and many more apps). |
We now monitor dbus names to see when the application actually comes up, as opposed to niavely immediately quiting. This does mean some quite nasty workarounds as we now have to monitor names on the bus compared with the .desktop files. For "normal" applications we obey the startup notification spec and wait for them to fail or succeed, and quit then. It's also quite likely that we'll have to add functionality to expire the rundialog after a certain amount of time regardless of the call, in case dbus activation failed (cuz it succeeds regardless) - and to ensure we show again when we are app-activated. This resolves issue #658. Signed-off-by: Ikey Doherty <ikey@solus-project.com>
|
^ Implemented, fixed, closed. |
|
@ikeydoherty after updating (including some budgie-related packages) I'm still having this issue |
|
Needs releasing @m-delvalle - we're planning a 10.2.9 release. It's not really backportable I'm afraid, hence needing a new release |
|
@ikeydoherty np, just checking :) |
|
Update: just applied latest patches and it's working great now! thanks @ikeydoherty |
|
Woot! :D |
Operating System: Solus 1.2.0.5 + Arch Linux
Budgie version: Budgie 10.2.7
When answering some support tickets, I discovered a problem regarding budgie-run-dialog.
The problem is basically as described in the following:
A program like gedit or corebird have "DBusActivatable" set to true in their /usr/share/applications/ entry. If it's set to true, you can either not, or sometimes start it with budgie-run-dialog, but only if you try to open it multiple times in a row. When DBusActivatable is set to "false" or compeltely removed, it starts normally. It's a really weird behaviour...
Here is a video I made to demonstrate the problem. Sorry for the flickering and such...:
http://sendvid.com/qvxnywhi
The text was updated successfully, but these errors were encountered: