unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: Sergey Trofimov <sarg@sarg.org.ru>
Cc: 68512@debbugs.gnu.org
Subject: bug#68512: Qutebrowser 3, no sound from pipewire-only system
Date: Thu, 25 Jan 2024 15:26:43 -0800	[thread overview]
Message-ID: <ZbLuM54i2dEdgZTN@guix-xps> (raw)
In-Reply-To: <87o7d9utz9.fsf@sarg.org.ru>

On  1月25日 木, Sergey Trofimov wrote:
> 
> I'm glad you sorted it out. Check what are the environment variables for
> your sway process (cat /proc/<pid>/environ | tr -s '\0' '\n').
> Maybe XDG_RUNTIME_DIR is missing there? Enabling debug logging for pipewire
> might help as well: https://docs.pipewire.org/page_daemon.html

Sergey,

Yesterday after reporting back here, I found that I was able to change the commands used by sway from this
```
exec_always killall -wqr "(pipewire|wireplumber)" \
  || sleep 1 && ((pipewire &); sleep 2 && (wireplumber &))
```

To this
```
exec sleep 2 && pipewire
exec sleep 4 && wireplumber
```

sound is working each time the machine is started or restarted.

In order to script-generate the asoundrc file, I wish to use pipewire's store directory path inside a scheme function. WOuld you teach me how to do this? eg, `$(guix build pipewire) # /gnu/store/8572wxb5138hanhvn1lbfdm1kicxsd2k-pipewire-1.0.0`

No success trying various things from this thread https://www.mail-archive.com/help-guix@gnu.org/msg11871.html

'have also tried the following
```
(use-modules (gnu packages linux)
             (gnu packages build-tools)
             (gnu packages package-management))

(guix build pipewire)
```

running the file fails with this message:
```
Wrong type to apply: #<package guix@1.4.0-15.e0885fc gnu/packages/package-management.scm:179 7fd6dfe0ebb0>
```

Thanks in advance for any recommendations or advice. Thank you for conversing with me and helping me thus far,

Chris





  reply	other threads:[~2024-01-25 23:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 16:43 bug#68512: Qutebrowser 3, no sound from pipewire-only system chris
2024-01-16 17:30 ` chris
2024-01-16 17:39 ` chris
2024-01-16 18:12   ` chris
2024-01-16 19:25 ` Sergey Trofimov
2024-01-16 20:49   ` chris
2024-01-17  6:58     ` Sergey Trofimov
2024-01-17  9:49       ` chris
2024-01-17  9:56         ` chris
2024-01-25  9:09         ` chris
2024-01-25 18:37           ` Sergey Trofimov
2024-01-25 23:26             ` chris [this message]
2024-01-26  5:56               ` Sergey Trofimov
2024-01-26  8:18                 ` chris
2024-01-26 12:46                   ` Sergey Trofimov
2024-01-26 23:35                     ` chris
2024-01-26  0:00             ` chris
2024-01-26  6:10               ` Sergey Trofimov
2024-01-26  8:19                 ` chris
2024-01-26  9:45                 ` Clément Lassieur
2024-01-26 23:32                   ` chris
2024-01-26  9:10 ` bug#68512: done chris

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=ZbLuM54i2dEdgZTN@guix-xps \
    --to=chris@bumblehead.com \
    --cc=68512@debbugs.gnu.org \
    --cc=sarg@sarg.org.ru \
    /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).