You are not logged in.
I use sway with sddm. The log file contains these error messages:
```
00:00:00.104 [ERROR] [wlr] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
2024-02-27 19:16:17 - [swaybg-1.2.0/main.c:293] Found config * for output eDP-1 (LG Display 0x069A)
[058 19:16:18.620738] [glfw error 65544]: process_desktop_settings: failed with error: [org.freedesktop.DBus.Error.UnknownMethod] No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
Read 68 .desktop files, found 52 apps.
User input is: Firefox Web Browser
/usr/bin/bash -c '/usr/lib/firefox/firefox '
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
:
Error: WaylandMessage::Write() too many files to send
```
Where the "Error: WaylandMessage::Write() too many files to send" is written to it again and again that it has started to consume very large amount of space. At the time I noticed it the log was approx 140GB. The file is here .local/share/sddm/wayland-session.log
Offline
Which compositor command for SDDM are you using? Can you reproduce if you start SDDM with xorg and just start a distinct sway session from there?
If this is actually from the sway session likely some misconfiguration. Are you running some status/notification widget or so in a tight loop rather than with a delay or so?
Last edited by V1del (2024-02-27 14:16:52)
Offline
I don't know. I installed archlinux using archinstall. How do I find out which compositor I am using?
I am running mako as a notification widget. The issue appeared after the new update for sway (1.9).
Last edited by Ruyx (2024-02-27 14:27:30)
Offline
I configured mako as follows:
default-timeout=5000
max-visible=5
max-history=5
Offline
This doesn't have to come from mako, while I haven't found any ref to WaylandMessage::Write() in either the Wlroots or sway or mako sources, likely sway is running "something" unnecessarily often.
Last edited by V1del (2024-02-27 14:55:44)
Offline
The messages apparently start after running firefox
Offline
This definitely seems to be caused by firefox. After I killed it, the log messages stopped. This even happens in Ubuntu 22.04.
Offline
https://searchfox.org/mozilla-central/s … xy.cpp#218
But why is the error being triggered?
Offline
Having the same problem here on debian with sway. For me all is fine until I put my laptop in suspend and then bring it back from suspend. Afterwards I have to kill firefox and start it again.
This right here is probably related too: https://bugs.launchpad.net/ubuntu/+sour … ug/2051838
I could be very wrong but I have the feeling this started happening when I upgraded to firefox 123 on February 23rd.
Offline
Can confirm that when starting firefox with
MOZ_ENABLE_WAYLAND=0 firefox
I don't have the problem.
Offline
https://bugzilla.mozilla.org/show_bug.cgi?id=1882449
Some progress on the bug.
Offline