[Touch-packages] [Bug 1942363] Re: apport-bug unusably broken
** Attachment added: "Wat" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1942363/+attachment/5522348/+files/apport2.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1942363 Title: apport-bug unusably broken Status in apport package in Ubuntu: New Bug description: For a regarding LibreOffice Calc, I started apport-cli in order to submit a bug report. Attached picture #1 shows the second screen of apport. I'm not reporting a display problem, but I've chosen "Other problem" before. And "I don't know" isn't exactly the correct option, "Neither of those" would be more accurate. Picture #2 shows the collection of information. There isn't really anything to collect in my case, so I'd rather not have apport attach random data. Picture #3 shows the result of the collection. No idea. Pressing Cancel yields another one of those windows. How are we supposed to submit bug reports? Especially since the link to manually report a bug is buried in very long list of things that could go wrong on a random web page. Kindly fix apport-cli so that bug reporting is possible (or make manual reporting easier). *** Description:Ubuntu 20.04.3 LTS Release:20.04 apport: Installed: 2.20.11-0ubuntu27.18 Candidate: 2.20.11-0ubuntu27.18 Version table: *** 2.20.11-0ubuntu27.18 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1942363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942363] Re: apport-bug unusably broken
** Attachment added: "Collecting" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1942363/+attachment/5522347/+files/apport1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1942363 Title: apport-bug unusably broken Status in apport package in Ubuntu: New Bug description: For a regarding LibreOffice Calc, I started apport-cli in order to submit a bug report. Attached picture #1 shows the second screen of apport. I'm not reporting a display problem, but I've chosen "Other problem" before. And "I don't know" isn't exactly the correct option, "Neither of those" would be more accurate. Picture #2 shows the collection of information. There isn't really anything to collect in my case, so I'd rather not have apport attach random data. Picture #3 shows the result of the collection. No idea. Pressing Cancel yields another one of those windows. How are we supposed to submit bug reports? Especially since the link to manually report a bug is buried in very long list of things that could go wrong on a random web page. Kindly fix apport-cli so that bug reporting is possible (or make manual reporting easier). *** Description:Ubuntu 20.04.3 LTS Release:20.04 apport: Installed: 2.20.11-0ubuntu27.18 Candidate: 2.20.11-0ubuntu27.18 Version table: *** 2.20.11-0ubuntu27.18 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1942363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942363] [NEW] apport-bug unusably broken
Public bug reported: For a regarding LibreOffice Calc, I started apport-cli in order to submit a bug report. Attached picture #1 shows the second screen of apport. I'm not reporting a display problem, but I've chosen "Other problem" before. And "I don't know" isn't exactly the correct option, "Neither of those" would be more accurate. Picture #2 shows the collection of information. There isn't really anything to collect in my case, so I'd rather not have apport attach random data. Picture #3 shows the result of the collection. No idea. Pressing Cancel yields another one of those windows. How are we supposed to submit bug reports? Especially since the link to manually report a bug is buried in very long list of things that could go wrong on a random web page. Kindly fix apport-cli so that bug reporting is possible (or make manual reporting easier). *** Description:Ubuntu 20.04.3 LTS Release:20.04 apport: Installed: 2.20.11-0ubuntu27.18 Candidate: 2.20.11-0ubuntu27.18 Version table: *** 2.20.11-0ubuntu27.18 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Problem kind" https://bugs.launchpad.net/bugs/1942363/+attachment/5522346/+files/apport0.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1942363 Title: apport-bug unusably broken Status in apport package in Ubuntu: New Bug description: For a regarding LibreOffice Calc, I started apport-cli in order to submit a bug report. Attached picture #1 shows the second screen of apport. I'm not reporting a display problem, but I've chosen "Other problem" before. And "I don't know" isn't exactly the correct option, "Neither of those" would be more accurate. Picture #2 shows the collection of information. There isn't really anything to collect in my case, so I'd rather not have apport attach random data. Picture #3 shows the result of the collection. No idea. Pressing Cancel yields another one of those windows. How are we supposed to submit bug reports? Especially since the link to manually report a bug is buried in very long list of things that could go wrong on a random web page. Kindly fix apport-cli so that bug reporting is possible (or make manual reporting easier). *** Description:Ubuntu 20.04.3 LTS Release:20.04 apport: Installed: 2.20.11-0ubuntu27.18 Candidate: 2.20.11-0ubuntu27.18 Version table: *** 2.20.11-0ubuntu27.18 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1942363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902427] Re: systemd pauses for unspecified reason
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902427 Title: systemd pauses for unspecified reason Status in systemd package in Ubuntu: Invalid Bug description: I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I noticed that the boot time (time between entering LUKS credentials and appearance of login screen) took more than 1 minute. Using `systemd-analyze`, I found the following: ``` cassiopeia:~# systemd-analyze Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s graphical.target reached after 1min 32.144s in userspace cassiopeia:~# systemd-analyze blame 4.721s fstrim.service 2.949s apt-daily-upgrade.service 2.380s systemd-cryptsetup@store.service 1.739s NetworkManager-wait-online.service 439ms apt-daily.service 421ms man-db.service 398ms systemd-logind.service 323ms dev-mapper-root.device 294ms systemd-fsck@dev-mapper-store.service 204ms logrotate.service 153ms systemd-journald.service ... cassiopeia:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 32.144s └─multi-user.target @1min 32.144s └─fetchmail.service @1min 32.128s +16ms └─network-online.target @1min 32.127s └─NetworkManager-wait-online.service @1min 30.388s +1.739s └─NetworkManager.service @1min 30.282s +105ms └─dbus.service @1min 30.279s └─basic.target @1min 30.265s └─sockets.target @1min 30.265s └─snapd.socket @1min 30.264s +370us └─sysinit.target @1min 30.262s └─systemd-timesyncd.service @1min 30.219s +42ms └─systemd-tmpfiles-setup.service @1min 30.202s +15ms └─systemd-journal-flush.service @288ms +49ms └─systemd-journald.service @131ms +153ms └─systemd-journald.socket @129ms └─-.mount @127ms └─blockdev@dev-mapper-root.target @410ms └─systemd-cryptsetup@root.service @401ms +8ms └─dev-nvme0n1p2.device @398ms ``` This didn't really help, but `systemd-analyze plot > boot.svg` produced an SVG file (see attachment) that shows a gap between store.mount (completes within 38 ms) and apparmor.service of almost 1:30 minutes. What did systemd do during this gap? I think it is either a bug in systemd that idles, or in systemd- analyze that doesn't disclose the actions in that gap. (Note: I have posted this question in two well-known Ubuntu forums, but I didn't receive any answers.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904769] [NEW] Installed chromium-browser does not work
Public bug reported: Since I need Chrome, I installed chromium-browser and snapd in aptitude. But Chrome didn't appear in the menu, and launching it from the console yields cassiopeia ~ > chromium-browser Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium cassiopeia ~ > snap install chromium error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory I would have thought that chromium-browser does install the chromium snap. So what does it mean, and how do I fix it? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904769 Title: Installed chromium-browser does not work Status in chromium-browser package in Ubuntu: New Bug description: Since I need Chrome, I installed chromium-browser and snapd in aptitude. But Chrome didn't appear in the menu, and launching it from the console yields cassiopeia ~ > chromium-browser Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium cassiopeia ~ > snap install chromium error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory I would have thought that chromium-browser does install the chromium snap. So what does it mean, and how do I fix it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1904769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902427] Re: systemd pauses for unspecified reason
The issue was indeed /etc/fstab, which contained a UUID inserted by the installer. Removing the UUID by the actual device name removed the 1:30 minutes delay. You might argue that this is a bug by itself, but it's good enough for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902427 Title: systemd pauses for unspecified reason Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I noticed that the boot time (time between entering LUKS credentials and appearance of login screen) took more than 1 minute. Using `systemd-analyze`, I found the following: ``` cassiopeia:~# systemd-analyze Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s graphical.target reached after 1min 32.144s in userspace cassiopeia:~# systemd-analyze blame 4.721s fstrim.service 2.949s apt-daily-upgrade.service 2.380s systemd-cryptsetup@store.service 1.739s NetworkManager-wait-online.service 439ms apt-daily.service 421ms man-db.service 398ms systemd-logind.service 323ms dev-mapper-root.device 294ms systemd-fsck@dev-mapper-store.service 204ms logrotate.service 153ms systemd-journald.service ... cassiopeia:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 32.144s └─multi-user.target @1min 32.144s └─fetchmail.service @1min 32.128s +16ms └─network-online.target @1min 32.127s └─NetworkManager-wait-online.service @1min 30.388s +1.739s └─NetworkManager.service @1min 30.282s +105ms └─dbus.service @1min 30.279s └─basic.target @1min 30.265s └─sockets.target @1min 30.265s └─snapd.socket @1min 30.264s +370us └─sysinit.target @1min 30.262s └─systemd-timesyncd.service @1min 30.219s +42ms └─systemd-tmpfiles-setup.service @1min 30.202s +15ms └─systemd-journal-flush.service @288ms +49ms └─systemd-journald.service @131ms +153ms └─systemd-journald.socket @129ms └─-.mount @127ms └─blockdev@dev-mapper-root.target @410ms └─systemd-cryptsetup@root.service @401ms +8ms └─dev-nvme0n1p2.device @398ms ``` This didn't really help, but `systemd-analyze plot > boot.svg` produced an SVG file (see attachment) that shows a gap between store.mount (completes within 38 ms) and apparmor.service of almost 1:30 minutes. What did systemd do during this gap? I think it is either a bug in systemd that idles, or in systemd- analyze that doesn't disclose the actions in that gap. (Note: I have posted this question in two well-known Ubuntu forums, but I didn't receive any answers.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902427] [NEW] systemd pauses for unspecified reason
Public bug reported: I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I noticed that the boot time (time between entering LUKS credentials and appearance of login screen) took more than 1 minute. Using `systemd-analyze`, I found the following: ``` cassiopeia:~# systemd-analyze Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s graphical.target reached after 1min 32.144s in userspace cassiopeia:~# systemd-analyze blame 4.721s fstrim.service 2.949s apt-daily-upgrade.service 2.380s systemd-cryptsetup@store.service 1.739s NetworkManager-wait-online.service 439ms apt-daily.service 421ms man-db.service 398ms systemd-logind.service 323ms dev-mapper-root.device 294ms systemd-fsck@dev-mapper-store.service 204ms logrotate.service 153ms systemd-journald.service ... cassiopeia:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 32.144s └─multi-user.target @1min 32.144s └─fetchmail.service @1min 32.128s +16ms └─network-online.target @1min 32.127s └─NetworkManager-wait-online.service @1min 30.388s +1.739s └─NetworkManager.service @1min 30.282s +105ms └─dbus.service @1min 30.279s └─basic.target @1min 30.265s └─sockets.target @1min 30.265s └─snapd.socket @1min 30.264s +370us └─sysinit.target @1min 30.262s └─systemd-timesyncd.service @1min 30.219s +42ms └─systemd-tmpfiles-setup.service @1min 30.202s +15ms └─systemd-journal-flush.service @288ms +49ms └─systemd-journald.service @131ms +153ms └─systemd-journald.socket @129ms └─-.mount @127ms └─blockdev@dev-mapper-root.target @410ms └─systemd-cryptsetup@root.service @401ms +8ms └─dev-nvme0n1p2.device @398ms ``` This didn't really help, but `systemd-analyze plot > boot.svg` produced an SVG file (see attachment) that shows a gap between store.mount (completes within 38 ms) and apparmor.service of almost 1:30 minutes. What did systemd do during this gap? I think it is either a bug in systemd that idles, or in systemd-analyze that doesn't disclose the actions in that gap. (Note: I have posted this question in two well-known Ubuntu forums, but I didn't receive any answers.) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot.svg" https://bugs.launchpad.net/bugs/1902427/+attachment/5429998/+files/boot.svg ** Package changed: snapd (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902427 Title: systemd pauses for unspecified reason Status in systemd package in Ubuntu: New Bug description: I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I noticed that the boot time (time between entering LUKS credentials and appearance of login screen) took more than 1 minute. Using `systemd-analyze`, I found the following: ``` cassiopeia:~# systemd-analyze Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s graphical.target reached after 1min 32.144s in userspace cassiopeia:~# systemd-analyze blame 4.721s fstrim.service 2.949s apt-daily-upgrade.service 2.380s systemd-cryptsetup@store.service 1.739s NetworkManager-wait-online.service 439ms apt-daily.service 421ms man-db.service 398ms systemd-logind.service 323ms dev-mapper-root.device 294ms systemd-fsck@dev-mapper-store.service 204ms logrotate.service 153ms systemd-journald.service ... cassiopeia:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 32.144s └─multi-user.target @1min 32.144s └─fetchmail.service @1min 32.128s +16ms └─network-online.target @1min 32.127s └─NetworkManager-wait-online.service @1min 30.388s +1.739s └─NetworkManager.service @1min 30.282s +105ms └─dbus.service @1min 30.279s └─basic.target @1min 30.265s └─sockets.target @1min 30.265s └─snapd.socket @1min 30.264s +370us └─sysinit.target @1min 30.262s
[Touch-packages] [Bug 1902352] [NEW] apt-get -u upgrade yields "-bash: /usr/bin/snap: No such file or directory"
Public bug reported: I'm running Kubuntu 20.04. To the best of my knowledge, I purged all snap-related packages, including snap itself. Now, every time I update my packages with `apt-get update && apt-get -u upgrade`, I get this output at the end: -bash: /usr/bin/snap: No such file or directory How can I get rid of this message? ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => snap (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902352 Title: apt-get -u upgrade yields "-bash: /usr/bin/snap: No such file or directory" Status in snap package in Ubuntu: New Bug description: I'm running Kubuntu 20.04. To the best of my knowledge, I purged all snap-related packages, including snap itself. Now, every time I update my packages with `apt-get update && apt-get -u upgrade`, I get this output at the end: -bash: /usr/bin/snap: No such file or directory How can I get rid of this message? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1902352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899352] Re: Pulseaudio cannot be kept from starting or respawning
The package "pulseaudio" contains the files: /usr/bin/start-pulseaudio-x11 /etc/pulse/client.conf.d/01-enable-autospawn.conf Thus, it should be fairly obvious where I got the files from. And /etc/pulse/client.conf is ignored, despite my user (and root) not having a ~/.local/pulse directory. And why would we need files for non-systemd systems if Ubuntu _is_ a systemd-base system? So I still think something is quite wrong with the pulseaudio package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899352 Title: Pulseaudio cannot be kept from starting or respawning Status in pulseaudio package in Ubuntu: Invalid Bug description: On my freshly installed system, I need to run pulseaudio in system mode. Alas, by default, pulseaudio is run in user mode, and is set to respawn, so that I cannot kill the user process and start pulseaudio in system mode. I tried: 1. Editing /etc/pulse/client.conf, setting autospawn = no. This did nothing. 2. Removing the file /etc/pulse/client.conf.d/01-respawn-something. I cannot even begin to fathom why such a file would exist. Anyway, this did nothing. 3. I removed the file /usr/bin/start-pulseaudio. Why Of course, this did nothing. 4. I removed the file /etc/xdg/autostart/pulseaudio.desktop. Why on earth do you implement four different ways to annoy your users? On the other hand, this did NOTHING. User mode is still starting, and respawning is enabled. What the heck do I have to do to get rid of user mode pulseaudio? Could you please clean up this clusterfuck? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899352] Re: Pulseaudio cannot be kept from starting or respawning
Thanks, that's fair enough. My remaining questions then are: 1. Why is /usr/bin/start-pulseaudio needed? 2. Why is /etc/pulse/client.conf ignored? 3. In light of 2, why is /etc/pulse/client.conf.d/01-respawn-something needed? 4. And in light of /lib/systemd/user/pulseaudio.service, why is /etc/xdg/autostart/pulseaudio.desktop needed? Wouldn't one way to start pulseaudio be sufficient? Also, please don't ignore the configuration. Finally, how can I use any of these methods to start pulseaudio in system mode? Adding -D to /lib/systemd/user/pulseaudio.service did not work (probably because I'm not root). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899352 Title: Pulseaudio cannot be kept from starting or respawning Status in pulseaudio package in Ubuntu: Invalid Bug description: On my freshly installed system, I need to run pulseaudio in system mode. Alas, by default, pulseaudio is run in user mode, and is set to respawn, so that I cannot kill the user process and start pulseaudio in system mode. I tried: 1. Editing /etc/pulse/client.conf, setting autospawn = no. This did nothing. 2. Removing the file /etc/pulse/client.conf.d/01-respawn-something. I cannot even begin to fathom why such a file would exist. Anyway, this did nothing. 3. I removed the file /usr/bin/start-pulseaudio. Why Of course, this did nothing. 4. I removed the file /etc/xdg/autostart/pulseaudio.desktop. Why on earth do you implement four different ways to annoy your users? On the other hand, this did NOTHING. User mode is still starting, and respawning is enabled. What the heck do I have to do to get rid of user mode pulseaudio? Could you please clean up this clusterfuck? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899352] Re: Pulseaudio cannot be kept from starting or respawning
Also, as user: cassiopeia ~ > pulseaudio -k N: [pulseaudio] main.c: System mode refused for non-root user. Only starting the D-Bus server lookup service. Then, as root, with system mode running: cassiopeia:~# ps aux | grep pulse pulse 2334 0.0 0.0 239320 10568 ?Shttps://bugs.launchpad.net/bugs/1899352 Title: Pulseaudio cannot be kept from starting or respawning Status in pulseaudio package in Ubuntu: New Bug description: On my freshly installed system, I need to run pulseaudio in system mode. Alas, by default, pulseaudio is run in user mode, and is set to respawn, so that I cannot kill the user process and start pulseaudio in system mode. I tried: 1. Editing /etc/pulse/client.conf, setting autospawn = no. This did nothing. 2. Removing the file /etc/pulse/client.conf.d/01-respawn-something. I cannot even begin to fathom why such a file would exist. Anyway, this did nothing. 3. I removed the file /usr/bin/start-pulseaudio. Why Of course, this did nothing. 4. I removed the file /etc/xdg/autostart/pulseaudio.desktop. Why on earth do you implement four different ways to annoy your users? On the other hand, this did NOTHING. User mode is still starting, and respawning is enabled. What the heck do I have to do to get rid of user mode pulseaudio? Could you please clean up this clusterfuck? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899354] [NEW] apport-bug crashes (Kununtu)
Public bug reported:
Starting apport-bug from the terminal and then selecting "Sound/audio
related problems" crashes apport-bug:
cassiopeia ~ > apport-bug
ERROR: symptom script /usr/share/apport/symptoms/installer.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/ui.py", line 95, in
thread_collect_info
package = symb['run'](report, ui)
File "/usr/share/apport/symptoms/installer.py", line 9, in run
with os.scandir('/var/log/installer') as entries:
FileNotFoundError: [Errno 2] No such file or directory: '/var/log/installer'
Of course, I never was able to submit ANY bug using apport-bug, because
it does not work for other options either.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1899354
Title:
apport-bug crashes (Kununtu)
Status in apport package in Ubuntu:
New
Bug description:
Starting apport-bug from the terminal and then selecting "Sound/audio
related problems" crashes apport-bug:
cassiopeia ~ > apport-bug
ERROR: symptom script /usr/share/apport/symptoms/installer.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/ui.py", line 95, in
thread_collect_info
package = symb['run'](report, ui)
File "/usr/share/apport/symptoms/installer.py", line 9, in run
with os.scandir('/var/log/installer') as entries:
FileNotFoundError: [Errno 2] No such file or directory: '/var/log/installer'
Of course, I never was able to submit ANY bug using apport-bug,
because it does not work for other options either.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899354/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899354] Re: apport-bug crashes (Kununtu)
As to why there is no /var/log/installer: I installed from a USB stick
into a fully encrypted system, so that /var/log/installer file was on
the sticks' memory file system, but not in the encrypted filesystem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1899354
Title:
apport-bug crashes (Kununtu)
Status in apport package in Ubuntu:
New
Bug description:
Starting apport-bug from the terminal and then selecting "Sound/audio
related problems" crashes apport-bug:
cassiopeia ~ > apport-bug
ERROR: symptom script /usr/share/apport/symptoms/installer.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/ui.py", line 95, in
thread_collect_info
package = symb['run'](report, ui)
File "/usr/share/apport/symptoms/installer.py", line 9, in run
with os.scandir('/var/log/installer') as entries:
FileNotFoundError: [Errno 2] No such file or directory: '/var/log/installer'
Of course, I never was able to submit ANY bug using apport-bug,
because it does not work for other options either.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899354/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899352] [NEW] Pulseaudio cannot be kept from starting or respawning
Public bug reported: On my freshly installed system, I need to run pulseaudio in system mode. Alas, by default, pulseaudio is run in user mode, and is set to respawn, so that I cannot kill the user process and start pulseaudio in system mode. I tried: 1. Editing /etc/pulse/client.conf, setting autospawn = no. This did nothing. 2. Removing the file /etc/pulse/client.conf.d/01-respawn-something. I cannot even begin to fathom why such a file would exist. Anyway, this did nothing. 3. I removed the file /usr/bin/start-pulseaudio. Why Of course, this did nothing. 4. I removed the file /etc/xdg/autostart/pulseaudio.desktop. Why on earth do you implement four different ways to annoy your users? On the other hand, this did NOTHING. User mode is still starting, and respawning is enabled. What the heck do I have to do to get rid of user mode pulseaudio? Could you please clean up this clusterfuck? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Pulseaudio cannot be stopped or kept from respawning + Pulseaudio cannot be kept from starting or respawning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899352 Title: Pulseaudio cannot be kept from starting or respawning Status in pulseaudio package in Ubuntu: New Bug description: On my freshly installed system, I need to run pulseaudio in system mode. Alas, by default, pulseaudio is run in user mode, and is set to respawn, so that I cannot kill the user process and start pulseaudio in system mode. I tried: 1. Editing /etc/pulse/client.conf, setting autospawn = no. This did nothing. 2. Removing the file /etc/pulse/client.conf.d/01-respawn-something. I cannot even begin to fathom why such a file would exist. Anyway, this did nothing. 3. I removed the file /usr/bin/start-pulseaudio. Why Of course, this did nothing. 4. I removed the file /etc/xdg/autostart/pulseaudio.desktop. Why on earth do you implement four different ways to annoy your users? On the other hand, this did NOTHING. User mode is still starting, and respawning is enabled. What the heck do I have to do to get rid of user mode pulseaudio? Could you please clean up this clusterfuck? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890041] Re: Apport does not work without Chrome
Sorry, I misunderstood. arcturus ~ > grep chromium ~/.local/share/applications/* /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser --incognito /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser --temp-profile /home/ralph/.local/share/applications/chromium-browser-2.desktop:Icon=chromium-browser /home/ralph/.local/share/applications/chromium-browser-2.desktop:X-AppInstall-Package=chromium-browser /home/ralph/.local/share/applications/Chromium.desktop:Exec=/snap/chromium/current/bin/chromium.launcher /home/ralph/.local/share/applications/Chromium.desktop:Icon=chromium-browser -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: Incomplete Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890041] Re: Apport does not work without Chrome
arcturus ~ > xdg-mime query default x-scheme-handler/http firefox.desktop Not sure what you mean by "it", but: arcturus ~ > ls .local/share/applications/apport* ls: No match. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: Incomplete Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890041] Re: Apport does not work without Chrome
I'm using the KDE desktop. As for your question: arcturus ~ > xdg-open http://launchpad.net non-network local connections being added to access control list sudo: chromium-browser: command not found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: Incomplete Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890042] Re: KDE: Key shortcuts no longer working
** Package changed: apport (Ubuntu) => plasma-workspace (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890042 Title: KDE: Key shortcuts no longer working Status in plasma-workspace package in Ubuntu: New Bug description: In the KDE menu editor, you can define keyboard shortcuts for each program that, when pressed, will launch that respective program. However, since 20.04, that mechanism no longer works -- pressing any shortcut key (e.g., Meta+E) no longer starts the assigned program (e.g., Emacs GUI). Of course I don't know if the issue is with menu editor, or kwin, or something else in Plasma. Further information: Description:Ubuntu 20.04.1 LTS Release:20.04 plasma-workspace: Installed: 4:5.18.5-0ubuntu0.1 Candidate: 4:5.18.5-0ubuntu0.1 Version table: *** 4:5.18.5-0ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:5.18.4.1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1890042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890042] [NEW] KDE: Key shortcuts no longer working
Public bug reported: In the KDE menu editor, you can define keyboard shortcuts for each program that, when pressed, will launch that respective program. However, since 20.04, that mechanism no longer works -- pressing any shortcut key (e.g., Meta+E) no longer starts the assigned program (e.g., Emacs GUI). Of course I don't know if the issue is with menu editor, or kwin, or something else in Plasma. Further information: Description:Ubuntu 20.04.1 LTS Release:20.04 plasma-workspace: Installed: 4:5.18.5-0ubuntu0.1 Candidate: 4:5.18.5-0ubuntu0.1 Version table: *** 4:5.18.5-0ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:5.18.4.1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890042 Title: KDE: Key shortcuts no longer working Status in apport package in Ubuntu: New Bug description: In the KDE menu editor, you can define keyboard shortcuts for each program that, when pressed, will launch that respective program. However, since 20.04, that mechanism no longer works -- pressing any shortcut key (e.g., Meta+E) no longer starts the assigned program (e.g., Emacs GUI). Of course I don't know if the issue is with menu editor, or kwin, or something else in Plasma. Further information: Description:Ubuntu 20.04.1 LTS Release:20.04 plasma-workspace: Installed: 4:5.18.5-0ubuntu0.1 Candidate: 4:5.18.5-0ubuntu0.1 Version table: *** 4:5.18.5-0ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:5.18.4.1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890041] [NEW] Apport does not work without Chrome
Public bug reported: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: New Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806238] Re: Sandboxed applications donplay sound with Pulseaudio
I resorted to system-wide mode now, no matter how supported that is or not. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1806238 Title: Sandboxed applications donplay sound with Pulseaudio Status in pulseaudio package in Ubuntu: Invalid Bug description: On my Kubuntu desktop machine, I'm running Firefox as a different user for security reasons. Since Firefox has dropped support for ALSA, I no longer have sound in Firefox. The actual bug is that (a) Pulseaudio doesn't accept connection from other users, or (b) Pulseaudio isn't supposed to be run by root. Note that the workaround of creating a socket does not work in my machine; /etc/pulse/default.pa: load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/ff-pulse-socket /etc/pulse/client.conf: default-server = unix:/tmp/ff-pulse-socket Using this workaround, pavucontrol shows a sound stream by Firefox and shows sound for line out, but no audio is heard. Audio for the logged-in user works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1806238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806238] Re: Sandboxed applications donplay sound with Pulseaudio
The title should read "Sandboxed applications don't play sound with Pulseaudio", but if there's a way to edit the title after accidentally hitting Return, it's not obvious. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1806238 Title: Sandboxed applications donplay sound with Pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: On my Kubuntu desktop machine, I'm running Firefox as a different user for security reasons. Since Firefox has dropped support for ALSA, I no longer have sound in Firefox. The actual bug is that (a) Pulseaudio doesn't accept connection from other users, or (b) Pulseaudio isn't supposed to be run by root. Note that the workaround of creating a socket does not work in my machine; /etc/pulse/default.pa: load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/ff-pulse-socket /etc/pulse/client.conf: default-server = unix:/tmp/ff-pulse-socket Using this workaround, pavucontrol shows a sound stream by Firefox and shows sound for line out, but no audio is heard. Audio for the logged-in user works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1806238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806238] [NEW] Sandboxed applications donplay sound with Pulseaudio
Public bug reported: On my Kubuntu desktop machine, I'm running Firefox as a different user for security reasons. Since Firefox has dropped support for ALSA, I no longer have sound in Firefox. The actual bug is that (a) Pulseaudio doesn't accept connection from other users, or (b) Pulseaudio isn't supposed to be run by root. Note that the workaround of creating a socket does not work in my machine; /etc/pulse/default.pa: load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/ff-pulse-socket /etc/pulse/client.conf: default-server = unix:/tmp/ff-pulse-socket Using this workaround, pavucontrol shows a sound stream by Firefox and shows sound for line out, but no audio is heard. Audio for the logged-in user works fine. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1806238 Title: Sandboxed applications donplay sound with Pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: On my Kubuntu desktop machine, I'm running Firefox as a different user for security reasons. Since Firefox has dropped support for ALSA, I no longer have sound in Firefox. The actual bug is that (a) Pulseaudio doesn't accept connection from other users, or (b) Pulseaudio isn't supposed to be run by root. Note that the workaround of creating a socket does not work in my machine; /etc/pulse/default.pa: load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/ff-pulse-socket /etc/pulse/client.conf: default-server = unix:/tmp/ff-pulse-socket Using this workaround, pavucontrol shows a sound stream by Firefox and shows sound for line out, but no audio is heard. Audio for the logged-in user works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1806238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631746] [NEW] grub accepts only one key press in total
Public bug reported: When grub start, I can press exactly one key, then all other key presses are ignored. I cannot tell if grub crashes or not. This one keypress could be RETURN, then normal boot continues. It could be ARROW DOWN, then the second line in the grub menu is selected. But from then on, all further key presses are ignored, be they RETURN, ARROW UP/DOWN, even CTRL+ALT+DEL. This breaks the selection of MEMTEST and other grub entries but the first. Note that I'm using a regular USB keyboard. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 9 15:57:32 2016 InstallationDate: Installed on 2016-08-24 (45 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631746 Title: grub accepts only one key press in total Status in xorg package in Ubuntu: New Bug description: When grub start, I can press exactly one key, then all other key presses are ignored. I cannot tell if grub crashes or not. This one keypress could be RETURN, then normal boot continues. It could be ARROW DOWN, then the second line in the grub menu is selected. But from then on, all further key presses are ignored, be they RETURN, ARROW UP/DOWN, even CTRL+ALT+DEL. This breaks the selection of MEMTEST and other grub entries but the first. Note that I'm using a regular USB keyboard. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 9 15:57:32 2016 InstallationDate: Installed on 2016-08-24 (45 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631746] Re: grub accepts only one key press in total
ignore the xorg, that's another bug in bug-ubuntu I'm about to report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631746 Title: grub accepts only one key press in total Status in xorg package in Ubuntu: New Bug description: When grub start, I can press exactly one key, then all other key presses are ignored. I cannot tell if grub crashes or not. This one keypress could be RETURN, then normal boot continues. It could be ARROW DOWN, then the second line in the grub menu is selected. But from then on, all further key presses are ignored, be they RETURN, ARROW UP/DOWN, even CTRL+ALT+DEL. This breaks the selection of MEMTEST and other grub entries but the first. Note that I'm using a regular USB keyboard. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 9 15:57:32 2016 InstallationDate: Installed on 2016-08-24 (45 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631748] [NEW] ubuntu-bug selects wrong category
Public bug reported: The ubuntu-bug tool always assumes an xorg bug when I select "other". For example, selecting "other problem" on the first screen and then "I don't know" will create an xorg bug report, even though I want to report another problem (e.g. grub). The selection in the first screen apparently is not honored, which makes reporting bugs (including bugs about ubuntu-bug) quite difficult. (Also, the launchpad package search dialog reports an "OOPS-xxx" error.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 9 16:03:15 2016 InstallationDate: Installed on 2016-08-24 (45 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631748 Title: ubuntu-bug selects wrong category Status in xorg package in Ubuntu: New Bug description: The ubuntu-bug tool always assumes an xorg bug when I select "other". For example, selecting "other problem" on the first screen and then "I don't know" will create an xorg bug report, even though I want to report another problem (e.g. grub). The selection in the first screen apparently is not honored, which makes reporting bugs (including bugs about ubuntu-bug) quite difficult. (Also, the launchpad package search dialog reports an "OOPS-xxx" error.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 9 16:03:15 2016 InstallationDate: Installed on 2016-08-24 (45 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
