[Desktop-packages] [Bug 1995730] Re: pulseaudio does not start automatically upon startup.
I found that installing the wireplumber package resolved this for me: sudo apt install wireplumber I'm guessing it's a missing dependency? Source was https://moisescardona.me/restoring-audio-after-upgrading- ubuntu-cinnamon-remix-22-04-to-ubuntu-22-10-development-version/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1995730 Title: pulseaudio does not start automatically upon startup. Status in pulseaudio package in Ubuntu: Confirmed Bug description: Recently updated to Ubuntu 22.10 from 22.04 LTS. (kernel - 5.19.0-23) There is no sound output unless pulseaudio is started manually. No output devices except dummy output, until pulseaudio is started. pulseaudio is enabled but is inactive(dead) until it is started using systemctl. Tested on kernels 5.19.0-23 and 5.15.0-52 but does not work. pulseaudio require manual startup. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4 20:00:12 2022 InstallationDate: Installed on 2022-05-16 (171 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-11-04 (0 days ago) dmi.bios.date: 07/16/2022 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0FNCYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/16/2022:br1.16:svnDellInc.:pnInspiron155501:pvr:rvnDellInc.:rn0FNCYP:rvrA00:cvnDellInc.:ct10:cvr:sku09E9: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 5501 dmi.product.sku: 09E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1995730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828908] Re: Relative symlink in /var/lib/transmission-daemon should be absolute
I think my report is not accurate. Replacing the symlink with an absolute one didn't help. Transmission seems to want to read my user dirs no matter what. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1828908 Title: Relative symlink in /var/lib/transmission-daemon should be absolute Status in transmission package in Ubuntu: New Bug description: ~ ⌘ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~ ⌘ apt-cache policy transmission-daemon transmission-daemon: Installed: 2.92-3ubuntu2 Candidate: 2.92-3ubuntu2 Version table: *** 2.92-3ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status After installing transmission-daemon, the directory /var/lib /transmission-daemon/ contains a directory symlinked to '.config /transmission-daemon': ~ ⌘ sudo ls -alh /var/lib/transmission-daemon/info lrwxrwxrwx 1 root root 27 Feb 7 2018 /var/lib/transmission-daemon/info -> .config/transmission-daemon Since this is a relative link, if I start transmission-daemon in an arbitrary directory, I get the following errors: ~ ⌘ sudo -u debian-transmission transmission-daemon -f --log-error --log-info --log-debug [2019-05-14 11:29:52.373] Couldn't read "/home/jason/.config/user-dirs.dirs": Permission denied [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Transmission 2.92 (14714) started (session.c:740) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.json": No such file or directory (utils.c:238) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:238) It seems like this should be an absolute link, since there actually is a directory /var/lib/transmission-daemon/info/.config/transmission- daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1828908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828908] [NEW] Relative symlink in /var/lib/transmission-daemon should be absolute
Public bug reported: ~ ⌘ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ~ ⌘ apt-cache policy transmission-daemon transmission-daemon: Installed: 2.92-3ubuntu2 Candidate: 2.92-3ubuntu2 Version table: *** 2.92-3ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status After installing transmission-daemon, the directory /var/lib /transmission-daemon/ contains a directory symlinked to '.config /transmission-daemon': ~ ⌘ sudo ls -alh /var/lib/transmission-daemon/info lrwxrwxrwx 1 root root 27 Feb 7 2018 /var/lib/transmission-daemon/info -> .config/transmission-daemon Since this is a relative link, if I start transmission-daemon in an arbitrary directory, I get the following errors: ~ ⌘ sudo -u debian-transmission transmission-daemon -f --log-error --log-info --log-debug [2019-05-14 11:29:52.373] Couldn't read "/home/jason/.config/user-dirs.dirs": Permission denied [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Transmission 2.92 (14714) started (session.c:740) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.json": No such file or directory (utils.c:238) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:238) It seems like this should be an absolute link, since there actually is a directory /var/lib/transmission-daemon/info/.config/transmission-daemon ** Affects: transmission (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1828908 Title: Relative symlink in /var/lib/transmission-daemon should be absolute Status in transmission package in Ubuntu: New Bug description: ~ ⌘ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~ ⌘ apt-cache policy transmission-daemon transmission-daemon: Installed: 2.92-3ubuntu2 Candidate: 2.92-3ubuntu2 Version table: *** 2.92-3ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status After installing transmission-daemon, the directory /var/lib /transmission-daemon/ contains a directory symlinked to '.config /transmission-daemon': ~ ⌘ sudo ls -alh /var/lib/transmission-daemon/info lrwxrwxrwx 1 root root 27 Feb 7 2018 /var/lib/transmission-daemon/info -> .config/transmission-daemon Since this is a relative link, if I start transmission-daemon in an arbitrary directory, I get the following errors: ~ ⌘ sudo -u debian-transmission transmission-daemon -f --log-error --log-info --log-debug [2019-05-14 11:29:52.373] Couldn't read "/home/jason/.config/user-dirs.dirs": Permission denied [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Couldn't create "/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189) [2019-05-14 11:29:53.628] Transmission 2.92 (14714) started (session.c:740) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.json": No such file or directory (utils.c:238) [2019-05-14 11:29:53.628] Couldn't read "/home/jason/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:238) It seems like this should be an absolute link, since there actually is a directory /var/lib/transmission-daemon/info/.config/transmission- daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1828908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749890] [NEW] Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share"
Public bug reported: Under 17.04, I had added an Owncloud account to the Gnome Online Accounts under Gnome 3. This created an entry in Nautilus' sidebar that allowed me to remotely browse my Owncloud account. Since upgrading to 17.10, clicking on the entry just brings up an error dialog: Unable to access "@" Not a WebDAV enabled share [OK] I get exactly the same error if I type "davs:///remote.php/webdav/" into the location field. I had earlier accessed the same server successfully that morning under 17.04, and I'm certain nothing's changed server side. Rebooting doesn't help, installing davfs2 doesn't help, neither does fusedav. I've tried removing and re-adding the account in Online Accounts. The server is accessible via web and the desktop sync client sees it fine. The server is not internal, it's on the public internet. There is a corporate proxy for which I use CNTLM. But again, this hasn't changed since before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 16 14:28:56 2018 InstallationDate: Installed on 2017-04-25 (296 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2018-01-24 (22 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1749890 Title: Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share" Status in nautilus package in Ubuntu: New Bug description: Under 17.04, I had added an Owncloud account to the Gnome Online Accounts under Gnome 3. This created an entry in Nautilus' sidebar that allowed me to remotely browse my Owncloud account. Since upgrading to 17.10, clicking on the entry just brings up an error dialog: Unable to access "@" Not a WebDAV enabled share [OK] I get exactly the same error if I type "davs:///remote.php/webdav/" into the location field. I had earlier accessed the same server successfully that morning under 17.04, and I'm certain nothing's changed server side. Rebooting doesn't help, installing davfs2 doesn't help, neither does fusedav. I've tried removing and re-adding the account in Online Accounts. The server is accessible via web and the desktop sync client sees it fine. The server is not internal, it's on the public internet. There is a corporate proxy for which I use CNTLM. But again, this hasn't changed since before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 16 14:28:56 2018 InstallationDate: Installed on 2017-04-25 (296 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2018-01-24 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1749890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
I just upgraded from 17.04, but it's impossible to complete the upgrade because of this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Network Proxy settings available under Settings/Network are not applied system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a proxy here: - does not modify /etc/environment - does not set root's http_proxy, https_proxy, ftp_proxy environment variables This means that apt and Software Updates do not receive the proxy settings, and package checks/updates/installs fail. workaround: sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261192] Re: Incorrect start on condition in upstart script for transmission-daemon
I can confirm that this problem exists in 14.04.1 LTS, and is fixed by changing the init script as per the original comment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1261192 Title: Incorrect start on condition in upstart script for transmission-daemon Status in “transmission” package in Ubuntu: Confirmed Bug description: Release: Ubuntu Server 13.10 x86_64 Package: transmission-daemon 2.82 After the system is booted transmission-daemon is not contactable on port 9091 using transmission-remote or the web interface. The daemon is however started and uploading/downloading. After the daemon is restarted everything works correctly. The 'start on' condition (in /etc/init/transmission-daemon.conf) currently reads as follows: start on (filesystem and net-device-up IFACE=lo) i.e. start after both the filesystem and loopback adapter are available. The transmission-daemon binds to 0.0.0.0:9091 on start up in order to listen for remote procedure calls and as such should wait for an adapter other than the loopback adapter to be available. The line should read as follows: start on (filesystem and net-device-up IFACE!=lo) PS At least I think that's what's going on (and this change has resolved my problem)... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1261192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
