[Touch-packages] [Bug 1978108] [NEW] totem doesn't detect newly installed gstreamer plugin
Public bug reported: So you just installed Ubuntu 22.04 and you try to play an mp4 video. Totem will complain about missing an H.264 decoder, as you can see in the command line output: Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main Profile)|decoder-video/x-h264, level=(string)3, profile=(string)main (decodificador H.264 (Main Profile)) You will now install gstreamer1.0-libav and try again, but it will still fail with the same complaint. The solution, as others have found (https://askubuntu.com/a/407595/818746), is: $ rm -rf ~/.cache/gstreamer-1.0/ I suppose that is a bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 08:06:35 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978108 Title: totem doesn't detect newly installed gstreamer plugin Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: So you just installed Ubuntu 22.04 and you try to play an mp4 video. Totem will complain about missing an H.264 decoder, as you can see in the command line output: Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main Profile)|decoder-video/x-h264, level=(string)3, profile=(string)main (decodificador H.264 (Main Profile)) You will now install gstreamer1.0-libav and try again, but it will still fail with the same complaint. The solution, as others have found (https://askubuntu.com/a/407595/818746), is: $ rm -rf ~/.cache/gstreamer-1.0/ I suppose that is a bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 08:06:35 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978108/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
I forgot to tell you that I never see any dialog when I plug the earphone. It's a feature of some desktop environments, right? I have never seen it in Xfce. The capture source changes to "headphone" every time I plug the earphone, and when that happens, there is no sound output. Changing it to any other source makes the sound work. I don't remember how it worked in previous versions of Ubuntu. It just worked. I never had to worry about switching the capture source in order to have sound. If you think that's important to know, I can try a live ISO of 18.04 and report back what I find. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Oh, I can finally hear sound through the earphones by changing the capture source. Too bad the change doesn't persist after I remove and reinsert the connector. Every time that happens, I must change it to Headset Mic, otherwise there will be no sound output. It also works when I do it through the Pulseaudio GUI mixer that comes with Xubuntu. Now I just wish the default selection could be one that works out of the box, as it was in previous Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
I have attached a screenshot of that screen, because I couldn't find any Capture Source or Input Source there. Maybe it has a different name or is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
** Attachment added: "screenshot alsamixer capture" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+attachment/5361512/+files/Captura%20de%20tela_2020-04-27_06-51-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Running amixer sset 'Capture Source' 'Internal Mic' returns error: amixer: Unable to find simple control 'Capture Source',0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875249] [NEW] [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Public bug reported: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - No sound output from earphones + [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDe
[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive
I think I can't reproduce this anymore on Xubuntu 20.04. I left the laptop idle and after 30 minutes it was suspended as expected, without making any fixes (clean install). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is unable to suspend the system when the user is inactive. A PK user- agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1851661] [NEW] AppArmor denied operation open to snap pick-colour-picker
Public bug reported: I've written an issue here: https://github.com/stuartlangridge/ColourPicker/issues/63 Pick (a color picker distributed as a snap) will not launch. The creator of the application believes this to be a problem with my system, not with their app. Apparently, AppArmor is preventing it from starting. I'm not familiar with this MAC implementation, but the logs suggest that this is the problem. See the attachment. ``` nov 07 11:18:29 alq22 audit[27542]: AVC apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 nov 07 11:18:29 alq22 kernel: audit: type=1400 audit(1573136309.796:304): apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ``` This is a fresh installation of Ubuntu 18.04.3. I take great care not to mess with system components such as snapd. Other snaps are working properly. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Journalctl output - see last lines" https://bugs.launchpad.net/bugs/1851661/+attachment/5303495/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1851661 Title: AppArmor denied operation open to snap pick-colour-picker Status in apparmor package in Ubuntu: New Bug description: I've written an issue here: https://github.com/stuartlangridge/ColourPicker/issues/63 Pick (a color picker distributed as a snap) will not launch. The creator of the application believes this to be a problem with my system, not with their app. Apparently, AppArmor is preventing it from starting. I'm not familiar with this MAC implementation, but the logs suggest that this is the problem. See the attachment. ``` nov 07 11:18:29 alq22 audit[27542]: AVC apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 nov 07 11:18:29 alq22 kernel: audit: type=1400 audit(1573136309.796:304): apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ``` This is a fresh installation of Ubuntu 18.04.3. I take great care not to mess with system components such as snapd. Other snaps are working properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1851661/+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 1849324] [NEW] Xorg logs spammed with failed page flip messages
Public bug reported: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The Xorg log file, currently 15 MB large" https://bugs.launchpad.net/bugs/1849324/+attachment/5299212/+files/Xorg.0.log ** Description changed: - This bug has already been discussed here: + Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Description changed: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` - A fix has already been merged here: + A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. -- 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/1849324 Title: Xorg logs spammed with failed page flip messages Status in xorg package in Ubuntu: New Bug description: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1849324/+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 1848616] [NEW] LightDM crashes and logs me out when resuming from suspend
Public bug reported: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. How reproducible? 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Journalctl output from right after the problem" https://bugs.launchpad.net/bugs/1848616/+attachment/5298012/+files/journalctl.txt ** Description changed: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. + + How reproducible? + 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1848616 Title: LightDM crashes and logs me out when resuming from suspend Status in lightdm package in Ubuntu: New Bug description: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. How reproducible? 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1848616/+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 1757375] Re: Desktop unable to Suspend when Inactive
** Description changed: - On 16.04 (XFCE session and others) and possibly later the power-manager - is unable to suspend the system when the user is inactive. A PK user- - agent dialog is presented for the user to authenticate first - and as - this action occurs specifically when the user is idle and away the PC - can end up having an unplanned loss of power when the battery is - exhausted. + On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is + unable to suspend the system when the user is inactive. A PK user-agent + dialog is presented for the user to authenticate first - and as this + action occurs specifically when the user is idle and away the PC can end + up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is unable to suspend the system when the user is inactive. A PK user- agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1757375] Re: Desktop unable to Suspend when Inactive
I can also reproduce this on both of my computers running Xubuntu 19.04, a desktop and a laptop. Just to be extra clear on what the issue is: If the computer is left idle for 10 minutes, the screen locks. When 15 minutes have passed, it should suspend, but it never does. I unlock the screen to investigate why, and find that there is a prompt window asking my password in order to allow the system to suspend. What usually happens as a consequence: I fall asleep with the laptop still running, and on the next day the thing is powered off with only 1% of battery power. It stayed ON all night. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1757375] Re: Desktop unable to Suspend when Inactive
Thanks for the response. Sorry for the delay, I didn't get a notification about this. If by admin you mean one that has sudo privileges or a member of group `adm`, then yes. It's the default user created by the installer. I could reproduce this on Arch Linux and other distros IIRC. The workaround works on them too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1839900] [NEW] Power button action not working
Public bug reported: I've configured it so that the system would suspend after pressing the power button. This does not happen. How is it reproducible? It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new kernel, new bug. On Ubuntu 19.04, this has been reproducible since its release. This is also reproducible on other distributions with the GNOME desktop. This is exclusive to the GNOME desktop. No other desktop I've tried has issues with the power button action. Ubuntu 18.04.3 Kernel 5.0.0-23-generic GNOME 3.28.2 See attached logs. Near the end of it I attempted to make the system suspend by repeatedly pressing the power button, as configured in GNOME Settings > Power > When the power button is pressed. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl output" https://bugs.launchpad.net/bugs/1839900/+attachment/5282269/+files/journalctl.txt ** Package changed: systemd (Ubuntu) => gnome-settings-daemon (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/1839900 Title: Power button action not working Status in gnome-settings-daemon package in Ubuntu: New Bug description: I've configured it so that the system would suspend after pressing the power button. This does not happen. How is it reproducible? It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new kernel, new bug. On Ubuntu 19.04, this has been reproducible since its release. This is also reproducible on other distributions with the GNOME desktop. This is exclusive to the GNOME desktop. No other desktop I've tried has issues with the power button action. Ubuntu 18.04.3 Kernel 5.0.0-23-generic GNOME 3.28.2 See attached logs. Near the end of it I attempted to make the system suspend by repeatedly pressing the power button, as configured in GNOME Settings > Power > When the power button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1839900/+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 1757375] Re: Desktop unable to Suspend when Inactive
The solution is right here, so simple to apply. Why is this ignored? No one else suspends their machines? Merge the necessary polkit rule, please. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1825785] [NEW] lightdm: screen does not wake up on mouse/keyboard events
Public bug reported: Description: When session is locked either using dm-tool or light- locker, lightdm greeter is functional (you can type your password and press Enter to unlock the session) but screen is not turned on, and remains turned off even when you move the mouse or press any key. Although, it doesn't occur when you close your session instead locking it. Additional info: * xorg: 1:7.7+19ubuntu12 * lightdm 1.28.0-0ubuntu1 * xfce4-session: 4.12.1-6ubuntu1 >From lsb_release: Description:Ubuntu 19.04 Release:19.04 * Reproducible on other distributions as well. See here: https://bugs.archlinux.org/task/59750 * Reproducible on both Intel UHD Graphics and AMDGPU Graphics. Steps to reproduce: * Lock the running session using lightdm * Screen is turned off, but it won't turn back on when you move the mouse or use the keyboard * You can type the password and press Enter to unlock the session. It the password is correct, the screen will finally turn on and you will be at your desktop. Note: switching out and then switching back to tty7 restores visibility of the lock screen. On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the screen behave as expected. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Apr 22 02:06:42 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1028:0725] InstallationDate: Installed on 2019-04-22 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 11-3162 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu ** Description changed: Description: When session is locked either using dm-tool or light- locker, lightdm greeter is functional (you can type your password and press Enter to unlock the session) but screen is not turned on, and remains turned off even when you move the mouse or press any key. Although, it doesn't occur when you close your session instead locking it. Additional info: * xorg: 1:7.7+19ubuntu12 * lightdm 1.28.0-0ubuntu1 * xfce4-session: 4.12.1-6ubuntu1 From lsb_release: Description: Ubuntu 19.04 Release: 19.04 - * Reproducible on other distributions as well. + * Reproducible on other distributions as well. See here: https://bugs.archlinux.org/task/59750 * Reproducible on both Intel UHD Graphics and AMDGPU Graphics. Steps to reproduce: * Lock the running session using lightdm * Screen is turned off, but it won't turn back on when you move the mouse or use the keyboard * You can type the password and press Enter to unlock the session. It the password is correct, the screen will finally turn on and you will be at your desktop. Note: switching out and then switching back to tty7 restores visibility of the lock screen
[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen
*** This bug is a duplicate of bug 1795135 *** https://bugs.launchpad.net/bugs/1795135 ** This bug has been marked a duplicate of bug 1795135 XFCE window buttons are not clickable at the top of the screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1690671 Title: Pointer clicks and hovering fail to have effect at the very left and top borders of screen Status in gtk+3.0 package in Ubuntu: New Bug description: THE ISSUE: The pointer (happens with mouse, but it's worse with touchpad) fails to click or highlight any object at the very last pixel of the left and top borders of the screen. If there is a menu at the top, for instance, the highlighting that should appear on top of it starts to flicker on and off. If the icon highlights, I can click. If it doesn't, clicking such menu icon doesn't have any effect. It happens at the last pixel of the screen. Moving the pointer just one pixel away from the border restores the desired effect. This affects any desktop environment made with gtk+3, such as MATE, Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity are not affected. Any DE still using gtk2 works fine. I tested 3 different computers with Intel Graphics and they were all displaying the same glitch. It can always be reproduced. I can record a video of the issue if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+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 1757375] Re: Desktop unable to Suspend when Inactive
No change in Disco. Still missing the entry at "com.ubuntu.desktop.pkla". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1757375] Re: Desktop unable to Suspend when Inactive
Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can suspend the machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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