From: Martin Wege <martin.l.wege@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: Cygwin 3.5.0 KDE kate crashes in |cygdbus-1-3!_dbus_get_local_machine_uuid_encoded ()| ...
Date: Tue, 17 Oct 2023 11:08:00 +0200 [thread overview]
Message-ID: <CANH4o6M7WdD=5kLSRA34ig26uB-OzBQR6_EcddEtEGLQSwuKsQ@mail.gmail.com> (raw)
In-Reply-To: <20231017092849.2a159612504378b64493b4b1@nifty.ne.jp>
On Tue, Oct 17, 2023 at 2:29 AM Takashi Yano via Cygwin
<cygwin@cygwin.com> wrote:
>
> On Mon, 16 Oct 2023 23:31:40 +0200
> Roland Mainz wrote:
> > Steps to reproduce:
> > 1. Boot Windows 10
> > 2. Log in
> > 3. Open Cygwin terminal
> > 4. Run "kate"
> >
> > Result:
> > kate crashes
> >
> > Expected result:
> > kate runs
> >
> > ---- snip ----
> > $ uname -a
> > CYGWIN_NT-10.0-19045 DERFWNB8353 3.5.0-0.438.g322c7150b25e.x86_64
> > 2023-09-17 14:19 UTC x86_64 Cygwin
> > $ gdb --args kate
> > GNU gdb (GDB) (Cygwin 12.1-1) 12.1
> > Copyright (C) 2022 Free Software Foundation, Inc.
> > [snip]
> > (gdb) run
> > Starting program: /usr/bin/kate
> > [New Thread 9784.0x29ac]
> > [New Thread 9784.0x32c8]
> > [New Thread 9784.0x4288]
> > [New Thread 9784.0x4fa4]
> > [New Thread 9784.0x4e18]
> > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
> > '/tmp/runtime-roland.mainz'
> > [New Thread 9784.0x4350]
> > [New Thread 9784.0x4a0]
> > [New Thread 9784.0x159c]
> > [New Thread 9784.0x19d8]
> > [New Thread 9784.0x15f8]
> > [New Thread 9784.0x24fc]
> > process 170: D-Bus library appears to be incorrectly set up; failed to
> > read machine uuid: Failed to open "/etc/machine-id": No such file or
> > directory
> > See the manual page for dbus-uuidgen to correct this issue.
Basically all KDE apps crash like that in Cygwin 3.5
>
> Does not
> dbus-uuidgen --ensure=/etc/machine-id
> help?
I tried the steps-to-reproduce, and I get the same problem.
I tried to run kate with dbus-run-session kate, but while kate the
runs, dialogs like Open... need a MINUTE to open, and similar delays
happen when I browse inthe filesystem using that dialog.
Thanks,
Martin
next prev parent reply other threads:[~2023-10-17 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 21:31 Roland Mainz
2023-10-17 0:28 ` Takashi Yano
2023-10-17 9:08 ` Martin Wege [this message]
2023-10-17 2:27 ` Brian Inglis
2023-10-17 3:30 ` Takashi Yano
2023-11-01 9:05 ` Martin Wege
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='CANH4o6M7WdD=5kLSRA34ig26uB-OzBQR6_EcddEtEGLQSwuKsQ@mail.gmail.com' \
--to=martin.l.wege@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).