From: chris <chris@bumblehead.com>
To: 65769@debbugs.gnu.org
Cc: chris@bumblehead.com
Subject: bug#65769: wlgreet-sway-session
Date: Tue, 5 Sep 2023 22:10:54 -0700 [thread overview]
Message-ID: <ZPgJ3jPRPPjvBR3b@guix-xps> (raw)
In-Reply-To: <ZPfsKrd1Xsm_gHL4@guix-xps>
In case the attachment is not-accessible, important last lines of sway-greeter.388.log are pasted here.
```
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-1.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-2.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-3.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-4.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-5.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-6.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-7.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-8.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-9.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-10.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-11.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-12.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-13.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-14.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-15.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-16.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-17.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-18.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-19.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-20.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-21.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-22.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-23.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-24.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-25.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-26.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-27.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-28.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-29.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-30.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-31.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-32.lock check permissions
00:00:00.067 [ERROR] [sway/server.c:231] Unable to open wayland socket
00:00:00.067 [DEBUG] [wlr] [types/wlr_drm_lease_v1.c:103] Destroying wlr_drm_lease_device_v1 for /dev/dri/card0
```
next prev parent reply other threads:[~2023-09-06 5:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 3:04 bug#65769: greetd-wlgreet-sway-session result is blinking cursor chris
2023-09-06 5:00 ` bug#65769: wlgreet-sway-session chris
2023-09-06 5:10 ` chris [this message]
2023-09-06 5:22 ` chris
2023-09-06 12:34 ` Josselin Poiret via Bug reports for GNU Guix
2023-09-06 5:32 ` chris
2023-09-06 15:57 ` bug#65769: no elogind chris
2023-09-08 14:46 ` bug#65769: greetd-wlgreet-sway-session result is blinking cursor paren--- via Bug reports for GNU Guix
2023-09-08 15:31 ` chris
2023-09-08 15:37 ` paren--- via Bug reports for GNU Guix
2023-09-08 16:01 ` chris
2023-09-08 16:08 ` paren--- via Bug reports for GNU Guix
2023-09-09 11:11 ` Josselin Poiret via Bug reports for GNU Guix
2024-10-31 20:56 ` David Arroyo
2024-11-01 10:03 ` chris
2024-11-01 10:25 ` chris
2023-10-20 9:01 ` bug#65769: Hugo Buddelmeijer
2023-10-20 10:02 ` bug#65769: bdju via Bug reports for GNU Guix
2023-10-20 12:14 ` bug#65769: Hugo Buddelmeijer
2023-10-20 13:49 ` bug#65769: Hugo Buddelmeijer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPgJ3jPRPPjvBR3b@guix-xps \
--to=chris@bumblehead.com \
--cc=65769@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).