From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnome-connections: update to 45.0
Date: Wed, 06 Mar 2024 11:30:42 +0100 [thread overview]
Message-ID: <20240306103042.9D4A4254DA@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49111@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
New comment by chrysos349 on void-packages repository
https://github.com/void-linux/void-packages/pull/49111#issuecomment-1980133397
Comment:
I enabled remote desktop on localhost via `gnome-remote-desktop` (#49123), and successfully connected to localhost with `gnome-connections`. No segfaulting.
** UPD 1**
Actually, i reproduced the same intermittent segfaults when trying to connect to localhost. It happens when I copy an image to the clipboard.
```
../gdk/wayland/gdkselection-wayland.c:283: error reading selection buffer: Operation was cancelled
No data received from local clipboard for sending to remote side!
```
When I connect to the remote windows box, no segfaulting happens (even if I have an image in the clipboard).
Does it mean the bug is specific to localhost connections and has something to do with the clipboard contents? (Who needs connecting to the localhost anyway??)
**UPD 2**
here is what I found in release notes for `gnome-connections-46.beta`
see here - https://download.gnome.org/sources/gnome-connections/46/gnome-connections-46.beta.news
```mardkown
- Update gtk-frdp
- Fix several crashes related to clipboard channel
```
that may be the ~~reason~~ fix for the crashes.
next prev parent reply other threads:[~2024-03-06 10:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 7:14 [PR PATCH] " chrysos349
2024-03-06 4:47 ` oreo639
2024-03-06 4:53 ` oreo639
2024-03-06 4:58 ` oreo639
2024-03-06 4:58 ` oreo639
2024-03-06 5:50 ` chrysos349
2024-03-06 5:52 ` chrysos349
2024-03-06 6:54 ` chrysos349
2024-03-06 7:08 ` chrysos349
2024-03-06 7:24 ` chrysos349
2024-03-06 7:32 ` [PR PATCH] [Updated] " chrysos349
2024-03-06 8:26 ` chrysos349
2024-03-06 9:47 ` chrysos349
2024-03-06 10:28 ` chrysos349
2024-03-06 10:29 ` chrysos349
2024-03-06 10:29 ` chrysos349
2024-03-06 10:30 ` chrysos349
2024-03-06 10:30 ` chrysos349 [this message]
2024-03-06 10:30 ` chrysos349
2024-03-06 10:32 ` chrysos349
2024-03-06 12:57 ` [PR PATCH] [Updated] " chrysos349
2024-03-06 13:01 ` chrysos349
2024-04-20 13:14 ` fanyx
2024-04-21 6:54 ` [PR PATCH] [Closed]: " chrysos349
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=20240306103042.9D4A4254DA@inbox.vuxu.org \
--to=chrysos349@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).