search

openSUSE / openSUSEway

dotfiles for Sway on openSUSE
MIT License
82 stars 17 forks source link

GDM messes up tty1 #53

Closed denisok closed 2 years ago

denisok commented 2 years ago

in case GDM is installed it creates /usr/lib/systemd/logind.conf.d/reserveVT.conf with ReserveVT=1 which makes it unavailable for greeter. fixes #52

mcepl commented 2 years ago

Yes, it definitively helped. With the attached configuration I can log in, but I don't think I can reboot/poweroff computer after I exit sway.

mcepl commented 2 years ago

Hmm, another problem. I don't have Pulseaudio running (or pipewire or whatever): pavucontrol doesn't show any channels. Despite this:

~@stitny$ pgrep -f -a pipewire
2197 /usr/bin/pipewire
2198 /usr/bin/pipewire-media-session
2199 /usr/bin/pipewire-pulse
~@stitny$ pgrep -f -a dbus
1448 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
2214 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
2517 /usr/lib/cups/notifier/dbus dbus://
~@stitny$

and perhaps because of this (the Czech message means "Directory or file doesn't exist"):

~@stitny$ LANG=en_GB.utf8 systemctl --user -l -a --no-pager status pipewire
~@stitny$ LANG=en_GB.utf8 systemctl --user -l -a --no-pager status pipewire
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
     Active: active (running) since Tue 2021-11-02 18:20:34 CET; 2h 26min ago
TriggeredBy: ● pipewire.socket
   Main PID: 2197 (pipewire)
      Tasks: 2 (limit: 4915)
     Memory: 2.7M
        CPU: 61ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─2197 /usr/bin/pipewire

Nov 02 18:20:34 stitny systemd[2189]: Started PipeWire Multimedia Service.
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: could not set nice-level to -11: Adresář nebo soubor neexistuje
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Nov 02 18:20:34 stitny pipewire[2197]: mod.rtkit: could not make thread realtime: Adresář nebo soubor neexistuje
~@stitny$ groups
users docker libvirt rtkit systemd-journal wheel
~@stitny$
denisok commented 2 years ago

@mcepl I added changes for sway config in greetd, now shutdown and reboot should work from greetd (Mod4+shift+e).

denisok commented 2 years ago

Hmm, another problem. I don't have Pulseaudio running (or pipewire or whatever): pavucontrol doesn't show any channels. Despite this:

~@stitny$ pgrep -f -a pipewire
2197 /usr/bin/pipewire
2198 /usr/bin/pipewire-media-session
2199 /usr/bin/pipewire-pulse
~@stitny$ pgrep -f -a dbus
1448 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
2214 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
2517 /usr/lib/cups/notifier/dbus dbus://
~@stitny$

no idea, but that is a different issue:

~ 0$ pgrep -f -a pipewire
3347 /usr/bin/pipewire
3350 /usr/bin/pipewire-media-session
3352 /usr/bin/pipewire-pulse
~ 0$ pgrep -f -a dbus
1104 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
2967 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
5226 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
5228 bwrap --args 39 /usr/bin/xdg-dbus-proxy --args=41
5229 /usr/bin/xdg-dbus-proxy --args=41
5322 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
5323 /usr/bin/xdg-dbus-proxy --args=39
5351 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
5352 /usr/bin/xdg-dbus-proxy --args=39
5509 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
5510 /usr/bin/xdg-dbus-proxy --args=39
5538 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
5539 /usr/bin/xdg-dbus-proxy --args=39
10359 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
10360 /usr/bin/xdg-dbus-proxy --args=39
16218 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
16219 /usr/bin/xdg-dbus-proxy --args=39
16239 bwrap --args 37 /usr/bin/xdg-dbus-proxy --args=39
16240 /usr/bin/xdg-dbus-proxy --args=39

maybe this makes a difference:

~ 0$ zypper se -i xdg
Loading repository data...
Reading installed packages...

S  | Name                     | Summary                                                  | Type
---+--------------------------+----------------------------------------------------------+--------
i+ | libQt5Xdg3               | Libraries for qtxdg                                      | package
i  | libQt5XdgIconLoader3     | IconLoader library for QtXDG                             | package
i  | python38-pyxdg           | Implementations of freedesktop.org standards in python   | package
i  | xdg-dbus-proxy           | Filtering proxy for D-Bus connections                    | package
i  | xdg-desktop-portal       | A portal frontend service for Flatpak                    | package
i  | xdg-desktop-portal-gnome | A backend implementation for xdg-desktop-portal          | package
i  | xdg-desktop-portal-gtk   | Backend implementation for xdg-desktop-portal using GTK+ | package
i+ | xdg-desktop-portal-wlr   | An xdg-desktop-portal backend for wlroots                | package
i+ | xdg-menu                 | XDG Menus for WindowMaker and other Window Managers      | package
i+ | xdg-user-dirs            | Utilities to handle user data directories                | package
i  | xdg-utils                | Utilities to uniformly interface desktop environments    | package
denisok commented 2 years ago

@mcepl I am not sure what means not useful. Could you please open new ticket? Please attach the log from the sway session? The one attached looks like from sway greetd session.

mcepl commented 2 years ago

@mcepl I am not sure what means not useful. Could you please open new ticket? Please attach the log from the sway session? The one attached looks like from sway greetd session.

Yes, sorry, this was a false alarm. Something's screwed up between pipewire from packman and the one from Factory.