[Touch-packages] [Bug 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
I just tested it on a laptop with intel graphics, and sound and playback is perfectly normal on 60Hz when playing through the HDMI (playing on the television). Same cable, same television - only connected to my laptop instead. This makes me wonder whether this could be an issue in the kernel driver, amdgpu? Hardware: CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz GPU: Intel(R) HD Graphics 4400 (HSW GT2) OS: Ubuntu 21.10 -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
I don't know if the speed is exactly doubled, by but changing the output definitely changes the playback speed of any media. I tried making a video to show it: https://youtu.be/hlqw_ijdxOE -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
However, audio going through USB on the X1 ThinkVision (called "Analog Output - X1") is now playing correctly in Wayland with both monitors at 60Hz. When selecting the television output "HDMI / DisplayPort - Vega 20 HDMI Audio [Radeon VII]" on Wayland with 60Hz on both monitors, the playback doubles and sound is high pitched. (This one is connected through HDMI) When selecting the X1 monitor output "HDMI / DisplayPort 2 - Vega 20 HDMI Audio [Radeon VII]" on Wayland with 60Hz on both monitors, the playback doubles and sound is also high pitched. (This one is connected through DisplayPort) So it appears that on Wayland with both monitors on 60Hz, the audio going through either HDMI or DisplayPort doubles in speed and becomes high pitched. -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
This does not fix the issue. Playback is still double and high pitched in Wayland with both monitors at 60Hz. In Xorg I can still only select 30Hz as the maximum on the television. -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
Also because Wayland allows the television to be at 60Hz, whenever I login (after boot) and have it in mirror mode, the sound is therefore too fast by default. I cannot change it, since the HDMI port is the first port on the GPU and the DisplayPort port is the second. This means it by default assumes the television to be the default display. Of course this would not be an issue if the sound just worked. But right now it would also be nice to be able to change the primary display when mirroring screens. -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in xorg package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1957816/+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 1957816] Re: Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed
** Summary changed: - Wayland dual monitor 60Hz: High pitch audio + Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed ** Summary changed: - Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed + Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in xorg package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1957816/+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 1957819] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
** Summary changed: - Wayland dual monitor 60Hz: High pitch audio and fast playback + Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed -- 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/1957819 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in alsa-driver package in Ubuntu: New Bug description: I described the issue here first: https://bugs.launchpad.net/ubuntu/+bug/1957816 I am not sure it belongs here, but after the initial report i made an audio issue report with `ubuntu-bug -s audio` copy/paste: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 17:24:02 2022 InstallationDate: Installed on 2020-05-03 (620 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Vega 20 HDMI Audio [Radeon VII] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8101 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8101:bd07/15/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1957819/+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 1957819] [NEW] Wayland dual monitor 60Hz: High pitch audio and fast playback
Public bug reported: I described the issue here first: https://bugs.launchpad.net/ubuntu/+bug/1957816 I am not sure it belongs here, but after the initial report i made an audio issue report with `ubuntu-bug -s audio` copy/paste: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 17:24:02 2022 InstallationDate: Installed on 2020-05-03 (620 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Vega 20 HDMI Audio [Radeon VII] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8101 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8101:bd07/15/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Description changed: I described the issue here first: https://bugs.launchpad.net/ubuntu/+bug/1957816 + + I am not sure it belongs here, but after the initial report i made an + audio issue report with `ubuntu-bug -s audio` copy/paste: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the televisio
[Touch-packages] [Bug 1841387] Re: GDM hangs on boot with 5.3rc5 when using wayland
This bug can be closed, one could argue that the kernel could handle this a bit prettier as the -1 options is setting the firmware loading to auto so a fallback to not loading the firmware would be ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1841387 Title: GDM hangs on boot with 5.3rc5 when using wayland Status in wayland package in Ubuntu: New Bug description: Been testing newer kernels and everything works(5.2.9 works) until 5.3rc series where it seems there is an issue with Wayland and/or the setup on Ubuntu is using, it works on Arch Linux. When booting with 5.3rc5 GDM hangs on launch showing a blank screen, booting to safe mode trying to start weston results in: Date: 2019-08-24 CEST [23:29:54.788] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: unknown (not built from git or tarball) [23:29:54.788] Command line: /usr/bin/weston [23:29:54.788] OS: Linux, 5.3.0-050300rc5-generic, #201908182231 SMP Sun Aug 18 22:33:18 UTC 2019, x86_64 [23:29:54.788] Using config file '/home/tlb/.config/weston.ini' [23:29:54.788] Output repaint window is 7 ms maximum. [23:29:54.788] Loading module '/usr/lib/x86_64-linux-gnu/libweston-5/drm-backend.so' [23:29:54.790] initializing drm backend [23:29:54.792] logind: session control granted [23:29:54.793] no drm device found [23:29:54.793] fatal: failed to create compositor backend I know this is not supported but there are some nice thermal fixes in 5.3 for the Dell XPS 9380 and 9370 that would be nice to have. How do i debug this? Regards Troels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1841387/+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 1841387] Re: GDM hangs on boot with 5.3rc5 when using wayland
5 23:32:02 xps9380 kernel: RDX: RSI: 55ea24233bd0 RDI: 0015 Aug 25 23:32:02 xps9380 kernel: RBP: 55ea24233bd0 R08: R09: 55ea242254f0 Aug 25 23:32:02 xps9380 kernel: R10: 0015 R11: 0246 R12: Aug 25 23:32:02 xps9380 kernel: R13: 55ea24232130 R14: 0002 R15: 55ea242254f0 Aug 25 23:32:02 xps9380 kernel: ---[ end trace c92e890610d05150 ]--- Aug 25 23:32:02 xps9380 kernel: [drm:drm_mode_config_cleanup.cold [drm]] *ERROR* connector eDP-1 leaked! Aug 25 23:32:02 xps9380 kernel: i915 :00:02.0: Device initialization failed (-8) Aug 25 23:32:02 xps9380 kernel: i915: probe of :00:02.0 failed with error -8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1841387 Title: GDM hangs on boot with 5.3rc5 when using wayland Status in wayland package in Ubuntu: New Bug description: Been testing newer kernels and everything works(5.2.9 works) until 5.3rc series where it seems there is an issue with Wayland and/or the setup on Ubuntu is using, it works on Arch Linux. When booting with 5.3rc5 GDM hangs on launch showing a blank screen, booting to safe mode trying to start weston results in: Date: 2019-08-24 CEST [23:29:54.788] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: unknown (not built from git or tarball) [23:29:54.788] Command line: /usr/bin/weston [23:29:54.788] OS: Linux, 5.3.0-050300rc5-generic, #201908182231 SMP Sun Aug 18 22:33:18 UTC 2019, x86_64 [23:29:54.788] Using config file '/home/tlb/.config/weston.ini' [23:29:54.788] Output repaint window is 7 ms maximum. [23:29:54.788] Loading module '/usr/lib/x86_64-linux-gnu/libweston-5/drm-backend.so' [23:29:54.790] initializing drm backend [23:29:54.792] logind: session control granted [23:29:54.793] no drm device found [23:29:54.793] fatal: failed to create compositor backend I know this is not supported but there are some nice thermal fixes in 5.3 for the Dell XPS 9380 and 9370 that would be nice to have. How do i debug this? Regards Troels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1841387/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I also reverted to Linux kernel 4.18.0-13-generic (The one that ships with Ubuntu 18.10) after upgrading to 19.04. System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU @ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2) When running 'sudo apt upgrade' it complains about a missing dkms.conf file: Setting up linux-headers-5.0.0-13-generic (5.0.0-13.14) ... /etc/kernel/header_postinst.d/dkms: Error! Could not locate dkms.conf file. File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist. run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 dpkg: error processing package linux-headers-5.0.0-13-generic (--configure): installed linux-headers-5.0.0-13-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-5.0.0-13-generic; however: Package linux-headers-5.0.0-13-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured Setting up linux-image-5.0.0-13-generic (5.0.0-13.14) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 5.0.0.13.14); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for linux-image-5.0.0-13-generic (5.0.0-13.14) ... /etc/kernel/postinst.d/dkms: Error! Could not locate dkms.conf file. File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist. run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 dpkg: error processing package linux-image-5.0.0-13-generic (--configure): installed linux-image-5.0.0-13-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-5.0.0-13-generic linux-headers-generic linux-generic linux-image-5.0.0-13-generic E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet spla
[Touch-packages] [Bug 1754270] Re: systemd-user PAM configuration should initialize the keyring with pam_keyinit
I tested the setup on Ubuntu 18.10 and it seems to work correctly with a couple of fixes, I have created a small guide here: http://tlbdk.github.io/ubuntu/2018/10/22/fscrypt.html -- 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/1754270 Title: systemd-user PAM configuration should initialize the keyring with pam_keyinit Status in systemd package in Ubuntu: Confirmed Bug description: /etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's possible this should instead be added to common-session-noninteractive but I am not entirely sure about that - someone with more understanding of the PAM modules would probably need to weigh in on that. In any case systemd-user itself should at least have it - as it has it's own special PAMname for processes it launches. This means that the keyring does not link to the user keyring as it should, and will cause issues with programs needing a key from the keyring. In particular the use case that breaks for me is using 'fscrypt' and 'libpam-fscrypt' however anything making use of kernel keyrings would be affected. Something non-obvious about this, is that many desktop session processes are started under 'systemd-user' instead of the 'session' - this includes gnome-terminal-server which means any gnome-terminal shell runs under this context. If you start xterm instead of gnome- terminal, you get a different keyring and this can cause confusion when debugging the issue as some processes are in one state and the others are in another including your primary debug tool gnome- terminal. You can verify this by running 'systemctl status $(pidof gnome-terminal)' and 'systemctl status $(pidof xterm)' and note the different hierachy. The change to add pam_keyinit.so was made upstream in December 2016: https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f Ubuntu should make the same change so that services needing a keyring will work correctly in the desktop session, and the same keyring is used for processes launched under both methods. In my test I add the usual pam_keyinit.so line after "pam_limits.so" and before "common- session-noninteractive". I am not sure if this is the most ideal location (but it appears to work). You can test the behavior by running "keyctl show @s" in both contexts Working contexts: - xterm - SSH login Broken contexts: - gnome-terminal - systemd-run --user keyctl show @s (then check output with journalctl --user --follow) When the configuration is broken you will see this output: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ user: invocation_id When the configuration is working, you will see a link to the user session instead: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ keyring: _uid.1000 As background, what is broken on my test setup with libpam-fscrypt? gnome-terminal for example is unable to write any file in my encrypted /home which means that it cannot save preferences, so if you go into preferences and try to tick a checkbox it will immediately revert and an error is logged to the journal. You can use the guide at https://github.com/google/fscrypt to setup such a system if you wish to fully test my case. But you can simply verify the behavior as above. Verified on bionic (its the only version with fscrypt) however this issue extends back to at least xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754270/+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 278095] RE
Check [Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func() -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 278095] RE
Check [Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func() -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 278095] RE
Check [Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func() -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 1676665] [NEW] Crashed after returning to Unity 7 from Unity 8
Public bug reported: To be honest, I know very little about what happened. I only went to try Unity 8 and then went back to Unity 7. When logged in with Unity 7, many of the programs from Unity 8 where appearently still running and many of the crashed. ProblemType: RecoverableProblem DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 BadURL: scope://com.canonical.scopes.clickstore CurrentDesktop: Unity:Unity8 Date: Tue Mar 28 00:59:59 2017 DuplicateSignature: /usr/bin/unity8:url-dispatcher-bad-url ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2017-03-27 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: unity8 --mode=full-shell ProcEnviron: LANGUAGE=da PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-recoverableproblem zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1676665 Title: Crashed after returning to Unity 7 from Unity 8 Status in unity8 package in Ubuntu: New Bug description: To be honest, I know very little about what happened. I only went to try Unity 8 and then went back to Unity 7. When logged in with Unity 7, many of the programs from Unity 8 where appearently still running and many of the crashed. ProblemType: RecoverableProblem DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 BadURL: scope://com.canonical.scopes.clickstore CurrentDesktop: Unity:Unity8 Date: Tue Mar 28 00:59:59 2017 DuplicateSignature: /usr/bin/unity8:url-dispatcher-bad-url ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2017-03-27 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: unity8 --mode=full-shell ProcEnviron: LANGUAGE=da PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676665/+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 278095]
"[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()" Launchpad Bug Tracker doc -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 278095]
"[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()" Launchpad Bug Tracker doc -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 278095]
"[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()" Launchpad Bug Tracker doc -- 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/278095 Title: MASTER crash in getenv() ... spi_atk_bridge_exit_func() Status in at-spi: Expired Status in apport package in Ubuntu: Invalid Status in at-spi package in Ubuntu: Fix Released Status in firefox-3.0 package in Ubuntu: Invalid Status in apport source package in Intrepid: Invalid Status in at-spi source package in Intrepid: Fix Released Status in firefox-3.0 source package in Intrepid: Invalid Status in apport source package in Jaunty: Invalid Status in at-spi source package in Jaunty: Fix Released Status in firefox-3.0 source package in Jaunty: Invalid Bug description: This crash seems to occur most frequently when opening a new URL in an existing Firefox process. The URL is successfully opened, but the client process then crashes while exiting. The result is that the operation appears to work, but there has been a crash in the background (which is then displayed by update-notifier and apport). Steps to reproduce: 1. check "Enable assisitive technologies" in Preferences -> Assistive Technologies 2. restart X session 3. start firefox 4. start from terminal: firefox http://www.ubuntu.com Result: see crash. Verify: with updated package it shouldnt crash. === I am using Ubuntu 8.10 beta ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/lib/firefox-3.0.3/firefox Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: /usr/lib/firefox-3.0.3/firefox https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox-3.0 StacktraceTop: getenv () from /lib/tls/i686/cmov/libc.so.6 g_getenv () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so exit () from /lib/tls/i686/cmov/libc.so.6 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Title: firefox crashed with SIGSEGV in getenv() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/278095/+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 1364584] [NEW] `getaddrinfo` leaks memory
Public bug reported: I believe 2.11.1-0ubuntu7.14 (Ubuntu 10.04) introduces a regression in `getaddrinfo`. I'm using the test case from [Debian Bug #304022](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304022) (attached as "main.c"). Valgrind detects a leak (output below) that isn't detected if I'm downgrading to 2.11.1-0ubuntu7.13. Upgrading to 2.11.1-0ubuntu7.16 doesn't resolve this. However, I'm unable to reproduce on 2.19-0ubuntu6.3 (Ubuntu 14.04). (The host in the test case yields a NXDOMAIN, but this isn't significant; it seems 1 kB will be leaked per block in any case.) ==7== Memcheck, a memory error detector ==7== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==7== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==7== Command: ./a.out ==7== ==7== ==7== HEAP SUMMARY: ==7== in use at exit: 1,024 bytes in 1 blocks ==7== total heap usage: 58 allocs, 57 frees, 9,893 bytes allocated ==7== ==7== 1,024 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==7==at 0x4C274A8: malloc (vg_replace_malloc.c:236) ==7==by 0x4EE7EC6: gaih_inet (getaddrinfo.c:858) ==7==by 0x4EEA8F1: getaddrinfo (getaddrinfo.c:2425) ==7==by 0x400606: main (in /tmp/a.out) ==7== ==7== LEAK SUMMARY: ==7==definitely lost: 1,024 bytes in 1 blocks ==7==indirectly lost: 0 bytes in 0 blocks ==7== possibly lost: 0 bytes in 0 blocks ==7==still reachable: 0 bytes in 0 blocks ==7== suppressed: 0 bytes in 0 blocks ==7== ==7== For counts of detected and suppressed errors, rerun with: -v ==7== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Test case to reproduce" https://bugs.launchpad.net/bugs/1364584/+attachment/4193570/+files/main.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1364584 Title: `getaddrinfo` leaks memory Status in “eglibc” package in Ubuntu: New Bug description: I believe 2.11.1-0ubuntu7.14 (Ubuntu 10.04) introduces a regression in `getaddrinfo`. I'm using the test case from [Debian Bug #304022](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304022) (attached as "main.c"). Valgrind detects a leak (output below) that isn't detected if I'm downgrading to 2.11.1-0ubuntu7.13. Upgrading to 2.11.1-0ubuntu7.16 doesn't resolve this. However, I'm unable to reproduce on 2.19-0ubuntu6.3 (Ubuntu 14.04). (The host in the test case yields a NXDOMAIN, but this isn't significant; it seems 1 kB will be leaked per block in any case.) ==7== Memcheck, a memory error detector ==7== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==7== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==7== Command: ./a.out ==7== ==7== ==7== HEAP SUMMARY: ==7== in use at exit: 1,024 bytes in 1 blocks ==7== total heap usage: 58 allocs, 57 frees, 9,893 bytes allocated ==7== ==7== 1,024 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==7==at 0x4C274A8: malloc (vg_replace_malloc.c:236) ==7==by 0x4EE7EC6: gaih_inet (getaddrinfo.c:858) ==7==by 0x4EEA8F1: getaddrinfo (getaddrinfo.c:2425) ==7==by 0x400606: main (in /tmp/a.out) ==7== ==7== LEAK SUMMARY: ==7==definitely lost: 1,024 bytes in 1 blocks ==7==indirectly lost: 0 bytes in 0 blocks ==7== possibly lost: 0 bytes in 0 blocks ==7==still reachable: 0 bytes in 0 blocks ==7== suppressed: 0 bytes in 0 blocks ==7== ==7== For counts of detected and suppressed errors, rerun with: -v ==7== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1364584/+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
