[Touch-packages] [Bug 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
KUbuntu 19.10 -- 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 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
A very old report. Yes, it is fixed! -- 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 1740766] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat
*** This bug is a duplicate of bug 545790 *** https://bugs.launchpad.net/bugs/545790 Public bug reported: the error appears after rebooting from upgrade from 16.04.3 to 16.04.4 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Jan 1 17:59:15 2018 ErrorMessage: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat InstallationDate: Installed on 2018-01-01 (0 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1740766 Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat Status in dpkg package in Ubuntu: New Bug description: the error appears after rebooting from upgrade from 16.04.3 to 16.04.4 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Jan 1 17:59:15 2018 ErrorMessage: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat InstallationDate: Installed on 2018-01-01 (0 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: el paquet libssl1.0.0:amd64 ja està instal·lat i configurat UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1740766/+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 543767] Re: ssh logins doesn't show the MOTD when connecting with public key authorisation
I am also curious to understand why MOTD is being controlled by UsePAM Yes and not just PrintMotd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/543767 Title: ssh logins doesn't show the MOTD when connecting with public key authorisation Status in Ubuntu Server papercuts: Incomplete Status in openssh package in Ubuntu: Expired Bug description: This is merely a minor annoyance, but nonetheless worth a bug report for the servers papercut team: The method to display a MOTD described in the official Ubuntu server guide, chapter 22 (https://help.ubuntu.com/9.10/serverguide/C/update- motd.html) doesn't work as soon as you connect with public key authorisation. Connecting /w password only shows the MOTD correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/543767/+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 1447160] Re: lxc-create template does not include /etc/hosts hostname resolution
Sorry Serge, I didn't see the first reply. I made a mistake pasting the (4), the four was missing the 127.0.1.1 hostname -- 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/1447160 Title: lxc-create template does not include /etc/hosts hostname resolution Status in lxc package in Ubuntu: Incomplete Bug description: 1) Ubuntu 14.04 creating an Ubuntu 12.04 lxc container. 2) Version: 1.0.7-0ubuntu0.1 3) /etc/hosts should have been: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname 4) /etc/hosts was: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname According to http://www.debian.org/doc/manuals/debian- reference/ch05.en.html#_the_hostname_resolution the loopback address to use in this case is 127.0.1.1 and it is what for example maas provisioning does. This would help software that expects the hostname be resolvable work inside lxc containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1447160/+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 1447160] [NEW] lxc-create template does not include /etc/hosts hostname resolution
Public bug reported: 1) Ubuntu 14.04 creating an Ubuntu 12.04 lxc container. 2) Version: 1.0.7-0ubuntu0.1 3) /etc/hosts should have been: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname 4) /etc/hosts was: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname According to http://www.debian.org/doc/manuals/debian- reference/ch05.en.html#_the_hostname_resolution the loopback address to use in this case is 127.0.1.1 and it is what for example maas provisioning does. This would help software that expects the hostname be resolvable work inside lxc containers. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1447160 Title: lxc-create template does not include /etc/hosts hostname resolution Status in lxc package in Ubuntu: Confirmed Bug description: 1) Ubuntu 14.04 creating an Ubuntu 12.04 lxc container. 2) Version: 1.0.7-0ubuntu0.1 3) /etc/hosts should have been: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname 4) /etc/hosts was: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname According to http://www.debian.org/doc/manuals/debian- reference/ch05.en.html#_the_hostname_resolution the loopback address to use in this case is 127.0.1.1 and it is what for example maas provisioning does. This would help software that expects the hostname be resolvable work inside lxc containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1447160/+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 1445580] Re: Impossible to end a call after switching to airplane mode
I agree that the 'flight mode' switch should be somehow disabled during active call, but I would not dismiss completely the need to fix the dialer app. I have no idea how exactly the communication between dialer and modem is organized, but I can imagine some other methods to fall into this bug - like accidentally removing sim card (for example by dropping the phone), or by losing gsm connection. The dialer app should be prepared for such cases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1445580 Title: Impossible to end a call after switching to airplane mode Status in the base for Ubuntu mobile products: Confirmed Status in dialer-app package in Ubuntu: Incomplete Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: In Progress Bug description: As I described here https://lists.launchpad.net/ubuntu-phone/msg12177.html I accidentally switched the phone to the airplane mode while having an active incoming call. As a result it is impossible to end a call - the red button does not end the call. The bug is easy to reproduce: 1. Make a call to your Ubuntu phone and answer it. 2. Switch on 'airplane mode' 3. As a result you get unusable phone. Of course switching gsm off while having an active call is not a typical use of the phone, but still the phone should react to this situation differently. Another thing is that I somehow switched gsm off while holding my phone to my ear (which may suggest some issue with the top panel) - but I don't know how to reproduce this, hence currently I treat this as an very unfortunate accident. Workaround for ending the call: make another incoming call to your phone. BQ (r21) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+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 1442607] Re: I can't connect Bq Ubuntu to Ubuntu Store
Ok, so the bug occurred once again. Now I have exactly the same situation as described in the first post - Ubuntu store doesn't work and all other scopes does work. I think that this time this happened when - I switched on wi-fi (=means internet on my phone since I have gsm data disabled) - I lunched Ubuntu store - but I did it before the connection was really established As requested I attach scope-registry.log. By the way, it would be nice to have same tutorial how to connect Ubuntu phone to Ubuntu desktop and how to use adb. It is kind of strange that you have Ubuntu phone and you connect it to Ubuntu desktop and nothing happens. You need to apply solutions from various places, like http://askubuntu.com/questions/602760/ubuntuphone-does-not-connect-to-ubuntu-desktop http://askubuntu.com/questions/601324/bq-e4-5-adb-fails to get them connected. ** Attachment added: scope-registry.log https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442607/+attachment/4372908/+files/scope-registry.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1442607 Title: I can't connect Bq Ubuntu to Ubuntu Store Status in the base for Ubuntu mobile products: Confirmed Status in unity-scope-click package in Ubuntu: Confirmed Bug description: I had exactly the same issue as described in this thread: https://lists.launchpad.net/ubuntu-phone/msg11847.html In ubuntu store scope I have empty page (just the header 'Ubuntu store' and below a blank page -- see the attached photo). Searching does not change anything - still blank page. The same with refreshing the scope (by pulling the top edge). Other scopes work without problems, and there is no problem with internet connection. I guess that restarting the phone should resolve the issue, but I haven't done this yet. I suspect that the problem occurred when the wi-fi connection was switched on/off - I did it several times (I checked which apps does not work offline) and at some point ubuntu store stopped working. If I can be of some help in debugging the issue please let me know. My phone: BQ Aquaris OS: Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442607/+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
