From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Pipewire and Pipewire Pulse Not Properly Configured for Autostarting
Date: Tue, 09 Aug 2022 10:43:51 +0200 [thread overview]
Message-ID: <20220809084351.07KJpE53YtQfub9QL9nFo3SDx92KoEFChhp9rZ8AOdE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
Closed issue by TrueTechie on void-packages repository
https://github.com/void-linux/void-packages/issues/38541
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.16_1 x86_64 GenuineIntel uptodate FFFFFFF
### Package(s) Affected
pipewire-0.3.56_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The package places its autostart files in the XDG standard location `/etc/xdg/autostart` and thus start automatically without intervention by the user when installed. However, this would require the `pipewire-pulse` desktop file (and ideally the binary and other configuration tools, for organization sake) to be placed in separate, conflicting package since `pipewire` can also be used alongside `pulseaudio`.
### Actual behaviour
The two autostart files `pipewire.desktop` and `pipewire-pulse.desktop` are located in `/usr/share/applications` which has nothing to do with auto-starting applications, only listing them in menus and application runners.
### Steps to reproduce
1. Install the package `pipewire`
2. Log out from or otherwise restart desktop environment
3. Log back in, audio server does not automatically start
prev parent reply other threads:[~2022-08-09 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 22:24 [ISSUE] " TrueTechie
2022-08-08 23:03 ` paper42
2022-08-09 1:45 ` TrueTechie
2022-08-09 8:43 ` paper42
2022-08-09 8:43 ` paper42 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220809084351.07KJpE53YtQfub9QL9nFo3SDx92KoEFChhp9rZ8AOdE@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).