[Touch-packages] [Bug 870001] Re: [Creative X-Fi 20K1 Unknown] Not recording input from microphone
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Confirmed => 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/870001 Title: [Creative X-Fi 20K1 Unknown] Not recording input from microphone Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Logitech headset with 3.5mm jack plugged into x-fi xtreme music microphone port. 1. xtreme music + 3.5mm microphone plugged into mic port 2. Check alsamixer to confirm mic port on, set to capture, and full audio 3. notice nothing happen 4. boot into windows and notice it working fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ikt1693 F pulseaudio /dev/snd/controlC1: ikt1693 F pulseaudio Card0.Amixer.info: Card hw:0 'STX'/'Asus Virtuoso 100 at 0xd800, irq 40' Mixer name : 'AV200' Components : 'PCM1792A CS5381 AV200' Controls : 18 Simple ctrls : 11 Card1.Amixer.info: Card hw:1 'XFi'/'Creative X-Fi 20K1 Unknown' Mixer name : '20K1' Components : '' Controls : 30 Simple ctrls : 11 Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xf7ffc000 irq 90' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] CheckboxCommand: alsa_record_playback CheckboxDescription: Connect a microphone to your microphone port. Select Test, then speak into the microphone. After a few seconds, your speech will be played back to you. Did you hear your speech played back? CheckboxTest: audio/alsa_record_playback_external Date: Sat Oct 8 00:10:27 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_AU.UTF-8 LANGUAGE=en_AU:en SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: 890FX Deluxe3 dmi.board.vendor: ASRock 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.:bvrP1.40:bd04/23/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890FXDeluxe3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/870001/+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 863423] Re: [USB-Audio - USB Device 0x46d:0x81a, recording] Device shows up in the mixer's "hardware" tab, but its input is not in the "input" tab
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Confirmed => 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/863423 Title: [USB-Audio - USB Device 0x46d:0x81a, recording] Device shows up in the mixer's "hardware" tab, but its input is not in the "input" tab Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When i plug in this webcam (Logictech C260), alsa detects it properly and it shows up as a second device in alsamixer with one input. It also shows up in the "hardware" tab of the gnome mixer, but in the "input" tab only the input from my HDA intel is shown. It looks like a pulseaudio issue to me, because it's not in pavucontrol either... and this is after pulseaudio failed to detect *any* device (input and output), but i already rebooted and forgot to collect information for that bug report :-/ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 1677 F pulseaudio /dev/snd/pcmC0D0c: riccardo 1677 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 43' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0269,10250364,00100100 HDA:80862804,80860101,0010' Controls : 24 Simple ctrls : 13 Card1.Amixer.info: Card hw:1 'U0x46d0x81a'/'USB Device 0x46d:0x81a at usb-:00:1d.0-1.2, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081a' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 4001 [65%] [21.62dB] [on] Date: Fri Sep 30 11:56:25 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:U0x46d0x81a failed Symptom_Card: 081a - USB Device 0x46d:0x81a Symptom_Type: None of the above Title: [USB-Audio - USB Device 0x46d:0x81a, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.13 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 3820 dmi.board.vendor: Acer dmi.board.version: V1.13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.13:bd05/04/2010:svnAcer:pnAspire3820:pvrV1.13:rvnAcer:rnAspire3820:rvrV1.13:cvnAcer:ct10:cvrV1.13: dmi.product.name: Aspire 3820 dmi.product.version: V1.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863423/+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 830007] Re: [HDA-Intel - HDA Intel, playback] fails after a while
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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/830007 Title: [HDA-Intel - HDA Intel, playback] fails after a while Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Probleem, Minul on ubuntu iga versiooniga jama. Minul on 5.1 süsteem ja analoog. Probleem selles et alsa ei suuda bassi igakord maha mängida filmiestiajas muudan stereo 5.1 siis mängib woofer kui on vajadus player kinni panna siis bas kadunud ja tuleb asi seadistada 4.1 siis hetkeks jälle tuleb bass see on ka ainus asi mis ei kisu linuxit kasutama, Problem is I have 5.1 analog audio it is alsa in sound settings i choose hardware and sound profile analog surround 5.1 + analog stereo input. Yes it works but no bass. It is fun part if i use mp3 sound in movie player and go to edit preferences and audio output type choose 5.1 and it start play bass if i close player to use next mp3 sound it not play bass anymore and needed to choose 4.1 in audio options then it play again in play bass too for listening one mp3 sound It happen any any release of ubuntu. Subwoofers revels not change for next sound i miss bass subwoofer any app in needed anytime change output I have p5q deluxe motherboard with integrated sound it use AD2000B chip for sound. Problem is subwoofer level for listening sound and i needed to change play levels to play levels and input 5.1 to 4.1 anytime somtime i hear cracking sound. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: m 1646 F pulseaudio /dev/snd/pcmC0D0p: m 1646 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe8f8000 irq 45' Mixer name : 'Analog Devices AD1989B' Components : 'HDA:11d4989b,10438311,00100300' Controls : 47 Simple ctrls : 26 Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xfe9fc000 irq 46' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat Aug 20 13:46:31 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=et_EE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Type: Sound works for a while, then breaks Title: [HDA-Intel - HDA Intel, playback] fails after a while UpgradeStatus: Upgraded to oneiric on 2011-08-20 (0 days ago) dmi.bios.date: 07/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/830007/+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 868726] Re: [Sony VPCYB15KX, Realtek ALC269VB] Sound is muted at every boot
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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/868726 Title: [Sony VPCYB15KX, Realtek ALC269VB] Sound is muted at every boot Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The sound work but if I enable the sound at the next reboot the sound is disable again, I need to enable everytime [VPCYB15KX, Realtek ALC269VB, Speaker, Internal] Playback problem ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ivan 1868 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xf0244000 irq 42' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'SB'/'HDA ATI SB at 0xf024 irq 16' Mixer name : 'Realtek ALC269VB' Components : 'HDA:10ec0269,104d5400,00100100' Controls : 14 Simple ctrls : 9 Date: Wed Oct 5 23:15:47 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Audio interno - HDA ATI SB Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [VPCYB15KX, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to oneiric on 2011-10-02 (3 days ago) dmi.bios.date: 12/22/2010 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0160Z7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0160Z7:bd12/22/2010:svnSonyCorporation:pnVPCYB15KX:pvrC9005E77:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCYB15KX dmi.product.version: C9005E77 dmi.sys.vendor: Sony Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2011-02-17T21:34:56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/868726/+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 696344] Re: Internal Mic seen but unable to be used.
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011. 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: Confirmed => 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/696344 Title: Internal Mic seen but unable to be used. Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Using Asus EeePC 1005. Mic is seen by system, but does not detect sound. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ronnie 1329 F pulseaudio /dev/snd/pcmC0D0p: ronnie 1329 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 22' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,104383ce,0014' Controls : 12 Simple ctrls : 7 Date: Sat Jan 1 13:36:39 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Realtek ALC269] Recording problem dmi.bios.date: 09/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1005HA dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005HA dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/696344/+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 795493] Re: [Inspiron 530, Realtek ALC888, Green Line Out, Rear] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Confirmed => 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/795493 Title: [Inspiron 530, Realtek ALC888, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Worked fine in Natty and very recently in Oneiric. As of now, no sound at all, and apps that try and produce sound (Banshee) tends to hang. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eapache1650 F pulseaudio /dev/snd/controlC1: eapache1650 F pulseaudio Date: Fri Jun 10 07:47:17 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.utf8 LC_MESSAGES=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 4 0 1 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Internal Audio - HDA Intel Symptom_DevicesInUse: 1650 1650 eapache F pulseaudio F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : I n t e l e r r o r : N o s u c h d e v i c e Title: [Inspiron 530, Realtek ALC888, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-05-28 (12 days ago) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/795493/+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 832184] Re: [SB Live! Value [CT4832]] Changing front output volume affects rear output volume
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. 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: Triaged => 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/832184 Title: [SB Live! Value [CT4832]] Changing front output volume affects rear output volume Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Now that all the outputs are supported (see bug 560178), there is still something wrong with the mixer elements. In Analog Surround 4.0 Output + Analog Stereo Input mode (where fortunately also digital output is enabled; I don't know about the digital input) Steps to reproduce: Select Output Devices tab in pavucontrol (0.9.9-1) set all channels equal somewhere between Silence and Base Unlock channels Increase level of front channels Result: Front volume is increased and rear volume is decreased (even if the visible Rear channel mixer elements do not move) Expected result: Front volume is increased and rear volume stays unchanged ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: pulseaudio 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Value [CT4832] (rev.6, serial:0x80271102) at 0xc000, irq 19' Mixer name : 'TriTech TR28602' Components : 'AC97a:54524123' Controls : 216 Simple ctrls : 38 Date: Tue Aug 23 19:15:51 2011 EcryptfsInUse: Yes InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110426.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7051 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/25/2005:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7051:rvr:cvn:ct3:cvr: mtime.conffile..etc.pulse.daemon.conf: 2011-08-20T01:15:00.412912 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/832184/+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 857073] Re: Internal speakers don't work on the Samsung Series 5 Chromebook
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Triaged => 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/857073 Title: Internal speakers don't work on the Samsung Series 5 Chromebook Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The internal speakers aren't working with Ubuntu on the Samsung Series 5 Chromebook. The headphone port and microphone work fine, however. Following the instructions in the comment section on this article, I grabbed the contents of /etc/modprobe.d/alsa.conf from Chrome OS and pasted it into /etc/modprobe.d/alsa-base.conf on Ubuntu, but unfortunately that still didn't fix my problem. http://chromeos-cr48.blogspot.com/2011/04/ubuntu-1104-for-cr-48-is- ready.html It might be worth noting that sound through the internal speakers has worked before - initially it was running fine with Ubuntu 11.04 until there was a backports update to alsa, and since I did a dist-upgrade to Oneiric for testing, I haven't been able to get sound working through the internal speakers again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 Uname: Linux 2.6.38.3+ i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 1.23-0ubuntu1 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2485 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9220 irq 43' Mixer name : 'Realtek ALC272' Components : 'HDA:10ec0272,144dc0a7,0011' Controls : 14 Simple ctrls : 8 Date: Fri Sep 23 18:00:32 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: Upgraded to oneiric on 2011-09-07 (16 days ago) dmi.bios.date: 04/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: Alex.03.61.0735.0056G3.0021 dmi.board.asset.tag: SAMSUNG dmi.board.name: G100 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrAlex.03.61.0735.0056G3.0021:bd04/07/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnAlex:pvrAlex.03.61.0735.0056G3.0021:rvnSAMSUNGELECTRONICSCO.,LTD.:rnG100:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A: dmi.product.name: Alex dmi.product.version: Alex.03.61.0735.0056G3.0021 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2011-09-23T17:51:18.431212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/857073/+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 794390] Re: [K40IJ/K50IJ, VIA VT1708S, Green Headphone Out, Rear] No automute
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. 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: Fix Committed => 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/794390 Title: [K40IJ/K50IJ, VIA VT1708S, Green Headphone Out, Rear] No automute Status in alsa-driver package in Ubuntu: Won't Fix Bug description: whenever i plug in my headphone jack into laptop, the speakers of laptop and the headphone both continue to sound, the laptop speakers are not automatically muted. i have checked all the steps through your forums but the problem is un resolved, i would definitely say that this is a bug in your Ubuntu and you people haven't fixed it yet. Ubuntu is still full of bugs even after so many releases, i like it, but it is difficult to use rather than windows, i am also having problems with mounting NTFS partitions in this release, although ntfs- 3g is already installed but two of my NTFS drives are also not visible in gnome. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: razzi 1508 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 45' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,1043,0010' Controls : 26 Simple ctrls : 16 Date: Wed Jun 8 02:20:49 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internal Audio - HDA Intel Symptom_Jack: Green Headphone Out, Rear Symptom_Type: No auto-mute between outputs Title: [K40IJ, VIA VT1708S, Green Headphone Out, Rear] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K40IJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr209:bd07/10/2009:svnASUSTeKComputerInc.:pnK40IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK40IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K40IJ 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/794390/+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 818946] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. 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: Confirmed => 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/818946 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Sound was working fine until I installed some updates yesterday, now it's not working at all. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robinsjp 1489 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe5f8000 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1043841b,00100302' Controls : 32 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe7e8000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sun Jul 31 18:59:09 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: RS880 Audio Device [Radeon HD 4200] - HDA ATI HDMI Symptom_DevicesInUse: 1489 Symptom_Type: No sound at all Title: [HDA-Intel - HDA ATI SB, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M EVO 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.:bvr1701:bd09/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/818946/+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 870907] Re: [Phoenix M622UCX, AC'97 (Conexant Cx20468-31)] sound doesnt play..tried system testing..found bug
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Confirmed => 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/870907 Title: [Phoenix M622UCX, AC'97 (Conexant Cx20468-31)] sound doesnt play..tried system testing..found bug Status in alsa-driver package in Ubuntu: Won't Fix Bug description: sound does'nt play in y laptop even after changing the settings. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: subhankar 2379 F pulseaudio /dev/snd/pcmC0D0p: subhankar 2379 F...m pulseaudio Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with Cx20468-31 at irq 17' Mixer name : 'Conexant Cx20468-31' Components : 'AC97a:43585430' Controls : 23 Simple ctrls : 16 CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink' CheckboxDescription: Select Test to play a sound on the automatically detected playback device. Did you hear a sound and was that sound free of any distortion, clicks or other strange noises? CheckboxTest: audio/playback_auto Date: Sun Oct 9 00:08:52 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_IN LANGUAGE=en_IN:en SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2006 dmi.bios.vendor: Phoenix dmi.bios.version: HCL0FT02 dmi.board.name: M622UCX dmi.board.vendor: HCL Infosystems Limited dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrHCL0FT02:bd02/23/2006:svnHCLInfosystemsLimited:pnM622UCX:pvrNotApplicable:rvnHCLInfosystemsLimited:rnM622UCX:rvrNotApplicable:cvnNoEnclosure:ct8:cvrN/A: dmi.product.name: M622UCX dmi.product.version: Not Applicable dmi.sys.vendor: HCL Infosystems Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/870907/+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 871633] Re: [HP Pavilion dv6, IDT 92HD75B3] Line out does not mute internal speakers
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Triaged => 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/871633 Title: [HP Pavilion dv6, IDT 92HD75B3] Line out does not mute internal speakers Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Well my card info is attached so I can't switch to headphones only in alsa. In Maverick and Natty I used to be able to switch via going to Sound>Output and switching to Analog Output instead of Analog Speakers. The Analog Output option is not available in Ubuntu Oneiric and I tried switching directly from the Alsa Mixer but it didn't have a "headphones" option either. Sound comes out of both the headphone and speakers when headphone is plugged in. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bayan 1667 F pulseaudio /dev/snd/controlC0: bayan 1667 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdb10 irq 43' Mixer name : 'IDT 92HD75B3X5' Components : 'HDA:111d7603,103c3659,00100202' Controls : 20 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Mon Oct 10 11:18:26 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.17 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3659 dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.17:bd02/06/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.24:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049D212412102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871633/+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 1078028] Re: Volume level is 100% when a bluetooth sound device is reconnected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/1078028 Title: Volume level is 100% when a bluetooth sound device is reconnected Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have a Bluetooth headphone with a high volume output, and usually I set it to a half volume level on "sound-nua" applet. However, if I disconnect/reconnect the headphone, the sound level is not restored, the headphone is not set as default output on applet devices list, and the sound control keys on my keyboard (I'm on a laptop) actually change the main volume output (laptop speakers) instead of set the phone volume, despite of the sound being played on my phone upon connecting it. The biggest problem is that the volume will be set to 100% on my phone and almost bleed my ears =/. I have to open the sound settings, select the headphone as output, and set a lower volume level. I think the system should restore the last settings to each output device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1078028/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
** Tags removed: oneiric -- 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/874535 Title: Volume Slider Jumps, due to rapidly changing hardware jack sense state Status in alsa-driver package in Ubuntu: Triaged Bug description: In Oneiric Release, The volume slider randomly jump down a notch or two for fraction of a second, even when there is no audio playing on the system. If mute is selected, the menu will quickly flip out of mute mode and back again. This change actually affects the audio output, resulting in pops correlated with the volume changes. nVidia GF106 Audio Controller --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfrorie9959 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1462522c,00100302' Controls : 35 Simple ctrls : 20 Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Package: pulseaudio 1:1.0-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: X58A-GD45 (MS-7522) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0: dmi.product.name: MS-7522 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => 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/1245624 Title: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hello I've been using the kernel Linux 3.0.100 kernel, and since then (subsequent versions), I don’t have support analog for this chipset. I ask whether you can solve. Thanks Regards Toni ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 2249 F pulseaudio /dev/snd/controlC1: toni 2249 F pulseaudio /dev/snd/controlC0: toni 2249 F pulseaudio Date: Mon Oct 28 19:29:17 2013 HibernationDevice: RESUME=UUID=146689ca-5189-4daa-87d7-b59d90ce4ac6 InstallationDate: Installed on 2013-05-07 (173 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: HP-Pavilion GJ306AA-ABE m8175.es MarkForUpload: True ProcEnviron: LANGUAGE=ca_AD:ca PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_AD.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=11a5f37e-f23e-4f05-8e78-0e1d97767d70 ro vga=791 acpi_sleep=s3_bios,s3_mode libata.atapi_enabled=1 combined_mode=libata RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (10 days ago) dmi.bios.date: 07/11/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.05 dmi.board.name: Berkeley dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GJ306AA-ABE m8175.es dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245624/+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 862748] Re: hedgewars crashed with SIGFPE in Mix_FadeInMusicPos()
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. 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: Confirmed => 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/862748 Title: hedgewars crashed with SIGFPE in Mix_FadeInMusicPos() Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hedgewars didn't start at mouse clic and this bug report appeared ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hedgewars 0.9.15-4 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Thu Sep 29 22:18:58 2011 ExecutablePath: /usr/lib/hedgewars/bin/hedgewars InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901) ProcCmdline: hedgewars Signal: 8 SourcePackage: hedgewars StacktraceTop: Mix_FadeInMusicPos () from /usr/lib/libSDL_mixer-1.2.so.0 Mix_FadeInMusic () from /usr/lib/libSDL_mixer-1.2.so.0 SDLInteraction::StartMusic() () HWForm::qt_metacall(QMetaObject::Call, int, void**) () QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: hedgewars crashed with SIGFPE in Mix_FadeInMusicPos() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/862748/+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 886975] Re: [Thinkpad R61i/T61] Lenovo sound chip Conexant CX20549 Venice doesn't work correctly.
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. Ubuntu 12.04 (precise) reached end-of-life on April 28, 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: Confirmed => 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/886975 Title: [Thinkpad R61i/T61] Lenovo sound chip Conexant CX20549 Venice doesn't work correctly. Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Computer: IBM Lenovo Thinkpad R61i Card: HDA Intel Sound chip: Conexant CX20549 (Venice) Device: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) Subsystem: Lenovo ThinkPad T61 [17aa:20ac] System: Ubuntu Oneiric 11.10 (desktop-i386) Kernel: 3.0.0-12-generic-pae#20-Ubuntu SMP Fri Oct 7 16:37:17 UTC 2011 Problems: 1) Integrated microphone doesn't work at all because the driver uses node 0x14 instead of 0x15 for integrated mic and node 0x12 instead of 0x14 for external mic. 2) Sound output is muted in the "0% <-> unamplified" part of the volume slider and is working in the "unamplified <-> 100% ->" part only; the driver doesn't allow amplified part because sound is distorted over 0dB of the PCM level so there is no need amplified part of the volume slider. Solution: Attached patch is fixing nodes of integrated and external microphone and is removing the amplified part of the volume slider. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c4pp4 1698 F pulseaudio /dev/snd/pcmC0D0p: c4pp4 1698 F...m pulseaudio CRDA: Error: [Errno 2] Adresář nebo soubor neexistuje Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe10 irq 48' Mixer name : 'Conexant CX20549 (Venice)' Components : 'HDA:14f15045,17aa20db,00100100' Controls : 19 Simple ctrls : 10 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=6e091b39-d59a-4d75-a7c5-dec246d020e5 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: LENOVO 89329ZG Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=666241df-0a9e-4711-a44e-92d2e6f5eccc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic-pae N/A linux-backports-modules-3.0.0-12-generic-pae N/A linux-firmware1.60 Tags: oneiric Uname: Linux 3.0.0-12-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers dmi.bios.date: 04/09/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7OETC4WW (2.24 ) dmi.board.name: 89329ZG 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:bvr7OETC4WW(2.24):bd04/09/2010:svnLENOVO:pn89329ZG:pvrThinkPadR61/R61i:rvnLENOVO:rn89329ZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 89329ZG dmi.product.version: ThinkPad R61/R61i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/886975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login
** Tags removed: saucy trusty ** Tags added: xenial -- 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+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 1152137] Re: Pulseaudio won't start when home directory not owned by user
** Tags removed: trusty -- 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/1152137 Title: Pulseaudio won't start when home directory not owned by user Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an NFS mounted home directory on a dedicated fileserver which is shared with Windows PCs via SMB. The home directory is not owned by me. ACLs are set on it to allow me full control of the contents but prevent me from changing its permissions. This means any files or directories created in the home directory are owned by me even though the top level is not. Pulseaudio checks the home directory is owned by the user at startup and exits if it isn't. This stops it running on my system. I have recompiled pulseaudio without this check and it works fine. Please either remove or modify the following startup check: pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415: if (st.st_uid != getuid()) { pa_log_error("Home directory %s not ours.", h); errno = EACCES; goto finish; } A better check would be for pulseaudio to try and create the files/folders it needs and fail if it cannot. I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+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 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on front panel
** Tags removed: trusty yakkety -- 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/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on front panel Status in pulseaudio package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In Windows it works normally. Workaround: 1. Start alsamixer from a terminal. 2. Press F6 to select the Xonar sound card 3. Press F4 to see recording controls. 4. Use arrow keys to find a control named "Mic Source" and change it from "Mic Jack" to "Front Panel". Still actual for: Ubuntu 16.04 x64 4.3.0-2-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/pulseaudio/+bug/1171435/+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 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
Thank you for reporting this bug to Ubuntu. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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. -- 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/1245624 Title: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hello I've been using the kernel Linux 3.0.100 kernel, and since then (subsequent versions), I don’t have support analog for this chipset. I ask whether you can solve. Thanks Regards Toni ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 2249 F pulseaudio /dev/snd/controlC1: toni 2249 F pulseaudio /dev/snd/controlC0: toni 2249 F pulseaudio Date: Mon Oct 28 19:29:17 2013 HibernationDevice: RESUME=UUID=146689ca-5189-4daa-87d7-b59d90ce4ac6 InstallationDate: Installed on 2013-05-07 (173 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: HP-Pavilion GJ306AA-ABE m8175.es MarkForUpload: True ProcEnviron: LANGUAGE=ca_AD:ca PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_AD.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=11a5f37e-f23e-4f05-8e78-0e1d97767d70 ro vga=791 acpi_sleep=s3_bios,s3_mode libata.atapi_enabled=1 combined_mode=libata RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (10 days ago) dmi.bios.date: 07/11/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.05 dmi.board.name: Berkeley dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GJ306AA-ABE m8175.es dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245624/+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 1183398] Re: pulseaudio can't start on NFSv4 home
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/1183398 Title: pulseaudio can't start on NFSv4 home Status in pulseaudio package in Ubuntu: Won't Fix Bug description: When I configure 12.04 LTS to use autofs and nfs mount the home volume, pulseaudio stops working. Although permissions in $HOME seem correct, it fails with this error: $ pulseaudio --start E: [autospawn] core-util.c: Failed to create secure directory: Operation not permitted W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock $ df -h . Filesystem Size Used Avail Use% Mounted on eckserver:/export/home3 1009G 483G 517G 49% /home3/eckserver strace of `pulseaudio --start' attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1183398/+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 1690046] Re: pacat crashed with SIGABRT in pa_xrealloc() from stream_read_callback() from pstream_memblock_callback() from do_read() from do_pstream_read_write()
** Tags removed: artful trusty utopic vivid wily yakkety zesty -- 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/1690046 Title: pacat crashed with SIGABRT in pa_xrealloc() from stream_read_callback() from pstream_memblock_callback() from do_read() from do_pstream_read_write() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/859197789d2ec8b939e60f93e38b6cb47a0af9e1 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/+source/pulseaudio/+bug/1690046/+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 1690047] Re: pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() from pa_source_post() from mmap_read() from thread_func()
** Tags removed: artful quantal saucy trusty utopic vivid yakkety zesty -- 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/1690047 Title: pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() from pa_source_post() from mmap_read() from thread_func() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5cde18a2c21560bb02b3e1f7dfe4ba24cc6cb02b 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/+source/pulseaudio/+bug/1690047/+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 1690071] Re: pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from speex_resampler_process_native() from speex_resampler_process_float() from speex_resampl
** Tags removed: artful precise trusty vivid wily zesty -- 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/1690071 Title: pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from speex_resampler_process_native() from speex_resampler_process_float() from speex_resampler_process_interleaved_float() from speex_resample_float() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/aae62bd41aea287ef4e95b261916bd17e9f6788f 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/+source/pulseaudio/+bug/1690071/+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 1690064] Re: pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop()
** Tags removed: artful precise saucy trusty utopic vivid wily yakkety zesty -- 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/1690064 Title: pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/114999a1ffc982bfc5fb50105a1ca8f4cfe5ab4a 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/+source/pulseaudio/+bug/1690064/+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 1690078] Re: pulseaudio crashed with SIGABRT in pa_sink_render_full() from sink_input_pop_cb() from pa_sink_input_peek() from fill_mix_info() from pa_sink_render_into()
** Tags removed: artful raring saucy trusty zesty -- 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/1690078 Title: pulseaudio crashed with SIGABRT in pa_sink_render_full() from sink_input_pop_cb() from pa_sink_input_peek() from fill_mix_info() from pa_sink_render_into() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a728e7efc5805597d6b2cd7bd0c18521c08afb8 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/+source/pulseaudio/+bug/1690078/+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 1690024] Re: pulseaudio crashed with SIGABRT in memblock_replace_import() from pa_memimport_free() from pa_pstream_unlink() from native_connection_unlink() from pstream_die_callb
** Tags removed: artful kylin-15.04 saucy trusty utopic vivid wily yakkety zesty -- 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/1690024 Title: pulseaudio crashed with SIGABRT in memblock_replace_import() from pa_memimport_free() from pa_pstream_unlink() from native_connection_unlink() from pstream_die_callback() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8ae1880098bcd68e85ab2259ab41aabcdf170705 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/+source/pulseaudio/+bug/1690024/+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 1690050] Re: pulseaudio crashed with SIGABRT in pa_rtpoll_set_timer_relative() from thread_func() from internal_thread_func() from start_thread() from clone()
** Tags removed: artful precise quantal raring saucy trusty utopic vivid wily yakkety zesty -- 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/1690050 Title: pulseaudio crashed with SIGABRT in pa_rtpoll_set_timer_relative() from thread_func() from internal_thread_func() from start_thread() from clone() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7b48f61206e9d4d82be7ff893f162e20c5c4538b 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/+source/pulseaudio/+bug/1690050/+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 1059185] Re: bluetooth-wizard doesn't find any devices
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => 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/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+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 1299236] Re: Bluetooth stays on after reboot in Trusty beta 14.04 even if was set as off before
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1299236 Title: Bluetooth stays on after reboot in Trusty beta 14.04 even if was set as off before Status in bluez package in Ubuntu: Won't Fix Bug description: Even if you put bluetooth off, it stays on after every reboot in Trusty beta 14.04. In Precise, I set it off once and it remained so after every reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 28 22:19:50 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=bf310eaf-be78-4eb0-bc3b-3d556643a61c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/18/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: AC:72:89:D2:05:09 ACL MTU: 310:10 SCO MTU: 64:8 DOWN RX bytes:501 acl:0 sco:0 events:22 errors:0 TX bytes:329 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1299236/+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 1276897] Re: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed.
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1276897 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Status in bluez package in Ubuntu: Won't Fix Bug description: I tried to connect via bluetooth to my desktop computer using my Galago Ultrapro Laptop. I connected...and then i recieved this error afterwards. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AssertionMessage: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Date: Wed Feb 5 20:22:32 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-02-05 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Galago UltraPro ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=bb82e1d2-7c73-4c90-9f41-2b7f805b6082 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: bluez StacktraceTop: __assert_fail_base (fmt=0x7fee829afbe0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fee8380b09e "hs->pending != ((void *)0)", file=file@entry=0x7fee8380ae40 "audio/headset.c", line=line@entry=1487, function=function@entry=0x7fee8380bdd4 "get_record_cb") at assert.c:92 __GI___assert_fail (assertion=0x7fee8380b09e "hs->pending != ((void *)0)", file=0x7fee8380ae40 "audio/headset.c", line=1487, function=0x7fee8380bdd4 "get_record_cb") at assert.c:101 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 0C:8B:FD:74:45:E5 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:5057 acl:60 sco:0 events:220 errors:0 TX bytes:20189 acl:59 sco:0 commands:141 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1276897/+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 1283621] Re: Bluetooth adapter not detected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283621 Title: Bluetooth adapter not detected Status in bluez package in Ubuntu: Won't Fix Bug description: In previous versions (<= Raring) I was able to turn on the bluetooth (on Raring I had to install blueman). Currently my device is not detected. Commands such as `rfkill list`, `hcitool dev`, `lsusb` won't show any bluetooth device. My laptop is an hp nx7400. I installed Debian wheezy, just to make sure I am not going crazy. And, yes, on wheezy bluetooth is functional (tested with KDE+bluedevil). Maybe this is related to the kernel/udev versions? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Sat Feb 22 22:13:17 2014 InstallationDate: Installed on 2014-01-14 (39 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140113) InterestingModules: bnep rfcomm bluetooth MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=96147aaf-4d58-4669-83a5-18e2f94dbd65 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YGU Ver. F.0A dmi.board.name: 30A2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.17 dmi.chassis.asset.tag: CNU7111JLR dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx7400 (GF451LA#ABM) dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1283621/+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 1305351] Re: bluetoothd crashed with SIGSEGV in g_slist_remove()
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1305351 Title: bluetoothd crashed with SIGSEGV in g_slist_remove() Status in bluez package in Ubuntu: Won't Fix Bug description: Tried to get my Bluetooth device to turn on again by installing Blueman. While changing name and visibility, thiis happened. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Thu Apr 10 01:16:16 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) InterestingModules: btusb bnep rfcomm bluetooth MachineType: Sony Corporation SVP1321M2EB ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f999169 : cmp %rsi,(%rdi) PC (0x7f999169) ok source "%rsi" ok destination "(%rdi)" (0x6567612f6e616d65) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: g_slist_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () ?? () Title: bluetoothd crashed with SIGSEGV in g_slist_remove() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1043V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1043V7:bd11/21/2013:svnSonyCorporation:pnSVP1321M2EB:pvrC60C0754:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321M2EB dmi.product.version: C60C0754 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:13:9F:5B ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:9804 acl:89 sco:0 events:504 errors:0 TX bytes:210292 acl:250 sco:0 commands:219 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1305351/+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 1305890] Re: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1305890 Title: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter Status in bluez package in Ubuntu: Won't Fix Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 patryk@Aspire-E1-772G:~$ apt-cache policy bluez bluez: Zainstalowana: 4.101-0ubuntu12 Kandydująca: 4.101-0ubuntu12 Tabela wersji: *** 4.101-0ubuntu12 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ bluez-simple-service Traceback (most recent call last): File "/usr/bin/bluez-simple-service", line 112, in path = manager.DefaultAdapter() File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter patryk@Aspire-E1-772G:~$ patryk@Aspire-E1-772G:~$ sudo hcidump -XYt > $HOME/hci.log Can't open device: No such device patryk@Aspire-E1-772G:~$ On Windows 8 bluetooth working great. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 15:19:24 2014 ExecutablePath: /usr/bin/bluez-simple-service InstallationDate: Installed on 2014-03-01 (39 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) InterestingModules: btusb rfcomm bnep bluetooth InterpreterPath: /usr/bin/python2.7 MachineType: Acer Aspire E1-772G ProcCmdline: /usr/bin/python /usr/bin/bluez-simple-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=a121d353-840a-4d56-979e-6870e7bf3541 ro quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/bluez-simple-service'] SourcePackage: bluez Title: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HW dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd01/28/2014:svnAcer:pnAspireE1-772G:pvrV1.03:rvnAcer:rnEA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-772G dmi.product.version: V1.03 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1305890/+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 1284649] Re: bluetooth devices no longer connect to the system
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1284649 Title: bluetooth devices no longer connect to the system Status in bluez package in Ubuntu: Won't Fix Bug description: Up until some recent trusty update (maybe a week or two ago), bluetooth worked fine, but after the update none of my bluetooth devices connect to the system, nor can I add new ones. The devices I use are an LG HBS-700 headset, an Apple Keyboard and Trackpad. I plugged in an Asus atheros based bluetooth dongle to see if it was the Broadcom driver no longer working, but I have been unable to get that to work either and it has also worked successfully in Ubuntu before. I ran the bluez-hcidump command that was suggested, but it complains about no device being found. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 25 08:47:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-14 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic.efi.signed root=UUID=aa52ad82-1d45-4456-972d-493b1dab370e ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B03.1310291227 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci1:Type: BR/EDR Bus: USB BD Address: 60:03:08:9A:5C:D1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:558 acl:0 sco:0 events:28 errors:0 TX bytes:355 acl:0 sco:0 commands:28 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284649/+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 1292879] Re: bluetoothd crashed with SIGSEGV in finalize_setup_errno()
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1292879 Title: bluetoothd crashed with SIGSEGV in finalize_setup_errno() Status in bluez package in Ubuntu: Won't Fix Bug description: When I paring bluetooth device sometimes the device was appear only in MONO, but this device is a stereo headphone. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sat Mar 15 12:07:11 2014 Disassembly: => 0x20: Não é possível acessar a memória no endereço 0x20 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-03-13 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Hewlett-Packard HP G42 Notebook PC ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=4b2231d5-0eba-4ddf-810c-08dfb9d7b13b ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x20: Não é possível acessar a memória no endereço 0x20 PC (0x0020) not located in a known VMA region (needed executable region)! source "0x20" (0x0020) not located in a known VMA region (needed readable region)! SegvReason: executing NULL VMA reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1445 dmi.board.vendor: Hewlett-Packard dmi.board.version: 69.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr05961224271010100:rvnHewlett-Packard:rn1445:rvr69.37:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 05961224271010100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: CC:52:AF:A9:48:7F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:83416 acl:84 sco:1567 events:124 errors:0 TX bytes:82252 acl:71 sco:1542 commands:65 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1292879/+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 1315290] Re: Broadcom BCM2046 Bluetooth not detected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1315290 Title: Broadcom BCM2046 Bluetooth not detected Status in bluez package in Ubuntu: Won't Fix Bug description: The bluez package provides some udev rules in /lib/udev/rules.d/97 -bluetooth-hid2hci.rules to switch some Dell devices into hci mode. The same is necessary for Broadcom BCM2046 based devices. To get bluetooth working on my Lenovo Ideacentre B320 I added the following rule to my local rules: -- #udev rules für Lenovo Ideacentre Bluetooth ACTION=="remove", GOTO="idea_end" SUBSYSTEM!="usb", GOTO="idea_end" # Variety of Broadcom Bluetooth devices - match on a mouse device that is # self powered and where a HID report needs to be sent to switch modes # Known supported devices: 0a5c:4503 ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", ATTR{bInterfaceProtocol}=="02", \ ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="0a5c", ATTRS{bmAttributes}=="c0", \ RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1" LABEL="idea_end" -- Please add this rule to 97-bluetooth-hid2hci.rules ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 10:27:22 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO IdeaCentre B320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3b23e969-65c7-4c68-b502-67bac2ef656a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: DXKT33AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: 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:bvnLENOVO:bvrDXKT33AUS:bd08/07/2012:svnLENOVO:pnIdeaCentreB320:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: IdeaCentre B320 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 40:2C:F4:F4:E2:8C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1062 acl:0 sco:0 events:54 errors:0 TX bytes:1434 acl:0 sco:0 commands:54 errors:0 modified.conffile..etc.bluetooth.main.conf: [modified] mtime.conffile..etc.bluetooth.main.conf: 2014-05-02T08:13:42.321372 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1315290/+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 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death
** Tags removed: trusty ** Tags added: bionic -- 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/1341256 Title: Press caps lock on bluetooth keyboard then the keyboard go death Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 1314188] Re: Bluetooth disconnects devices regularly
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1314188 Title: Bluetooth disconnects devices regularly Status in bluez package in Ubuntu: Won't Fix Bug description: My mouse suddenly disconnects randomly, while I am using it. Works fine for a while, suddenly it seems to disconnects because I can't use it, and then I press all the buttons, restart the mouse, or forces the Bluetooth to connect using the Bluetooth indicator again, and suddenly it works again. Same thing goes for other Bluetooth devices. Using my Nexus 4 as a Bluetooth modem it's the same. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 29 14:31:07 2014 InstallationDate: Installed on 2014-04-09 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) InterestingModules: btusb bnep rfcomm bluetooth MachineType: Sony Corporation SVP1321M2EB ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1043V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1043V7:bd11/21/2013:svnSonyCorporation:pnSVP1321M2EB:pvrC60C0754:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321M2EB dmi.product.version: C60C0754 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:13:9F:5B ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:403335 acl:25092 sco:0 events:158 errors:0 TX bytes:1137 acl:9 sco:0 commands:40 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1314188/+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 1320498] Re: Using BT Headset (a2dp) is not possible: Bluetooth: re-auth of legacy device is not possible.
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: New => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/1320498 Title: Using BT Headset (a2dp) is not possible: Bluetooth: re-auth of legacy device is not possible. Status in bluez package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: In Ubuntu 14.04/trusty the use of my BT headset (an old Motorola HT 820) is not possible any more. Pairing is successful, however I always find the following in /var/log/syslog when I trying to connect to the A2DP service: May 17 16:09:58 silberfisch2 kernel: [25385.859723] input: 00:07:A4:B5:F1:5E as /devices/virtual/input/input22 May 17 16:12:18 silberfisch2 kernel: [25526.017139] Bluetooth: re-auth of legacy device is not possible. This is a regression i.r.t. older version of Ubuntu, for example I *was* able to use the device with Ubuntu 13.10/saucy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1320498/+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 1410779] Re: Bluetooth adapter is not working in Ubuntu 14.04
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1410779 Title: Bluetooth adapter is not working in Ubuntu 14.04 Status in bluez package in Ubuntu: Won't Fix Bug description: Bluetooth is not working on Ubuntu 14.04 in a Lenovo t430s is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 13:37:16 2015 InstallationDate: Installed on 2014-08-29 (137 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: btusb bnep rfcomm bluetooth MachineType: LENOVO 23554M2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 23554M2 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET96WW(2.56):bd09/12/2013:svnLENOVO:pn23554M2:pvrThinkPadT430s:rvnLENOVO:rn23554M2:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23554M2 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO hciconfig: mtime.conffile..etc.init.bluetooth.conf: 2015-01-02T13:44:45.063731 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1410779/+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 1372265] Re: [packaging] /etc/bluetooth/*.conf appears during unpacking but disappeared after package installed
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1372265 Title: [packaging] /etc/bluetooth/*.conf appears during unpacking but disappeared after package installed Status in bluez package in Ubuntu: Won't Fix Bug description: Hi, I found that bluez config files under /etc/bluetooth were gone and tried to reinstall them using # apt-get install --reinstall bluez ; , then I noticed that those files appeared (as *.conf.dpkg-new) during package unpacking state but disappeared again after the package was installed. I suspected that there's issue in the package install/postinstall script. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-13.19-lowlatency 3.16.1 Uname: Linux 3.16.0-13-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Mon Sep 22 13:40:15 2014 InstallationDate: Installed on 2013-03-08 (562 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) InterestingModules: rfcomm btusb bnep bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-lowlatency root=UUID=a2700cc1-7ea8-4572-ae5e-f364ee6cb619 ro crashkernel=384M-2G:64M,2G-:128M splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-04-19 (156 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M 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.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:48439842 acl:151 sco:949426 events:2090 errors:0 TX bytes:49081906 acl:2290 sco:949394 commands:83 errors:0 rfkill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1372265/+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 1382128] Re: No bluetooth interfaces after suspend
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1382128 Title: No bluetooth interfaces after suspend Status in bluez package in Ubuntu: Won't Fix Bug description: sudo killall bluetoothd helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 16 18:58:03 2014 InstallationDate: Installed on 2014-08-14 (62 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1018P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=UUID=abb4e533-fc94-4834-83ed-0920535dd8ad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1018P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd01/03/2011:svnASUSTeKComputerINC.:pn1018P:pvrx.x:rvnASUSTeKComputerINC.:rn1018P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1018P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:F0:6D:AB:B8:6D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:913753 acl:1548 sco:0 events:858 errors:0 TX bytes:14 acl:811 sco:0 commands:402 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382128/+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 1366854] Re: bluetooth will not enable stays blocked
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. 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: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1366854 Title: bluetooth will not enable stays blocked Status in bluez package in Ubuntu: Won't Fix Bug description: Since installation of 14.04.1 I've been trying to get bluetooth working. Under preferences bluetooth says it's disabled. So I did $rfkill list all, and that showed me that asus bluetooth is soft blocked. I did an $rfkill unblock all, and nothing. I have tried everything listed here: http://askubuntu.com/questions/521190 /bluetooth-disabled-asus-g750jm and the person answering my questions suggested I report it as a bug because I'm out of options. I'm running a ROG ASUS G750JM it's a fairly new gaming laptop, the modem installation went fine through the install process of ubuntu. But bluetooth hasn't worked yet. I'm not sure what package it is it's probably bluez and it's up to date. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-09-06 (9 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: rfcomm bnep bluetooth MachineType: ASUSTeK COMPUTER INC. G750JM NonfreeKernelModules: wl Package: bluez 4.101-0ubuntu13 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=d4bccb16-54c7-4324-a7b8-7ed0f79c9183 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Tags: trusty third-party-packages Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JM.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JM.207:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G750JM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366854/+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 1402359] Re: Can't pair bluetooth device with hardcoded pin
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1402359 Title: Can't pair bluetooth device with hardcoded pin Status in bluez package in Ubuntu: Won't Fix Bug description: I try to pair my device with hardcoded pin "". I'm using default applet near clock (command bluetooth-wizard ?!). It show my device on list. I chose it and select "Pin options..." there select pin '', click close and continue. After that new wizard page appear with some random pin to put inside device and after few second an error appear with message "Setting up 'device' failed". It seems that wizard always send random pin to device... Of course when I use "blueman-manager" to pair that device, everything is working fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 14 11:01:00 2014 InstallationDate: Installed on 2013-07-12 (519 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: btusb rfcomm bnep bluetooth MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=165a27c3-afe4-4674-a311-3512b7accea5 ro plymouth:debug splash quiet drm.debug=0xe SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-05-20 (207 days ago) dmi.bios.date: 05/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd05/07/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:1A:7D:0A:BB:E0 ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN RX bytes:33555 acl:30 sco:0 events:2329 errors:0 TX bytes:7412 acl:27 sco:0 commands:1069 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1402359/+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 1366951] Re: Bluetooth doesn't work on Gigabyte f2a88xn motherboard
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1366951 Title: Bluetooth doesn't work on Gigabyte f2a88xn motherboard Status in bluez package in Ubuntu: Won't Fix Bug description: Bluetooth doesn't work properly on Gigabyte F2A88XN motherboard. The adapter is not always detected. When it's not, sometimes booting into Windows, then on Ubuntu again, makes it work. When it's detected, BT peripherals are regularly working (detection, connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 8 21:32:54 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (3 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=f64a76a3-71a1-4ce4-9934-626170049b70 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366951/+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 1377632] Re: No A2DP streaming to ECC speaker
** Changed in: bluez (Ubuntu) Status: New => Fix Released -- 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/1377632 Title: No A2DP streaming to ECC speaker Status in bluez package in Ubuntu: Fix Released Bug description: DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" Compaq 2510p, amd64 ECC Bluetooth Speaker EC-HTT2.1 This have a reference to an old question, where an existing one time solutions was listed. http://askubuntu.com/questions/470929/problems-connecting-to- bluetooth-headset-14-04 Howto run into the bug: Pair the speaker with bluetooth icon in the panel, this works well and in pulse appear a speaker that only supports HFP / HFS telephony. In pulse this speaker as HFS will not receive any sound, everything comes out of the laptop internal speakers. One time solution: No i apply the idea from the question above. - pactl list cards short 0 alsa_card.pci-_00_1b.0 module-alsa-card.c 2 bluez_card.00_58_50_1C_C9_73module-bluetooth-device. pactl set-card-profile bluez_card.00_58_50_1C_C9_73 a2dp - Now the speaker get a A2DP function under pulse audio selection and turn the music on. BUT this will not survive a disconnect, reboot or shutdown. So we have a bug here, how to make this permanent? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 15:40:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Compaq 2510p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=e6b33549-9e98-4433-8e36-523a97219a43 ro quiet splash elevator=deadline vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.30 dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.asset.tag: 8CZC84618S2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.30:bd11/11/2011:svnHewlett-Packard:pnHPCompaq2510p:pvrF.30:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 2510p dmi.product.version: F.30 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:21:86:AF:0C:35 ACL MTU: 1017:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:74868 acl:109 sco:0 events:10068 errors:0 TX bytes:18878268 acl:19655 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1377632/+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 1366854] Re: bluetooth will not enable stays blocked
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm -- 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/1366854 Title: bluetooth will not enable stays blocked Status in bluez package in Ubuntu: Won't Fix Bug description: Since installation of 14.04.1 I've been trying to get bluetooth working. Under preferences bluetooth says it's disabled. So I did $rfkill list all, and that showed me that asus bluetooth is soft blocked. I did an $rfkill unblock all, and nothing. I have tried everything listed here: http://askubuntu.com/questions/521190 /bluetooth-disabled-asus-g750jm and the person answering my questions suggested I report it as a bug because I'm out of options. I'm running a ROG ASUS G750JM it's a fairly new gaming laptop, the modem installation went fine through the install process of ubuntu. But bluetooth hasn't worked yet. I'm not sure what package it is it's probably bluez and it's up to date. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-09-06 (9 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: rfcomm bnep bluetooth MachineType: ASUSTeK COMPUTER INC. G750JM NonfreeKernelModules: wl Package: bluez 4.101-0ubuntu13 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=d4bccb16-54c7-4324-a7b8-7ed0f79c9183 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Tags: trusty third-party-packages Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JM.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JM.207:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G750JM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366854/+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 1416659] Re: Ubuntu can't detect bluetooth device of Lenovo s400u
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1416659 Title: Ubuntu can't detect bluetooth device of Lenovo s400u Status in bluez package in Ubuntu: Won't Fix Bug description: As reported in this question: https://answers.launchpad.net/ubuntu/+question/250942, Ubuntu 14.04.1 LTS with kernel 3.18.4-031804-generic can't detect bluetooth device of Lenovo s400u. root@galindro-nb:~# lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 root@galindro-nb:~# dmesg | grep Blue [ 17.753263] Bluetooth: Core ver 2.19 [ 17.753288] Bluetooth: HCI device and connection manager initialized [ 17.753296] Bluetooth: HCI socket layer initialized [ 17.753300] Bluetooth: L2CAP socket layer initialized [ 17.753308] Bluetooth: SCO socket layer initialized [ 17.761037] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 17.761042] Bluetooth: BNEP filters: protocol multicast [ 17.761051] Bluetooth: BNEP socket layer initialized [ 17.788967] Bluetooth: RFCOMM TTY layer initialized [ 17.788980] Bluetooth: RFCOMM socket layer initialized [ 17.788986] Bluetooth: RFCOMM ver 1.11 root@galindro-nb:~# hcitool scan Device is not available: No such device root@galindro-nb:/tmp# hcitool dev Devices: *** IMPORTANT thing about lsusb.log attached file *** The device displayed in this line: Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth , isn't the ultrabook built-in bluetooth. It is a Microsoft wireless mouse that has a micro usb bluetooth adaptor. This hardware is working very well. The problem is with Lenovo S400U built-in bluetooth that isn't reconized by Ubuntu 14.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 Uname: Linux 3.18.4-031804-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Jan 31 10:05:28 2015 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-06-29 (215 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterestingModules: rfcomm bnep bluetooth MachineType: LENOVO VIUS3 ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.4-031804-generic root=UUID=56329ea0-54a8-4c9e-baf2-e8b2980b224d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6DCN92WW(V8.06) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S400U dmi.modalias: dmi:bvnLENOVO:bvr6DCN92WW(V8.06):bd02/21/2013:svnLENOVO:pnVIUS3:pvrLenovoIdeaPadS400U:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadS400U: dmi.product.name: VIUS3 dmi.product.version: Lenovo IdeaPad S400U dmi.sys.vendor: LENOVO hciconfig: syslog: <30>1 2015-01-31T10:02:56.875155-02:00 galindro-nb bluetoothd 3934 - - Bluetooth daemon 4.101 <27>1 2015-01-31T10:02:56.876598-02:00 galindro-nb bluetoothd 3934 - - Unable to get on D-Bus <30>1 2015-01-31T10:04:58.601387-02:00 galindro-nb bluetoothd 3990 - - Bluetooth daemon 4.101 <27>1 2015-01-31T10:04:58.602835-02:00 galindro-nb bluetoothd 3990 - - Unable to get on D-Bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1416659/+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 1426228] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [reload: Unknown instance: invo
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1426228 Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [reload: Unknown instance: invoke-rc.d: initscript dbus, action "force-reload" failed.] Status in bluez package in Ubuntu: Won't Fix Bug description: Balnk screen on start up, so I went to the fails safe boot followed by fixing broken packages option, and this is the message resulting. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13.1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Fri Feb 27 18:09:53 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-05 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) InterestingModules: bnep rfcomm btusb bluetooth MachineType: TOSHIBA Satellite PRO C660 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=70e0e896-ab94-42e6-83d0-ff70ceeba57c ro recovery nomodeset SourcePackage: bluez Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-09-06 (173 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.00 dmi.board.asset.tag: NULL dmi.board.name: PWWHA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.00:bd03/18/2011:svnTOSHIBA:pnSatellitePROC660:pvrPSC1RA-003001:rvnTOSHIBA:rnPWWHA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite PRO C660 dmi.product.version: PSC1RA-003001 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 68:A3:C4:88:85:33 ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN RX bytes:1064 acl:0 sco:0 events:55 errors:0 TX bytes:1427 acl:0 sco:0 commands:53 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1426228/+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 1637802] Re: ubuntu 14.04 problem between airplane mode and bluetooth
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1637802 Title: ubuntu 14.04 problem between airplane mode and bluetooth Status in bluez package in Ubuntu: Won't Fix Bug description: is very strange because sometime is working but most of the time the bluetooth icon is absent and even if you go in System Settings you can not switch on bluetooth than if you start to play with airplane mode switch and bluetooth switch some time bluetooth comes a life for sometime than it stop for good, anyway to me becomes evident that there is a relation between airplane mode and bluetooth, be so nice finding a solution if posible --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-05-30 (153 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20235 Package: bluez 4.101-0ubuntu13.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c89a3965-eb84-4899-abe5-01cf184b6981 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Tags: trusty Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN16WW(V1.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400 dmi.modalias: dmi:bvnLENOVO:bvr78CN16WW(V1.04):bd04/17/2013:svnLENOVO:pn20235:pvrLenovoG400:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG400: dmi.product.name: 20235 dmi.product.version: Lenovo G400 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1637802/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
** Tags removed: artful saucy -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
In privacy settings, it says I am enabling "Send error reports to Canonical... Send report *automatically*". This does not have anything to do with NON-automatic error reporting. This worked before, what changed? -- 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/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
I think this probably should be reworded: [Regression Potential] No, ... -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1830503] Re: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1830503 Title: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1830503/+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 1837888] Re: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1
Moving this bug to the kernel as investigation discovered a kernel regression in overmounting protection behavior in 5.3 rc1. So not a LXC bug but a kernel one. ** Package changed: lxc (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837888 Title: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1 Status in linux package in Ubuntu: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837888/+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 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Changed in: nginx (Ubuntu Bionic) Status: Incomplete => Invalid ** Changed in: nginx (Ubuntu) Status: Incomplete => Invalid ** Changed in: openssl (Ubuntu Bionic) Status: New => Fix Released ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in nginx source package in Bionic: Invalid Status in openssl source package in Bionic: Fix Released Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1164016] Re: restore type-ahead find
This change has made the system effectively inappropriate for use in a business situation where mistakes are to be avoided. In the old system, searching within a folder for a file to send to a client would only list files from that folder. Now, file-open and so on show me files from ANYWHERE ON THE SYSTEM FOR ANY CLIENT WHATSOEVER, leaving the user a single mis-click away from a GDPR violation. Choosing a folder should set a boundary on the files displayed. If I want search, I'll search. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
Looks like the update to 1.1.1-1ubuntu2.1~18.04.4 resolved the issue! The listed failing tests above are now passing. I don't see a way I can close out an issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: Incomplete Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1828102] Re: Regression in ModemManager
@till-kamppeter are you able to verify this for disco? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: Fix Committed Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1833671] Re: bond interfaces stop working after restart of systemd-networkd
I've just updated the two machines where I was seeing this to 237-3ubuntu10.25 and in both cases the update was successful and managed to complete without disconnecting the network. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network] Address=1.2.3.4/32 restart networkd, or reboot, and verify the bond is up: root@lp1833671:~# ip a 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff inet 1.2.3.4/32 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::4030:62ff:fecc:362b/64 scope link valid_lft forever preferred_lft forever restart networkd and check /var/log/syslog: root@lp1833671:~# systemctl restart systemd-networkd root@lp1833671:~# cat /var/log/syslog ... Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier [regression potential] this changes how bond slaves are managed, so regressions could affect any configurations using bonding. [other info] the patch is already included in d, and ifupdown manages networking in x, so this is needed only for b. [original description] Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833671/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
Hello Ken, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
Hello Balint, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Committed Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+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 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
Hello Balint, or anyone else affected, Accepted ubuntu-meta into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.417.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Committed Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+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 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent f
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Hello jowfdoijdfdwfwdf, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, a
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
Hello Tom, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network] Address=1.2.3.4/32 restart networkd, or reboot, and verify the bond is up: root@lp1833671:~# ip a 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff inet 1.2.3.4/32 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::4030:62ff:fecc:362b/64 scope link valid_lft forever preferred_lft forever restart networkd and check /var/log/syslog: root@lp1833671:~# systemctl restart systemd-networkd root@lp1833671:~# cat /var/log/syslog ... Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier [regression potential] this changes how bond slaves are managed, so regressions could affect any configurations using bonding. [other info] the patch is already included in d, and ifupdown manages networking in x, so this is needed only for b. [original description] Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for int
[Touch-packages] [Bug 1837937] Re: CRASH
?? Im lost -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+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 1837944] Re: systemd-journal failed to write entry read only mode
*** This bug is a duplicate of bug 1837937 *** https://bugs.launchpad.net/bugs/1837937 ** This bug has been marked a duplicate of bug 1837937 CRASH -- 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/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+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 1837937] Re: CRASH
The version installed on your system is: "linux-image-5.2.0-9-generic 5.2.0-9.10" and this version is not yet released. ** Attachment added: "linux.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+attachment/5279290/+files/linux.png -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+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 1837944] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+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 1837937] Re: CRASH
no and its greyed out... ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+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 1837944] [NEW] systemd-journal failed to write entry read only mode
Public bug reported: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+subscriptions -- Mailing list: https://launch
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
This bug was fixed in the package ubuntu-meta - 1.417.2 --- ubuntu-meta (1.417.2) bionic; urgency=medium * Added xdg-desktop-portal-gtk to desktop-recommends (LP: #1795959) -- Ken VanDine Tue, 09 Jul 2019 13:11:04 -0400 ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1795959] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1837938] [NEW] Incorrect: "python3 /usr/lib/software-properties/software-properties-dbus"
Public bug reported: Incorrect: root 13608 1 0 09:29 ?00:00:00 python3 /usr/lib/software-properties/software-properties-dbus YES: root 13608 1 0 09:29 ?00:00:00 /usr/bin/python3 /usr/lib/software-properties/software-properties-dbus ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-common 0.98.5 Uname: Linux 5.2.2-050202-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:25 2019 InstallationDate: Installed on 2018-12-02 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1837938 Title: Incorrect: "python3 /usr/lib/software-properties/software-properties- dbus" Status in software-properties package in Ubuntu: New Bug description: Incorrect: root 13608 1 0 09:29 ?00:00:00 python3 /usr/lib/software-properties/software-properties-dbus YES: root 13608 1 0 09:29 ?00:00:00 /usr/bin/python3 /usr/lib/software-properties/software-properties-dbus ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-common 0.98.5 Uname: Linux 5.2.2-050202-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:25 2019 InstallationDate: Installed on 2018-12-02 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1837938/+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 1837926] [NEW] snapd snap ftbfs in eoan due to python-apt regression
Public bug reported: snapd snap FTBFS in launchpad snap build due to python-apt regression in eoan https://launchpad.net/~xnox/+snap/snapd/+build/626157 ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: core20 rls-ee-incoming ** Tags added: core20 ** Tags added: rls-ee-incoming ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1837926 Title: snapd snap ftbfs in eoan due to python-apt regression Status in python-apt package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: snapd snap FTBFS in launchpad snap build due to python-apt regression in eoan https://launchpad.net/~xnox/+snap/snapd/+build/626157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1837926/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
I have accepted this to disco-proposed conditionally without the fix landing in eoan yet as per the ongoing 242 systemd merge, mostly because the proposed changes are already merged and accepted upstream. But to make sure eoan is not left without this fix, please be sure to push the changes to eoan-proposed as soon as the systemd merge is done, uploaded and migrated. If possible, I'd prefer not releasing these out of -proposed without the eoan counterparts at least present in eoan-proposed. Thank you! -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Hello jowfdoijdfdwfwdf, or anyone else affected, Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to E
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello Dan, or anyone else affected, Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traf
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
I have accepted this to disco-proposed conditionally without the fix landing in eoan yet as per the ongoing 242 systemd merge, mostly because the proposed changes are already merged and accepted upstream. But to make sure eoan is not left without this fix, please be sure to push the changes to eoan-proposed as soon as the systemd merge is done, uploaded and migrated. If possible, I'd prefer not releasing these out of -proposed without the eoan counterparts at least present in eoan-proposed. Thank you! -- 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/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast majority of systems. And any systems that do add static address(es) would usually be able to route through a gateway from either the dhcp-provided, or static, address. So the regression potential for this change should be low. [o
[Touch-packages] [Bug 1837894] Re: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
We've also seen regressions with lxc which atm appear to be related to a regression in mounting sysfs in containers which use user namespaces (bug 1837888 for reference, though there's no activity on the bug as of yet, just some irc discussion about the regression). -- 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/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+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 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Changed in: nginx (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: Incomplete Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1837894] Re: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
boot-and-services failed because: Jul 24 13:09:02 autopkgtest systemd[1]: Starting Container c1... Jul 24 13:09:02 autopkgtest systemd-nspawn[891]: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted Jul 24 13:09:02 autopkgtest systemd-nspawn[891]: Failed to add new veth interfaces (ve-c1:host0): No such process Jul 24 13:09:02 autopkgtest systemd[1]: systemd-nspawn@c1.service: Main process exited, code=exited, status=1/FAILURE Jul 24 13:09:02 autopkgtest systemd[1]: systemd-nspawn@c1.service: Failed with result 'exit-code'. Jul 24 13:09:02 autopkgtest systemd[1]: Failed to start Container c1. as did upstream TEST-01: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted and upstream TEST-24: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted those seem to be the problem on all arch failure logs. -- 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/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+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 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nginx (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: New Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1837914] [NEW] restart systemd-jounald fails
Public bug reported: While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal/journal- file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: journal xenial -- 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/1837914 Title: restart systemd-jounald fails Status in systemd package in Ubuntu: New Bug description: While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837914/+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 1833758] Re: lvm2: vgcfgbackup in postinst takes several minutes
** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1833758 Title: lvm2: vgcfgbackup in postinst takes several minutes Status in lvm2 package in Ubuntu: New Bug description: The postinst for lvm2 includes a call to vgcfgbackup; in the version included in eoan 2.03.02-2ubuntu4 (and 2.03.02-2ubuntu3 before it), this command takes several minutes to run when invoked in an schroot as happens when a building a package with sbuild that ends up pulling lvm2 as part of its build dependency chain. An example package with lvm2 in its build depends is rsnapshot, but this behavior was seen with a build of glibc. Some notes: - this behavior is NOT seen with the version of lvm2 in disco. - this happens in bionic with a 4.15 kernel and disco with a 5.0 kernel (different hosts, so different sets of block devices) - this happens regardless of whether the host is currently using logical volumes or not Here's the time difference between running the disco version and the eoan version: (disco-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Failed to connect to lvmetad. Falling back to device scanning. real0m0.204s user0m0.014s sys 0m0.010s (eoan-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Device /dev/sda not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. real4m11.405s user0m0.470s sys 0m0.576s /proc/mounts in the schroot: (eoan-amd64)root@HOSTNAME:~# cat /proc/mounts eoan-amd64 / overlay rw,relatime,lowerdir=/var/lib/schroot/union/underlay/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34,upperdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/upper,workdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/work 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10197712k,nr_inodes=2549428,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/sda2 /home ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda2 /tmp ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /run/shm tmpfs rw,rel
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-with-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279222/+files/log-network-manager-with-segmentation.txt -- 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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-without-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279221/+files/log-network-manager-without-segmentation.txt -- 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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Jean, thank you for the input, could you retest these two cases (with and without split connection) but create debug logs of Network Manager and systemd-resolved, following the instructions on https://wiki.ubuntu.com/DebuggingNetworkManager (and/or of my comment #10)? -- 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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This bug report expired because 17.04 is not supported anymore. Did anyone recreate a corresponding bug report for a more recent version of Ubuntu? If so, can you please publish the link so we can subscribe to it? -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Won't Fix Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1837888] [NEW] lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837888 Title: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1837888/+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 1837894] [NEW] systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+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 1837443] Re: [Power9][Witherspoon dd2.3] unable to set hwclock
I believe /sbin/hwclock is the default tool for manually setting the hwclock in Linux. I’m nervous that higher level workloads may depend on the correct functioning of the /sbin/hwclock tool for their successful operation. The /sbin/hwclock tool is shipped with the util-linux package. Adding util-linux as impacted and assigning to Foundations team to comment on whether the /sbin/hwclock tool not operating on witherspoon is a serious issue or not. ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: bugproxy (bugproxy) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1837443 Title: [Power9][Witherspoon dd2.3] unable to set hwclock Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: New Bug description: On the upgraded witherspoon Power9 system we are unable to set hwclock. ubuntu@bobone:~$ uname -a Linux bobone 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:31:42 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ cat /etc/issue Ubuntu 19.04 \n \l ubuntu@bobone:~$ date Mon Jul 22 18:25:04 UTC 2019 ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock 2019-07-22 18:25:26.799805+00:00 ubuntu@bobone:~$ ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock --verbose hwclock from util-linux 2.33.1 System Time: 1563820048.938797 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1101096600 seconds after 1969 Last calibration done at 1101096600 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/07/22 18:27:29 Hw clock time : 2019/07/22 18:27:29 = 1563820049 seconds since 1969 Time since last adjustment is 462723449 seconds Calculated Hardware Clock drift is 0.00 seconds 2019-07-22 18:27:28.877732+00:00 ubuntu@bobone:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1837443/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
My systemd is newer (237-3ubuntu10.24), instead network manager is locked at 1.10.6 (1.10.6-2ubuntu1.1). I've upgraded network-manager as suggested to 1.10.14-0ubuntu2 and rebooted. I've shut down both my Wifi and LAN since I'm at the office, and hooked up my phone with USB tethering to use an external connection and use the VPN to my office. First test: it works. I get my DNS from the VPN: Link 61 (tun2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.27.0.42 172.27.0.33 DNS Domain: ~. Following the test case in #1754671: when I enable the split connection, this is the full result of systemd-resolve --status, where I do not see any DNS coming from the VPN: Global DNS Domain: mycompany.com DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 48 (tun1) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 43 (tun0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 42 (enp0s20f0u2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.42.129 DNS Domain: ~. Link 11 (br-b2c3b7f9b208) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 10 (br-775248335fa8) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 9 (br-6671ba352ece) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 8 (br-642ed19f0ac7) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 7 (br-5699f03e12bc) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 6 (br-1f97d7363f0e) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 5 (docker0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (br-dbf7ef8f9ab9) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enx106530b07160) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- 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 : http