[Touch-packages] [Bug 1693992] Re: gdm-session-worker crashed with SIGABRT - "assertion failed: (manager->priv->accounts_proxy != NULL)" in load_users()
** Tags removed: artful yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1693992 Title: gdm-session-worker crashed with SIGABRT - "assertion failed: (manager->priv->accounts_proxy != NULL)" in load_users() Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.24.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0848264c9da4adaeb5da47a7aa34ce5bdd84909 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1693992/+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 1536158] Re: Upgrade to 1.1.1 that was released in March 2016
** Tags removed: yakkety ** Tags added: bionic eoan -- 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/1536158 Title: Upgrade to 1.1.1 that was released in March 2016 Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver-2.6.28-12 package in Ubuntu: Confirmed Bug description: Please, upgrade to 1.1.1 that was released in March 2016, see http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1536158/+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 1635668] Re: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1635668 Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted Status in alsa-driver package in Ubuntu: Won't Fix Bug description: This defect is not apparent on two other Ubuntu 16.04 machines. The upgrade to 16.10 did not change the symptoms. lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 11:53:54 2016 InstallationDate: Installed on 2016-09-22 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0773VG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+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 1641690] Re: [X7, Realtek ALC282, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1641690 Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: no sound from built-in speakers, headphones fine ubuntu 16.10, frehs install laptop is this http://www.aorus.com/Product/Spec/X7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tweichart 2752 F pulseaudio /dev/snd/controlC2: tweichart 2752 F pulseaudio /dev/snd/pcmC0D0p: tweichart 2752 F...m pulseaudio /dev/snd/controlC0: tweichart 2752 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 14 18:51:43 2016 InstallationDate: Installed on 2016-11-11 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tweichart 2752 F pulseaudio /dev/snd/controlC2: tweichart 2752 F pulseaudio /dev/snd/controlC0: tweichart 2752 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X7.309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X7 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX7.309:bd02/10/2014:svnGIGABYTE:pnX7:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX7:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: X7 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1641690/+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 1635797] Re: Analog audio out not showing in GUI sound settings.
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1635797 Title: Analog audio out not showing in GUI sound settings. Status in alsa-driver package in Ubuntu: Won't Fix Bug description: "aplay -Dplughw:0,0 -fcd sound.wav" works fine kes@vesta:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 <...other cards which do appear in the System sound GUI...> ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 16:13:28 2016 InstallationDate: Installed on 2016-10-16 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1150, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1810 dmi.board.asset.tag: Default string dmi.board.name: H170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1810:bd07/12/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name 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/1635797/+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 1639753] Re: USB-Audio - HyperX 7.1 Audio, playback Not detected at startup
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1639753 Title: USB-Audio - HyperX 7.1 Audio, playback Not detected at startup Status in alsa-driver package in Ubuntu: Won't Fix Bug description: USB-Audio - HyperX 7.1 USB soundcard Output device is not detected at startup, need to manually unplug and re-plug the USB cable for the system to recognize it. After re- plugging, everything works normally. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: marco 2534 F...m pulseaudio /dev/snd/controlC2: marco 2534 F pulseaudio /dev/snd/controlC1: marco 2534 F pulseaudio /dev/snd/controlC0: marco 2534 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 7 11:34:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-20 (352 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: HyperX 7.1 Audio - HyperX 7.1 Audio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marco 2534 F pulseaudio /dev/snd/controlC1: marco 2534 F pulseaudio /dev/snd/controlC0: marco 2534 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - HyperX 7.1 Audio, playback] No sound at all UpgradeStatus: Upgraded to yakkety on 2016-10-28 (9 days ago) dmi.bios.date: 04/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd04/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1639753/+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 1637837] Re: [Em28xx-Audio - Em28xx Audio, recording] WinTV HVR-900 no sound at all or distorted sound
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1637837 Title: [Em28xx-Audio - Em28xx Audio, recording] WinTV HVR-900 no sound at all or distorted sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The device is WinTV HVR-900 (actually Elgato EyeTV Hybrid). It has an additional dongle with Composite, S-Video and stereo audio inputs. lsusb: Bus 002 Device 006: ID 2040:6502 Hauppauge WinTV HVR-900 I use it together with TVTime, pavucontrol and module-loopback and it generally works well (barring bug #1637817 which I reported earlier today), provided sound is plugged into the computer's line-in input. I'd really like to make it work with the tuner's input, however. When connected, it appears in pavucontrol and can be configured as Analog Stereo Input, and in Input Devices I can select Line In or Video. Selecting either makes no difference: most times there's no sound at all, sometimes sound appears, but it's distorted (a bit like an echo together with overdrive). I'll try to make it work (plugging/unplugging the tuner, restarting pulseaudio usually makes it work after a few times) and post a sample. Interestingly, the volume slider in Input Devices in pavucontrol has no effect at all; sound level remains constant. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 30 15:00:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-02-02 (270 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Em28xxAudio failed Symptom_Card: WinTV HVR-900 - Em28xx Audio Symptom_Type: No sound at all Title: [Em28xx-Audio - Em28xx Audio, recording] No sound at all UpgradeStatus: Upgraded to yakkety on 2016-10-25 (5 days ago) dmi.bios.date: 09/23/15 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.0057.B11.1509232013 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B11.1509232013:bd09/23/15:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.name: MacBookPro6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637837/+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 1637683] Re: ubuntu 16.10 internal speakers don't work, but headphones do
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1637683 Title: ubuntu 16.10 internal speakers don't work, but headphones do Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Under sound settings only headphone output is listed as an option, no internal speakers are listed. Headphone playback does work. In alsamixer, speaker output was at 0 and muted, but unmuting and increasing volume does not produce playback in speakers. ASUS X550LB laptop ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 28 20:42:56 2016 InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637683/+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 1648183] Re: Crackling and popping sound when using headphones
** Tags removed: yakkety ** Tags added: bionic -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1641959] Re: [CMI8786 - Xonar DG, playback] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1641959 Title: [CMI8786 - Xonar DG, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: ubuntu 16.10 3.9Gb AMD Penim(TM) II X4 965 Processor x4 GeFofce GTX 5590 Ti/PCIe/SSE2 64 hdd 59 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sergy113 2806 F...m pulseaudio /dev/snd/pcmC1D0p: sergy113 2806 F...m pulseaudio /dev/snd/controlC1: sergy113 2806 F pulseaudio /dev/snd/controlC0: sergy113 2806 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 15 17:07:14 2016 InstallationDate: Installed on 2016-11-09 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DG failed Symptom_Card: CMI8788 [Oxygen HD Audio] (CMI8786 (Xonar DG)) - Xonar DG Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sergy113 2806 F...m pulseaudio /dev/snd/pcmC1D0p: sergy113 2806 F...m pulseaudio /dev/snd/controlC1: sergy113 2806 F pulseaudio /dev/snd/controlC0: sergy113 2806 F pulseaudio Symptom_Type: No sound at all Title: [CMI8786 - Xonar DG, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd05/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-11-10T10:30:02.974053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1641959/+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 1838848] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485]
I don't think the log message "tracker-miner-f[1357] ..." is related to Bluetooth. Can you say what "Bluetooth device" is not detected? Are you talking about a particular Bluetooth peripheral, or is the Bluetooth icon itself missing? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838848 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485] Status in bluez package in Ubuntu: Incomplete Bug description: It's very familiar to Bug #1788807. I'm on 19.04. How can I help to solve it? 1) $lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 2) $ apt-cache policy bluez bluez: Установлен: 5.50-0ubuntu2 Кандидат: 5.50-0ubuntu2 Таблица версий: *** 5.50-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) Expectations: work as designed - no issues. 4) after resume from suspended state device is no longer available - if open gnome (UI) bluetooth manager in journal: 03 16:35:50 PC-Name tracker-miner-f[1357]: Could not process 'file:///home/user/%23534117': Error when getting information for file “/home/user/#534117”: Нет такого файла или каталога* *translation from russian: File or path does not exist $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 05) Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller [103c:3566] Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 05c8:021e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 5.0.0-23-generic [0.177448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.198830] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [3.257474] [Firmware Bug]: Invalid critical threshold (0) [4.140519] usb 6-1: Product: Bluetooth USB Host Controller [6.610450] Bluetooth: Core ver 2.22 [6.610478] Bluetooth: HCI device and connection manager initialized [6.610485] Bluetooth: HCI socket layer initialized [6.610488] Bluetooth: L2CAP socket layer initialized [6.610494] Bluetooth: SCO socket layer initialized [ 16.795026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.795029] Bluetooth: BNEP filters: protocol multicast [ 16.795036] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 3 16:19:13 2019 InstallationDate: Installed on 2019-08-03 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=670d7b88-4792-45a0-a2d1-b026d4926c27 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.3A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1838809] Re: Full screen doesn't work with SDL2.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1838809 Title: Full screen doesn't work with SDL2. Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When trying to enter full screen in SDL2 apps I just get a jittery mouse or a black screen. I've tried pygame2 apps and this simple C program: https://github.com/illume/pygame4000/blob/master/code/sdl2_basics_tutorial_fundamentals/hey.c But I replaced line 150 where it has SDL_WINDOW_RESIZABLE with SDL_WINDOW_FULLSCREEN. and I just get a black screen with a discolored bar at the top. I'm using Ubuntu 18.04.2 with sdl2.0.9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 2 11:13:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d0] NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0] InstallationDate: Installed on 2018-07-03 (394 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4236B16 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=0f9f42c8-a36e-4919-a9ba-8ad037dc193a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET78WW (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236B16 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET78WW(1.48):bd01/21/2016:svnLENOVO:pn4236B16:pvrThinkPadT420:rvnLENOVO:rn4236B16:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236B16 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838809/+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 1838818] Re: intel graphic
Thanks for the bug report. Can you please explain in more detail what the problem is? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1838818 Title: intel graphic Status in xorg-server package in Ubuntu: Incomplete Bug description: i cant launch my intel graphic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) Uname: Linux 5.0.0-05-generic i686 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Aug 2 20:42:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2019-08-01 (1 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-05-generic root=UUID=55255409-9bb4-47d0-8b50-c96ca1a24f27 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.3C dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3465LBF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: E9P66EA#BH4 dmi.product.version: 088F130059160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1907241930.6f4972~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1838818/+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 1836809] Re: segfault when CCD are present in two different HOG services
Please note that Bluetooth developers do not monitor Launchpad (AFAIK). So if you would like their feedback then please comment in the upstream bug instead: https://bugzilla.kernel.org/show_bug.cgi?id=204201 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+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 1609700] Re: username is not saved in openconnect connection dialog
I can confirm, this bug is back. The password is saved, but the username is not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1838836] Re: network-manager needs to be restarted frequently
What is the result from terminal for cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32
[Touch-packages] [Bug 1838848] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485]
Can you do dmesg | tail -30 in terminal after resume from suspend? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838848 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485] Status in bluez package in Ubuntu: New Bug description: It's very familiar to Bug #1788807. I'm on 19.04. How can I help to solve it? 1) $lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 2) $ apt-cache policy bluez bluez: Установлен: 5.50-0ubuntu2 Кандидат: 5.50-0ubuntu2 Таблица версий: *** 5.50-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) Expectations: work as designed - no issues. 4) after resume from suspended state device is no longer available - if open gnome (UI) bluetooth manager in journal: 03 16:35:50 PC-Name tracker-miner-f[1357]: Could not process 'file:///home/user/%23534117': Error when getting information for file “/home/user/#534117”: Нет такого файла или каталога* *translation from russian: File or path does not exist $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 05) Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller [103c:3566] Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 05c8:021e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 5.0.0-23-generic [0.177448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.198830] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [3.257474] [Firmware Bug]: Invalid critical threshold (0) [4.140519] usb 6-1: Product: Bluetooth USB Host Controller [6.610450] Bluetooth: Core ver 2.22 [6.610478] Bluetooth: HCI device and connection manager initialized [6.610485] Bluetooth: HCI socket layer initialized [6.610488] Bluetooth: L2CAP socket layer initialized [6.610494] Bluetooth: SCO socket layer initialized [ 16.795026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.795029] Bluetooth: BNEP filters: protocol multicast [ 16.795036] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 3 16:19:13 2019 InstallationDate: Installed on 2019-08-03 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=670d7b88-4792-45a0-a2d1-b026d4926c27 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.3A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name:
[Touch-packages] [Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
** Package changed: systemd (Ubuntu) => linux (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/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor Status in linux package in Ubuntu: Confirmed Bug description: Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0) Tried to boot 5.2.3 (but I believe this happened on 5.1.X too) It will boot to a certain extent, it does my disk password, i can see everything say "ok" when i do no quiet splash. But where it should go to the login screen I just see a single cursor Setting nomodeset lets me boot, looking at logs: Syslog Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 8.383s (userspace) = 49.675s. Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:59 kenji-mintop NetworkManager[1082]: [1564288139.7335] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new request (1 scripts) Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start running ordered scripts... Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615662] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615665] [drm] GPU recovery disabled. Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:19 kenji-mintop kernel: [ 70.855956] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856043] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856047] [drm] GPU recovery disabled. Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ connect: Host is unreachable] Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:29 kenji-mintop kernel: [ 81.095310] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095401] [drm] GPU recovery disabled. Jul 27 21:29:40 kenji-mintop kernel: [ 91.335557] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335645] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335648] [drm] GPU recovery disabled. Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ connect: Host is unreachable] Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data collection... Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data collection. Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:50 kenji-mintop kernel: [ 101.575935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576027] [drm] GPU recovery disabled. Jul 27 21:30:00 kenji-mintop kernel: [ 111.815551] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815638] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815642] [drm] GPU recovery disabled. Kern.log Jul 27 21:28:56 kenji-mintop kernel: [ 47.231201] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:57 kenji-mintop kernel: [ 48.907343] failed to write reg 28b4 wait reg 28c6 Jul 27 21:28:58 kenji-mintop kernel: [ 49.772880] capability: warning: `zerotier-one' uses 32-bit capabilities (legacy support in use) Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575]
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
The longer of your two attached log files, log-network-manager-without-
segmentation.txt, seems to contain at least one of your two tests, so I
extracted the part from your test starting (last start of network-
manager, with log verbosity set to contain and messages)
up to the end. I have attached this part to this posting as log-network-
manager-without-segmentation-2.txt.
When one searches for the string "current configuration:" one finds
where DNS configuration is changed due to network interfaces being added
or removed. The last of these occurrences is the only place where your
VPN (with your office's DNSes 172.27.0.42 and 172.27.0.33) gets added to
your phone's internet access (with DNS 192.168.42.129). Only in this
acase you get an error with pacrunner (PAC = Proxy Auto Configuration,
see https://wiki.gnome.org/Projects/NetworkManager/Proxies) but seems to
succeed later. There are also some other errors visible. Here are some
lines of the log:
--
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4886]
dns-mgr: current configuration: [{'nameservers': <['172.27.0.42',
'172.27.0.33']>, 'interface': <'tun2'>, 'priority': <50>, 'vpn': },
{'nameservers': <['192.168.42.129']>, 'interface': <'enp0s20f0u2'>, 'priority':
<100>, 'vpn': }]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4895]
dispatcher: (32) (tun2) dispatching action 'vpn-up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4900]
pacrunner: call[0x563b6899bc30]: send: new config ({'Interface': <'tun2'>,
'Method': <'direct'>, 'BrowserOnly': , 'Domains': <['172.31.252.244/24',
'172.27.0.0/24', '172.27.240.0/20', '192.168.222.0/24', '185.48.32.186/32',
'80.247.66.0/24', '87.248.32.84/32', '178.239.180.149/32', '80.247.66.96/32',
'87.248.32.223/32', '10.6.0.0/16', '172.31.252.0/24']>},)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4900]
pacrunner: call[0x563b6899bc30]: sending...
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4907]
pacrunner: call[0x563b6899bc30]: sending failed:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.pacrunner"
does not exist
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4907] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceStatisticsSke
leton: {'TxBytes': }
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4908] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceTunSkeleton:
{'Dhcp4Config': , 'Dhcp6Config': , 'Ip4Address':
, 'Ip4Config': , 'Ip6Config': , 'IpInterface': <''>, 'Managed': , 'State': ,
'StateReason': <(uint32 20, uint32 41)>}
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4909]
device[0x563b688b9c10] (tun2): ip4-config: update (commit=0,
new-config=0x563b688ab4a0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4910]
device[0x563b688b9c10] (tun2): ip6-config: update (commit=0,
new-config=0x563b688b4940)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4912]
manager: (tun2): assume: generated connection 'tun2'
(7ddca237-b609-4f44-bf54-9f3705d663ce)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4917]
settings: Failed to add 7ddca237-b609-4f44-bf54-9f3705d663ce/'tun2': Plugin
does not support adding connections
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4922]
settings-connection[0x563b68793a80]: constructed (NMSKeyfileConnection)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
update settings-connection flags to visible (was none)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
update settings-connection flags to unsaved,visible (was visible)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
keyfile: add connection in-memory (7ddca237-b609-4f44-bf54-9f3705d663ce,"tun2")
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4935]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
failed to read connection timestamp: Il file chiavi non presenta alcuna chiave
«7ddca237-b609-4f44-bf54-9f3705d663ce» nel gruppo «timestamps»
[...]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
dns-mgr: (device_state_changed): no DNS changes to commit (0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
device (tun2): Activation: successful, device activated.
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
device[0x563b688b9c10] (tun2): set metered value 4
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5345]
dispatcher: (34) (tun2) dispatching action 'up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5350]
pacrunner: call[0x563b689a10c0]: send: new config ({'Interface': <'tun2'>,
'Method': <'direct'>, 'BrowserOnly': },)
lug
[Touch-packages] [Bug 1838891] Re: qt5 applications crash when opening file chooser in gtk desktops
Can you please specify some more details about this issue: 1) Which Ubuntu release are you using? 18.04 (Bionic), 19.04 (Disco), 19.10 (Eoan) or some other? 2) What is the version of Qt package? I.e. the output of “apt policy qt5-gtk-platformtheme”. 3) What desktop environment does this happen on? Is this X11 or Wayland? If Wayland, is Qt using XWayland or running natively (does this happen when you run app with “-platform wayland”)? 4) What applications does this happen with? If this happens with many applications please name a few, so that I can look for crash logs in our error tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1838891 Title: qt5 applications crash when opening file chooser in gtk desktops Status in qtbase-opensource-src package in Ubuntu: New Bug description: Issue is apparently related to qt5-gtk-platformtheme. When you're in a non-Qt desktop environment and you open a file selection dialog from a Qt app it crashes. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1392605 https://bugs.archlinux.org/task/57984 https://github.com/TheAssassin/AppImageLauncher/issues/218 In my opinion this is a very serious issue and if newer Qt releases have fixed this it should be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+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 1836809] Re: segfault when CCD are present in two different HOG services
Hello, We have done some further investigation. During device pairing bluez is crashing. >From debugging I can see the 2 hog services with the correct attributes, then >one of the 2 hog services is reaching ref_count 0, hence it is getting freed, >but on the next read bluez is trying to use a corrupted hog service and during >reading its attributes we are receiving the segfault. With normal behavior the next step would be "Report characteristic descriptor written: notifications enabled", but crashes right before that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+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 1838891] [NEW] qt5 applications crash when opening file chooser in gtk desktops
Public bug reported: Issue is apparently related to qt5-gtk-platformtheme. When you're in a non-Qt desktop environment and you open a file selection dialog from a Qt app it crashes. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1392605 https://bugs.archlinux.org/task/57984 https://github.com/TheAssassin/AppImageLauncher/issues/218 In my opinion this is a very serious issue and if newer Qt releases have fixed this it should be backported. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1838891 Title: qt5 applications crash when opening file chooser in gtk desktops Status in qtbase-opensource-src package in Ubuntu: New Bug description: Issue is apparently related to qt5-gtk-platformtheme. When you're in a non-Qt desktop environment and you open a file selection dialog from a Qt app it crashes. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1392605 https://bugs.archlinux.org/task/57984 https://github.com/TheAssassin/AppImageLauncher/issues/218 In my opinion this is a very serious issue and if newer Qt releases have fixed this it should be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+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 1838890] [NEW] Suspected memory leak in xenial backport of fix for CVE-2019-13012
Public bug reported: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1838890 Title: Suspected memory leak in xenial backport of fix for CVE-2019-13012 Status in glib2.0 package in Ubuntu: New Bug description: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+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 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
Same here. Reported to https://bugzilla.kernel.org/show_bug.cgi?id=204325 Covers all 5.2.x kernels up to 5.2.5. No video, no KB response. But system runs. Can ssh into it. Runs fine on kernels up to 5.1.21. Ryzen 3 2200G using internal video. ** Bug watch added: Linux Kernel Bug Tracker #204325 https://bugzilla.kernel.org/show_bug.cgi?id=204325 -- 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/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor Status in systemd package in Ubuntu: Confirmed Bug description: Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0) Tried to boot 5.2.3 (but I believe this happened on 5.1.X too) It will boot to a certain extent, it does my disk password, i can see everything say "ok" when i do no quiet splash. But where it should go to the login screen I just see a single cursor Setting nomodeset lets me boot, looking at logs: Syslog Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 8.383s (userspace) = 49.675s. Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:59 kenji-mintop NetworkManager[1082]: [1564288139.7335] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new request (1 scripts) Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start running ordered scripts... Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615662] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615665] [drm] GPU recovery disabled. Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:19 kenji-mintop kernel: [ 70.855956] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856043] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856047] [drm] GPU recovery disabled. Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ connect: Host is unreachable] Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:29 kenji-mintop kernel: [ 81.095310] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095401] [drm] GPU recovery disabled. Jul 27 21:29:40 kenji-mintop kernel: [ 91.335557] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335645] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335648] [drm] GPU recovery disabled. Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ connect: Host is unreachable] Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data collection... Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data collection. Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:50 kenji-mintop kernel: [ 101.575935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576027] [drm] GPU recovery disabled. Jul 27 21:30:00 kenji-mintop kernel: [ 111.815551] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815638] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815642] [drm] GPU recovery disabled. Kern.log Jul 27 21:28:56 kenji-mintop kernel: [ 47.231201] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:57 kenji-mintop kernel: [ 48.907343] failed to write reg 28b4 wait reg 28c6 Jul
[Touch-packages] [Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor Status in systemd package in Ubuntu: Confirmed Bug description: Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0) Tried to boot 5.2.3 (but I believe this happened on 5.1.X too) It will boot to a certain extent, it does my disk password, i can see everything say "ok" when i do no quiet splash. But where it should go to the login screen I just see a single cursor Setting nomodeset lets me boot, looking at logs: Syslog Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 8.383s (userspace) = 49.675s. Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:59 kenji-mintop NetworkManager[1082]: [1564288139.7335] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new request (1 scripts) Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start running ordered scripts... Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615662] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615665] [drm] GPU recovery disabled. Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:19 kenji-mintop kernel: [ 70.855956] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856043] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856047] [drm] GPU recovery disabled. Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ connect: Host is unreachable] Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:29 kenji-mintop kernel: [ 81.095310] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095401] [drm] GPU recovery disabled. Jul 27 21:29:40 kenji-mintop kernel: [ 91.335557] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335645] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335648] [drm] GPU recovery disabled. Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ connect: Host is unreachable] Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data collection... Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data collection. Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:50 kenji-mintop kernel: [ 101.575935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576027] [drm] GPU recovery disabled. Jul 27 21:30:00 kenji-mintop kernel: [ 111.815551] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815638] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:30:00 kenji-mintop kernel: [ 111.815642] [drm] GPU recovery disabled. Kern.log Jul 27 21:28:56 kenji-mintop kernel: [ 47.231201] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:57 kenji-mintop kernel: [ 48.907343] failed to write reg 28b4 wait reg 28c6 Jul 27 21:28:58 kenji-mintop kernel: [ 49.772880] capability: warning: `zerotier-one' uses 32-bit capabilities (legacy support in use) Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Sorru for the late reply, I had a lot to do. I am not sure whether you have correctly taken the logs. Both are taken on July 25 but when you look into them, they span the following time frames: log-network-manager-with-segmentation.txt:Jan 31 - July 1 log-network-manager-without-segmentation.txt: Jan 31 - July 25 A "diff" shows also that all content of of the first is also in the second. It seems that the first got cut off during the upload. As they contain all history back to January, is it possible that the longer one (log-network-manager-without-segmentation.txt) contains both tests? Could you tell in which order you did the tests and which parts of the log reflect which test? Or could you re-test but this time reading the time stamps in the log before and after each test and upload only the logs of these time spans? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1837801] Re: [MESA] mesa 19.2 release will best support IceLake
** Package changed: ubuntu => mesa (Ubuntu) ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1837801 Title: [MESA] mesa 19.2 release will best support IceLake Status in intel: New Status in mesa package in Ubuntu: New Bug description: Description: MESA 19.2 release will best support IceLake platform. We'd better not miss it. 19.10 feature freeze is 08/22. 19.2-rc4 scheduled in 08/27, it should be the last release. 19.10 should can catch up with the final release of mesa 19.2. Target Release: 19.10 Target Package: 19.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1837801/+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 1837801] [NEW] [MESA] mesa 19.2 release will best support IceLake
You have been subscribed to a public bug: Description: MESA 19.2 release will best support IceLake platform. We'd better not miss it. 19.10 feature freeze is 08/22. 19.2-rc4 scheduled in 08/27, it should be the last release. 19.10 should can catch up with the final release of mesa 19.2. Target Release: 19.10 Target Package: 19.2 ** Affects: intel Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: intel-upkg-19.10 -- [MESA] mesa 19.2 release will best support IceLake https://bugs.launchpad.net/bugs/1837801 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1279060] Re: MIssing voicemail info for French provider Free
Please submit this change upstream, see: https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders#How_to_Contribute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider- info in Ubuntu. https://bugs.launchpad.net/bugs/1279060 Title: MIssing voicemail info for French provider Free Status in mobile-broadband-provider-info package in Ubuntu: New Bug description: I'm not sure if I just need to add 666 in the xml or if there are some wizardries to do, so I just open a bug for now. Provider is Free Mobile, country is France, and voicemail number is 666. Thanks :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1279060/+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 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
Hello everyone! No I have already tested Ubuntu 19.10 on Wayland. I have noticed that I don't see the problem with window flickering to black. Animations are more smoothly and beautiful: https://photos.app.goo.gl/1WiGYQziTSnrjrfz9 . I think Ubuntu 20.04 LTS should go with Wayland session as default. Why? Debian and Fedora use Wayland as a default. GNOME 3.34 will support good launching of X programms with XWayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+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
