all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 52029@debbugs.gnu.org
Subject: bug#52029: wterm fails to start on core-updates-frozen
Date: Thu, 04 Aug 2022 21:37:49 -0400	[thread overview]
Message-ID: <87czdfv5aq.fsf@dismail.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2111212334490.13935@marsh.hcoop.net> (Jack Hill's message of "Sun, 21 Nov 2021 23:39:05 -0500 (EST)")

Jack Hill <jackhill@jackhill.us> writes:

> Hi Guix,
>
> wterm fails to start on the core-updates-frozen branch (commit
> ddbc3a6f4ca2605d8102aa659389300f97d715ac) in both sway and gnome wayland
> sessions:
>
> ```
> $ wterm
> wl_registry@2: error 0: invalid interface for global 11: have xdg_wm_base, wanted zxdg_shell_v6
> # wayland_create_context: No wl_drm global
> # wayland_create_context: No wl_shm global
> # wld_wayland_create_context: Could not initialize any of the specified implementations
> Can't create wayland context
> ```
>
> However, wterm seems to be unmaintained upstream [0], so maybe this is not
> somethint that we want to fix in Guix.

I vote that we remove wterm from guix.  It is still unmaintained at the
github link below.  And it doesn't ever run properly.


> [0] https://github.com/majestrate/wterm/issues/24
>
> Best,
> Jack




  reply	other threads:[~2022-08-05  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  4:39 bug#52029: wterm fails to start on core-updates-frozen Jack Hill
2022-08-05  1:37 ` Joshua Branson via Bug reports for GNU Guix [this message]
2022-08-05  8:58   ` paren--- via Bug reports for GNU Guix
2022-08-06  1:38     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-06  9:14       ` paren--- via Bug reports for GNU Guix
2022-08-10 16:07         ` Joshua Branson via Bug reports for GNU Guix

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=87czdfv5aq.fsf@dismail.de \
    --to=bug-guix@gnu.org \
    --cc=52029@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    --cc=jbranso@dismail.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.