[SOLVED] GTK apps are very slow

Kaatios · 2024-09-02 23:11:05

This issue appeared three days ago, apps like Firefox, Virt Manager or Lutris do not load until ~25s have passed, so it may be a dbus timeout.
Already reinstalled the whole system, excepting /home partition and swap.
Tried reinstalling xdg-desktop-portal and xdg-desktop-portal-gtk.
I am using AwesomeWM and linux-hardened.

Some info that may be useful:

echo $XDG_CURRENT_DESKTOP
GNOME

cat /usr/share/xdg-desktop-portal/portals/gtk.portal
[portal]
DBusName=org.freedesktop.impl.portal.desktop.gtk
Interfaces=org.freedesktop.impl.portal.FileChooser;org.freedesktop.impl.portal.AppChooser;org.freedesktop.impl.portal.Print;org.freedesktop.impl.portal.Notification;org.freedesktop.impl.portal.Inhibit;org.freedesktop.impl.portal.Access;org.freedesktop.impl.portal.Account;org.freedesktop.impl.portal.Email;org.freedesktop.impl.portal.DynamicLauncher;org.freedesktop.impl.portal.Lockdown;org.freedesktop.impl.portal.Settings;
UseIn=gnome

cat .config/xdg-desktop-portal/portals.conf
[preferred]
default=gtk

Last edited by Kaatios (2024-09-06 23:26:16)

seth · 2024-09-02 23:27:07

Check the system journal after waiting for a client, xdg-desktop-portal issues tend to show up there.

1. how do you start awesome? Startx? Seen the last link below?
2. same issue w/ a non-hardened kernel?

Kaatios · 2024-09-02 23:40:16

seth wrote:

Check the system journal after waiting for a client, xdg-desktop-portal issues tend to show up there.

Do you mean like this?
https://pastebin.com/tCdM6Hrq
Used the linux kernel here, but I can't see anything wrong here.

seth wrote:

1. how do you start awesome? Startx? Seen the last link below?

Sorry, forgot to say that! I start it using LightDM. Do you need its config files too?

seth wrote:

2. same issue w/ a non-hardened kernel?

Yes, just tried with linux kernel, same thing.

seth · 2024-09-03 05:59:34

In doubt sudo it (for pot. more data, though this looks like part of the system journal) - and look at more context, xdg-desktop-portal wasn't triggered by whatever you did during that time
In doubt post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Sep 03 01:32:37 L15S xdg-desktop-por[1200]: PipeWire roundtrip timed out waiting for events
Sep 03 01:32:37 L15S xdg-desktop-por[1200]: Failed connect to PipeWire: No node factory discovered

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

And look for more pipewire related errors.

Lightdm is unlikely to leave you w/ a degenerated session except if you end up dbus-launch'ing awesome via the session setup scripts, a common awesome session service etc.

Kaatios · 2024-09-03 12:03:57

seth wrote:

xdg-desktop-portal wasn't triggered by whatever you did during that time

Didn't mention it, but I launched firefox to test it.

Here is the complete system journal.
https://0x0.st/Xwct.txt

Found some pipewire errors in the journal I posted above. I don't really understand them.

Sep 03 13:39:04 L15S pipewire[1013]: pw.context: 0x8ffb76cfa20: no modules loaded from context.modules

Sep 03 13:39:17 L15S xdg-desktop-por[1222]: PipeWire roundtrip timed out waiting for events
Sep 03 13:39:17 L15S xdg-desktop-por[1222]: Failed connect to PipeWire: No node factory discovered

seth wrote:

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
libvirtd-admin.socket                    | sockets.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants
virtlockd-admin.socket                   | sockets.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd-admin.socket                    | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
wireplumber.service                      | pipewire.service.wants

If pipewire is really the culprit, how can it be causing all this issues?

seth wrote:

Lightdm is unlikely to leave you w/ a degenerated session except if you end up dbus-launch'ing awesome via the session setup scripts, a common awesome session service etc.

Just for clearing up this, this is the relevant part of /etc/lightdm/lightdm.conf:

display-setup-script=autorandr --change && setxkbmap es
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=

seth · 2024-09-03 13:35:14

There's no sign of major portal (or pipewire) issues - 13s after your login.

GTK apps are very slow

apps like Firefox, Virt Manager or Lutris

Are "gtk3-demo-application" or https://archlinux.org/packages/extra/x86_64/l3afpad/ affected?

Last but not least, you're running awesome but set the DE to gnome. Don't.
In doubt rather try to remove the "UseIn=gnome" from the config - you'll probably have to restart the service.
I'd not be surprised if there's some gnome specific stuff going on in the implementation when gnome is "detected"

You can run "dbus-monitor --session" to track what's going on during the stall - whether and what FF etc. want to query and wait for.

Kaatios · 2024-09-03 18:33:27

Are "gtk3-demo-application" or https://archlinux.org/packages/extra/x86_64/l3afpad/ affected?

Yes, they are both affected.

Last but not least, you're running awesome but set the DE to gnome. Don't.

Oh, sorry, I thought that that was the thing to do when using a WM, as shown in here. Had that variable defined in .zshrc, I've removed it and now it's empty.

In doubt rather try to remove the "UseIn=gnome" from the config - you'll probably have to restart the service.

Done, removed it from /usr/share/xdg-desktop-portal/portals/gtk.portal and reloaded the daemon with systemctl daemon-reload.
No improvement.

You can run "dbus-monitor --session" to track what's going on during the stall - whether and what FF etc. want to query and wait for.

gtk3-demo-application log and firefox log

Both applications took some time to load, and hanged sometimes, until some time passed.

Maybe some of the info below might be useful?

echo $DBUS_SESSION_BUS_ADDRESS

unix:path=/run/user/1000/bus

systemctl --user status

● L15S
    State: running
    Units: 188 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Tue 2024-09-03 19:51:14 CEST; 36min ago
  systemd: 256.5-1-arch
   CGroup: /user.slice/user-1000.slice/user@1000.service
           ├─app.slice
           │ ├─app-dbus\x2d:1.16\x2dorg.a11y.atspi.Registry.slice
           │ │ └─dbus-:1.16-org.a11y.atspi.Registry@0.service
           │ │   └─1269 /usr/lib/at-spi2-registryd --use-gnome-session
           │ ├─dconf.service
           │ │ └─2490 /usr/lib/dconf-service
           │ └─xdg-desktop-portal-gtk.service
           │   └─1303 /usr/lib/xdg-desktop-portal-gtk
           ├─init.scope
           │ ├─1064 /usr/lib/systemd/systemd --user
           │ └─1066 "(sd-pam)"
           └─session.slice
             ├─at-spi-dbus-bus.service
             │ ├─1250 /usr/lib/at-spi-bus-launcher
             │ ├─1262 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/at-s
pi2/accessibility.conf --scope user
             │ └─1263 dbus-broker --log 4 --controller 9 --machine-id 2174cb5de3b047c3b1
2ed815e0f4b0a2 --max-bytes 100000000000000 --max-fds 6400000 --max-matches 5000000000
             ├─dbus-broker.service
             │ ├─1082 /usr/bin/dbus-broker-launch --scope user
             │ └─1083 dbus-broker --log 4 --controller 9 --machine-id 2174cb5de3b047c3b1
2ed815e0f4b0a2 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000
             ├─pipewire-pulse.service
             │ └─1076 /usr/bin/pipewire-pulse
             ├─pipewire.service
             │ └─1074 /usr/bin/pipewire
             ├─wireplumber.service
             │ └─1075 /usr/bin/wireplumber
             ├─xdg-desktop-portal.service
             │ └─1284 /usr/lib/xdg-desktop-portal
             ├─xdg-document-portal.service
             │ ├─1289 /usr/lib/xdg-document-portal
             │ └─1300 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=
portal -- /run/user/1000/doc
             └─xdg-permission-store.service
               └─1293 /usr/lib/xdg-permission-store

ps -df | grep dbus

dbus         569     568  0 19:23 ?        00:00:00 dbus-broker --log 4 --controller 9 --machine-id 2174cb5de3b047c3b12ed815e0f4b0a2 --max-bytes 536870912 --max-fds 4096 --max-matches 16384 --audit
k4ts0v      1083    1082  0 19:51 ?        00:00:00 dbus-broker --log 4 --controller 9 --machine-id 2174cb5de3b047c3b12ed815e0f4b0a2 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000
k4ts0v      1262    1250  0 19:51 ?        00:00:00 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/at-spi2/accessibility.conf --scope user
k4ts0v      1263    1262  0 19:51 ?        00:00:00 dbus-broker --log 4 --controller 9 --machine-id 2174cb5de3b047c3b12ed815e0f4b0a2 --max-bytes 100000000000000 --max-fds 6400000 --max-matches 5000000000
k4ts0v     12849    1319  0 20:31 pts/0    00:00:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox dbus

seth · 2024-09-03 20:08:44

The portal services start (and are running), dbus-monitor starts at 1725385966 then ~1725385986 (20s later) you'll have started gtk3-demo-application and the next dbus actions are around 1725386116 (30s gap) which are FS related signals.

So let's see where gtk3-demo-application is actually spending time:

strace -tt -f -o /tmp/gtk3-demo.strace gtk3-demo-application
cat /tmp/gtk3-demo.strace | curl -F 'file=@-' 0x0.st

Kaatios · 2024-09-03 21:52:10

There you go.
https://0x0.st/XwuZ.txt

I had to kill it using ctrl+c because it launched a dialog that didn't appear even after waiting for more than an hour.

seth · 2024-09-03 22:09:21

The strace covers ~90s?

Here's the gap:

82749 23:44:52.361195 futex(0x849190fb6b0, FUTEX_UNLOCK_PI_PRIVATE) = 0
82749 23:44:52.361243 futex(0x84919101dc8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY <unfinished ...>
82755 23:44:52.820952 <... futex resumed>) = -1 ETIMEDOUT (Connection timed out)
82755 23:44:52.821121 clock_gettime(CLOCK_MONOTONIC, {tv_sec=15697, tv_nsec=630949170}) = 0
82755 23:44:52.821342 clock_gettime(CLOCK_MONOTONIC, {tv_sec=15697, tv_nsec=631186840}) = 0
82755 23:44:52.821610 futex(0x84918f0c820, FUTEX_WAIT_PRIVATE, 0, {tv_sec=14, tv_nsec=999762160}) = -1 ETIMEDOUT (Connection timed out)
82755 23:45:07.822108 rt_sigprocmask(SIG_BLOCK, ~[RT_1], NULL, 8) = 0
82755 23:45:07.822338 madvise(0x671fbb600000, 8368128, MADV_DONTNEED) = 0
82755 23:45:07.822546 exit(0)           = ?
82755 23:45:07.822871 +++ exited with 0 +++
82756 23:45:22.391637 <... poll resumed>) = 0 (Timeout)
82756 23:45:22.391810 clock_gettime(CLOCK_MONOTONIC, {tv_sec=15727, tv_nsec=201661809}) = 0
82756 23:45:22.392115 futex(0x84919101dc8, FUTEX_WAKE_PRIVATE, 2147483647) = 1
82749 23:45:22.392267 <... futex resumed>) = 0

2 x 15s and this smells related to some pipe that looks like pulseaudio…

pacman -Qs 'wire|pulse'

Kaatios · 2024-09-03 22:46:37

The strace covers ~90s?

Yeah, I didn't wait too much.

this smells related to some pipe that looks like pulseaudio

I have no clue on how you deduced that pulseaudio was the culprit here.
Actually, I don't know what anything on the strace means.

pacman -Qs 'wire|pulse'

local/gtk-vnc 1.3.1-1
    VNC viewer widget for GTK
local/iwd 2.20-2
    Internet Wireless Daemon
local/iwgtk 0.9-1
    Lightweight wireless networking GUI (front-end for iwd)
local/lib32-libpipewire 1:1.2.3-1
    Low-latency audio/video router and processor - 32-bit - client library
local/lib32-libpulse 17.0-1
    A featureful, general-purpose sound server (32-bit client libraries)
local/lib32-pipewire 1:1.2.3-1
    Low-latency audio/video router and processor - 32-bit
local/libcanberra 1:0.30+r2+gc0620e4-4
    A small and lightweight implementation of the XDG Sound Theme Specification
local/libpipewire 1:1.2.3-1
    Low-latency audio/video router and processor - client library
local/libpulse 17.0-3
    A featureful, general-purpose sound server (client library)
local/libraw1394 2.1.2-4
    Provides an API to the Linux IEEE1394 (FireWire) driver
local/libwireplumber 0.5.5-1
    Session / policy manager implementation for PipeWire - client library
local/linux 6.10.7.arch1-1
    The Linux kernel and modules
local/linux-hardened 6.10.6.hardened1-1
    The Security-Hardened Linux kernel and modules
local/pavucontrol 1:6.1-1
    PulseAudio Volume Control
local/pipewire 1:1.2.3-1
    Low-latency audio/video router and processor
local/pipewire-alsa 1:1.2.3-1
    Low-latency audio/video router and processor - ALSA configuration
local/pipewire-audio 1:1.2.3-1
    Low-latency audio/video router and processor - Audio support
local/pipewire-pulse 1:1.2.3-1
    Low-latency audio/video router and processor - PulseAudio replacement
local/pipewire-session-manager 1:1.2.3-1
    Session manager for PipeWire (default provider)
local/qemu-audio-pa 9.0.2-1
    QEMU PulseAudio audio driver
local/qemu-audio-pipewire 9.0.2-1
    QEMU PipeWire audio driver
local/wireplumber 0.5.5-1
    Session / policy manager implementation for PipeWire
local/wpa_supplicant 2:2.11-2
    A utility providing key negotiation for WPA wireless networks

Removed libpulse, lib32-libpulse and qemu-audio-pa, and it all goes back to normal, excepting the said dialog that should appear on gtk3-demo-application. I guess that doesn't really matter?
Anyway, it seems pavucontrol requires libpulse as a dependency, and some electron versions, along with firefox and some other libraries. Wouldn't libpipewire work as a replacement? I don't know what to do now.

seth · 2024-09-04 07:36:43

excepting the said dialog that should appear on gtk3-demo-application

What? What dialog? You get something that looks like an application main window - I've never checked whether you can use the menu entries or so and I'd not worry all that much.

pipewire-pulse is supposed to provide a shim for pulseaudio, yes.
Does "pactl info" return immediately?
Does it help to clear the wireplumber state?
https://wiki.archlinux.org/title/PipeWi … ot_working

How do

mpv -ao pulse thunderstruck.mp3
mpv -ao pipewire thunderstruck.mp3
mpv -ao alsa thunderstruck.mp3

behave?

Do you have the same problem w/ a fresh user?

Kaatios · 2024-09-04 14:21:51

Does "pactl info" return immediately?

Without libpulse, it doesn't return anything, because it can't find that command.

Does it help to clear the wireplumber state?

No, it doesn't.

How do
mpv -ao pulse thunderstruck.mp3
mpv -ao pipewire thunderstruck.mp3
mpv -ao alsa thunderstruck.mp3
behave?

They don't do anything, because it needs the libpulse library.

mpv: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory

Should I reinstall it and retry?

seth · 2024-09-04 14:27:15

Should I reinstall it and retry?

Yeah, that was kinda the implication.

No, it doesn't.

Hold on, gtk apps still start slow despite removing libpulse? I was under the impression the latter had mitigated the former. No?

Kaatios · 2024-09-04 17:53:04

Hold on, gtk apps still start slow despite removing libpulse? I was under the impression the latter had mitigated the former. No?

Whoops, sorry, I thought you were referring to another thing. Regarding that, the apps start normally after removing libpulse, but now I can't start apps that require libpulse as a dependency (i.e. chromium or pavucontrol).

Yeah, that was kinda the implication.

I've got that problem again, the apps start slowly and hang from time to time.

Back to previous reply, pactl info does not return the info, it times out after 30s.
The mpv commands don't show any errors, but I can't hear anything. Maybe it's not detecting the soundcards properly? ALSA showed another soundcards and devices when this worked correctly... Same with discord, it should detect another devices.

Also cleared the wireplumber state, same result.

Last edited by Kaatios (2024-09-04 17:54:02)

seth · 2024-09-04 20:10:14

pactl info does not return the info, it times out after 30s

Did you try the behavior:
1. with a fresh user account
2. from the multi-user.target (console only login)
3. in doubt as root?

strace -f -tt -o /tmp/pulseaudio.sucks pactl info # wait
cat /tmp/pulseaudio.sucks | curl -F 'file=@-' 0x0.st # uploads the strace to 0x0.st and returns a ring

Kaatios · 2024-09-05 01:33:37

Tried all of that.

The test account and root give the same output when done from the terminal:

Connection failure: Connection refused
pa_context_connect() failed: Connection refused

However, in the console only login, only the root account gives that error. Using the test account, it gives the expected output.

Server String: /run/user/1001/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 76
Tile Size: 65472
User Name: test
Host Name: L15S
Server Name: PulseAudio (on PipeWire 1.2.3)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_03_00.6.HiFi__Speaker__sink
Default Source: alsa_input.pci-0000_03_00.6.HiFi__Mic1__source
Cookie: 06d6:904e

I'm afraid I can't upload the strace to 0x0, it doesn't work, so I uploaded it to bpaste.
https://bpa.st/DS36U

seth · 2024-09-05 06:21:26

311729 03:29:59.723640 openat(AT_FDCWD, "/home/k4ts0v/.config/pulse/cookie", O_RDONLY|O_NOCTTY|O_CLOEXEC) = 9
311729 03:29:59.723701 fcntl(9, F_GETFD) = 0x1 (flags FD_CLOEXEC)
311729 03:29:59.723806 fcntl(9, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1 EBADF (Bad file descriptor)

=> Remove the cookie.

Kaatios · 2024-09-05 13:10:42

Same result.

Here is a new strace after removing the cookie.
https://bpa.st/PXSO6

seth · 2024-09-05 13:36:24

2598  15:06:31.146603 openat(AT_FDCWD, "/home/k4ts0v/.config/pulse/cookie", O_RDONLY|O_NOCTTY|O_CLOEXEC) = 9
2598  15:06:31.146640 fcntl(9, F_GETFD) = 0x1 (flags FD_CLOEXEC)
2598  15:06:31.146670 fcntl(9, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1 EBADF (Bad file descriptor)
2598  15:06:31.146705 fcntl(9, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
2598  15:06:31.146738 read(9, "\261\33\"\356\30\6\2316Ej\270r\202y\373\210%\364[\1\327\3<\34\315L)G\226,\321\274"..., 256) = 256
2598  15:06:31.146771 fcntl(9, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
2598  15:06:31.146802 close(9)          = 0

Cookie is still there?

2598  15:06:31.148368 read(3, 0x7fb2a3a34d4e, 10) = -1 EAGAIN (Resource temporarily unavailable)
2598  15:06:31.148399 ppoll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}], 3, {tv_sec=29, tv_nsec=999827000}, NULL, 8) = 0 (Timeout)

Which is a pipe

2598  15:06:31.141354 pipe2([3, 4], O_CLOEXEC) = 0

What does the strace for the working test user look like?
Andm just a hunch: What's you main users login shell?
Do the pipewire/pulse processes crash?

ps aux | grep -E '(wire|pulse)'
pactl info
ps aux | grep -E '(wire|pulse)'

Kaatios · 2024-09-05 18:01:22

Cookie is still there?

I thought I deleted it, did rm -rf .config/pulse/cookie and checked that directory, it wasn't there.

What does the strace for the working test user look like?

https://bpa.st/ALQV6

What's you main users login shell?

Zsh (/usr/bin/zsh).
The root and test user's shell is Bash (/usr/bin/bash).

Do the pipewire/pulse processes crash?

They don't seem to crash, right?

k4ts0v       980  0.0  0.0   8932  4404 ?        Ss   16:31   0:00 /usr/bin/pipewire
k4ts0v       981  0.0  0.0 162660  7036 ?        S<sl 16:31   0:00 /usr/bin/wireplumber
k4ts0v       982  0.0  0.0  97468  7564 ?        S<sl 16:31   0:00 /usr/bin/pipewire-pulse
test        2047  0.0  0.0  99560 10448 ?        S<sl 16:32   0:00 /usr/bin/pipewire
test        2048  0.1  0.1 472836 16088 ?        S<sl 16:32   0:00 /usr/bin/wireplumber
test        2050  0.0  0.0  97704  7824 ?        S<sl 16:32   0:00 /usr/bin/pipewire-pulse
k4ts0v      5149  0.0  0.0   6644  2568 pts/0    S+   16:35   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox -E (wire|pulse)
Connection failure: Timeout
k4ts0v       980  0.0  0.0   8932  4404 ?        Ss   16:31   0:00 /usr/bin/pipewire
k4ts0v       981  0.0  0.0 162660  7036 ?        S<sl 16:31   0:00 /usr/bin/wireplumber
k4ts0v       982  0.0  0.0  97468  7564 ?        S<sl 16:31   0:00 /usr/bin/pipewire-pulse
test        2047  0.0  0.0  99560 10448 ?        S<sl 16:32   0:00 /usr/bin/pipewire
test        2048  0.1  0.1 472836 16088 ?        S<sl 16:32   0:00 /usr/bin/wireplumber
test        2050  0.0  0.0  97704  7824 ?        S<sl 16:32   0:00 /usr/bin/pipewire-pulse
k4ts0v      5266  0.0  0.0   6640  2424 pts/0    S+   16:36   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox -E (wire|pulse)

seth · 2024-09-05 19:21:29

The ppol times out for your pain user, but there's no significant difference building up to that

ls -lR ~/.config/*{pulse,wire}*

Back to

The mpv commands don't show any errors, but I can't hear anything. Maybe it's not detecting the soundcards properly? ALSA showed another soundcards and devices when this worked correctly... Same with discord, it should detect another devices.

Can you elaborate what alsa did show - or at least what it shows now?
https://github.com/termux/termux-packages/issues/19861 suggests relation to a BT (audio?) device…

You test user can play "mpv -ao pulse thunderstruck.mp3"?
What does alsa show for that user?

Kaatios · 2024-09-05 20:23:28

Can you elaborate what alsa did show - or at least what it shows now?

Well, now I noticed I didn't really mean ALSA, I meant pulseaudio / pipewire instead, sorry.
What I was trying to say was that some apps detected my devices correctly using the test user, for example, in the paste below you can see a sink called "Family 17h/19h HD Audio Controller Speaker", which is the laptop's speaker. But, using another users, (root or the main one), apps like Discord or Audacity do not show them, and only show other devices that do not seem familiar, and I assume that devices are related to ALSA. I don't know how to check them now, sorry.
It seems the test user works fine. Here is what pactl list cards show: https://bpa.st/YJBAY
Also, neither the main user or root can start alsamixer, it hangs. The test user can, all works as expected there.

You test user can play "mpv -ao pulse thunderstruck.mp3"?

Didn't check if there is really an output, but it seems to play without errors.

seth · 2024-09-05 20:44:09

They'll probably show dummies because PA doesn't respond.

seth wrote:

ls -lR ~/.config/*{pulse,wire}*

There has to be some custom element to the main user, most likely some config - maybe some environment variable.

Kaatios · 2024-09-05 21:59:11

ls -lR ~/.config/*{pulse,wire}*

Forgot about that, here it is.

/home/k4ts0v/.config/pipewire:
total 8
drwxr-xr-x 2 k4ts0v k4ts0v 4096 Aug 31 04:22 media-session.d
-rw-r--r-- 1 k4ts0v k4ts0v   71 Sep  1 02:14 pipewire.conf

/home/k4ts0v/.config/pipewire/media-session.d:
total 4
-rw-r--r-- 1 k4ts0v k4ts0v 113 Aug 31 04:03 alsa-monitor.conf

/home/k4ts0v/.config/pulse:
total 0

/home/k4ts0v/.config/wireplumber:
total 4
drwxr-xr-x 2 k4ts0v k4ts0v 4096 Sep  1 02:15 wireplumber.conf.d

/home/k4ts0v/.config/wireplumber/wireplumber.conf.d:
total 4
-rw-r--r-- 1 k4ts0v k4ts0v 655 Sep  1 02:15 51-disable-suspension.conf

There has to be some custom element to the main user, most likely some config - maybe some environment variable.

That would explain it, but what about root?

Here are the environment variables:

COLORTERM=truecolor
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
DESKTOP_SESSION=awesome
DESKTOP_STARTUP_ID=awesome/wezterm/981-0-L15S_TIME5515913
DISPLAY=:0
GDMSESSION=awesome
GTK_MODULES=canberra-gtk-module
HG=/usr/bin/hg
HOME=/home/k4ts0v
LANG=en_US.UTF-8
LOGNAME=k4ts0v
MAIL=/var/spool/mail/k4ts0v
MOTD_SHOWN=pam
OLDPWD=/home/k4ts0v
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/home/k4ts0v/.dotnet/tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/k4ts0v/.local/bin:/home/k4ts0v/.local/bin:/bin:/usr/lib/jvm/java-17-jdk/bin:/usr/lib/jvm/java-17-jdk/bin
PWD=/home/k4ts0v
SHELL=/usr/bin/zsh
SHLVL=1
TERM=xterm-256color
TERM_PROGRAM=WezTerm
TERM_PROGRAM_VERSION=20240203-110809-5046fc22
USER=k4ts0v
WEZTERM_CONFIG_DIR=/home/k4ts0v/.config/wezterm
WEZTERM_CONFIG_FILE=/home/k4ts0v/.config/wezterm/wezterm.lua
WEZTERM_EXECUTABLE=/usr/bin/wezterm-gui
WEZTERM_EXECUTABLE_DIR=/usr/bin
WEZTERM_PANE=0
WEZTERM_UNIX_SOCKET=/run/user/1000/wezterm/gui-sock-47416
XAUTHORITY=/home/k4ts0v/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/k4ts0v
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=awesome
XDG_SESSION_ID=2
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SESSION_TYPE=x11
XDG_VTNR=7
_=/usr/bin/printenv
EDITOR=vim
PAGER=more
LSCOLORS=Gxfxcxdxbxegedabagacad
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.7z=01;31:*.ace=01;31:*.alz=01;31:*.apk=01;31:*.arc=01;31:*.arj=01;31:*.bz=01;31:*.bz2=01;31:*.cab=01;31:*.cpio=01;31:*.crate=01;31:*.deb=01;31:*.drpm=01;31:*.dwm=01;31:*.dz=01;31:*.ear=01;31:*.egg=01;31:*.esd=01;31:*.gz=01;31:*.jar=01;31:*.lha=01;31:*.lrz=01;31:*.lz=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.lzo=01;31:*.pyz=01;31:*.rar=01;31:*.rpm=01;31:*.rz=01;31:*.sar=01;31:*.swm=01;31:*.t7z=01;31:*.tar=01;31:*.taz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tgz=01;31:*.tlz=01;31:*.txz=01;31:*.tz=01;31:*.tzo=01;31:*.tzst=01;31:*.udeb=01;31:*.war=01;31:*.whl=01;31:*.wim=01;31:*.xz=01;31:*.z=01;31:*.zip=01;31:*.zoo=01;31:*.zst=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.crdownload=00;90:*.dpkg-dist=00;90:*.dpkg-new=00;90:*.dpkg-old=00;90:*.dpkg-tmp=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:*.swp=00;90:*.tmp=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:
JAVA_HOME=/usr/lib/jvm/java-17-jdk/
SSH_AUTH_SOCK=/run/user/1000/ssh-agent.socket

Last edited by Kaatios (2024-09-05 22:12:20)

Arch Linux

#1 2024-09-02 23:11:05

[SOLVED] GTK apps are very slow

#2 2024-09-02 23:27:07

Re: [SOLVED] GTK apps are very slow

#3 2024-09-02 23:40:16

Re: [SOLVED] GTK apps are very slow

#4 2024-09-03 05:59:34

Re: [SOLVED] GTK apps are very slow

#5 2024-09-03 12:03:57

Re: [SOLVED] GTK apps are very slow

#6 2024-09-03 13:35:14

Re: [SOLVED] GTK apps are very slow

#7 2024-09-03 18:33:27

Re: [SOLVED] GTK apps are very slow

#8 2024-09-03 20:08:44

Re: [SOLVED] GTK apps are very slow

#9 2024-09-03 21:52:10

Re: [SOLVED] GTK apps are very slow

#10 2024-09-03 22:09:21

Re: [SOLVED] GTK apps are very slow

#11 2024-09-03 22:46:37

Re: [SOLVED] GTK apps are very slow

#12 2024-09-04 07:36:43

Re: [SOLVED] GTK apps are very slow

#13 2024-09-04 14:21:51

Re: [SOLVED] GTK apps are very slow

#14 2024-09-04 14:27:15

Re: [SOLVED] GTK apps are very slow

#15 2024-09-04 17:53:04

Re: [SOLVED] GTK apps are very slow

#16 2024-09-04 20:10:14

Re: [SOLVED] GTK apps are very slow

#17 2024-09-05 01:33:37

Re: [SOLVED] GTK apps are very slow

#18 2024-09-05 06:21:26

Re: [SOLVED] GTK apps are very slow

#19 2024-09-05 13:10:42

Re: [SOLVED] GTK apps are very slow

#20 2024-09-05 13:36:24

Re: [SOLVED] GTK apps are very slow

#21 2024-09-05 18:01:22

Re: [SOLVED] GTK apps are very slow

#22 2024-09-05 19:21:29

Re: [SOLVED] GTK apps are very slow

#23 2024-09-05 20:23:28

Re: [SOLVED] GTK apps are very slow

#24 2024-09-05 20:44:09

Re: [SOLVED] GTK apps are very slow

#25 2024-09-05 21:59:11

Re: [SOLVED] GTK apps are very slow

Board footer