GNOME Bugzilla – Bug 742469
Cannot launch gedit with --standalone and --wait simultaneously
Last modified: 2020-11-24 10:00:37 UTC
I'm running gedit 3.12.2 on Ubuntu 14.10. As far as I know, this is the latest version of gedit that is available from the Ubuntu repos. My git editor has for a long time been set to: $ git config -l | grep editor core.editor=gedit -s -w Since rebuilding my system with a clean install of Ubuntu 14.10, I can no longer launch gedit this way: $ gedit -s -w Failed to register: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "DescribeAll" with signature "" on interface "org.gtk.Actions" doesn't exist Both 'gedit -s' and 'gedit -w' work on their own, it's just the combination that no longer seems to work. It was working before I rebuilt the OS, so it's entirely possible that the problem is something in my environment. I'm just at a loss to understand what that might be.
Thanks for the bug report. I have the same error with the development version of gedit. As a workaround you can use: $ gedit --wait --new-window It should work the same, unless you use --standalone for a good reason.
Ok, thanks. I have tried the workaround, and it does work as you suggest. I had thought that I needed --standalone to ensure that the git client would see that my commit message edit had completed, in those cases where I also had an existing gedit window open. But I just tried it with the options you suggested, and it works fine.
Mass-closing of all gedit bugzilla tickets. Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.