Github messages for voidlinux
 help / color / mirror / Atom feed
From: svenper <svenper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ibus crash when setting engine 
Date: Sun, 23 Feb 2020 18:09:18 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19439@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

New issue by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/19439

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.4.21_1 x86_64-musl GenuineIntel uptodate hold rrnFFFFFFFFFFF
* package:  
  ibus-1.5.21_3
  ibus-rime-1.4.0_1
  librime-1.5.3_2

### Expected behavior

ibus sets the engine without dbus related errors.

### Actual behavior

```text
(process:5333): IBUS-WARNING **: 17:45:35.261: ibus_bus_call_sync: org.freedesktop.IBus.SetGlobalEngine: GDBus.Error:org.freedesktop.DBus.Error.Failed: Set global engine failed: The connection is closed
```

### Steps to reproduce the behavior

```text
ibus-daemon --daemonize --replace --xim
sleep 1
ibus engine rime
```

I tried to downgrade ibus but without success, I suspect the rebuild for python3 f03a0a9 may be involved which is a pain to reproduce as downgrading python3 places me in git revert hell.

             reply	other threads:[~2020-02-23 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 17:09 svenper [this message]
2020-02-28 12:57 ` svenper
2020-04-13  9:47 ` svenper
2020-04-13 10:20 ` svenper
2020-04-13 10:20 ` [ISSUE] [CLOSED] " svenper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19439@inbox.vuxu.org \
    --to=svenper@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).