[Touch-packages] [Bug 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
Raymond, You set status: New → Incomplete but I'm not sure exactly what you need from me or want me to do. I'd love t get this issue fixed for everyone, just tell me what you want. -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
Raymond, Filed a bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=92690 Is there anything else I should add? Thank you so much for your help! ** Bug watch added: freedesktop.org Bugzilla #92690 https://bugs.freedesktop.org/show_bug.cgi?id=92690 -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
attached the result of: # echo autospawn = no >> ~/.config/pulse/client.conf # sudo killall pulseaudio # LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 Is there anything else I can do to help? ** Attachment added: "PulseAudio verbose log" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+attachment/4496238/+files/pulseverbose.log -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
you have to open pulseaudio bug report if pulseaudio dB min is less than -9.99 Is this the problem here: (Analog Input), direction=2, priority=80, probed=yes, supported=yes, has_mute=no, has_volume=yes, has_dB=yes, min_volume=0, max_volume=255, min_dB=-10, max_dB=24 -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: New Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1497666] [NEW] No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
Public bug reported: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 Status in alsa-driver package in Ubuntu: New Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1204579] Re: ufw doesn't support concurrent updates
Is there a current work around for this, otherwise I have to re-write a bunch of code to go to iptables -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1204579 Title: ufw doesn't support concurrent updates Status in ufw: Triaged Status in ufw package in Ubuntu: Triaged Status in ufw package in Debian: New Bug description: On a server under Ubuntu 12.04 I automatically update firewall rules and I unfortunately noticed that if 2 rules are processed at the same time it leads to an inconsistent result between iptables and ufw status. In fact it can be reproduced using the python script in attachment. Before executing this script I didn't have any rules matching the ip 192.168.254.1 on my computer. After a launch iptables takes into acount 464 rules. sudo iptables -L -n | grep 192.168.254.1 | wc -l 464 It should be 500 rules but the script stressed a lot my system and all rules can't be processed by iptables sudo ./test_ufw_threads.py iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. [...] Anyway, ufw stores only the last updates (in /lib/ufw/user.rules): sudo ufw status État : actif Vers Action Depuis -- -- 192.168.254.1 1234/tcp ALLOW 192.168.46.9 192.168.254.1 1234/tcp ALLOW 192.168.22.10 192.168.254.1 1234/tcp ALLOW 192.168.32.10 192.168.254.1 1234/tcp ALLOW 192.168.5.10 192.168.254.1 1234/tcp ALLOW 192.168.43.9 192.168.254.1 1234/tcp ALLOW 192.168.40.10 192.168.254.1 1234/tcp ALLOW 192.168.46.10 192.168.254.1 1234/tcp ALLOW 192.168.48.10 192.168.254.1 1234/tcp ALLOW 192.168.42.10 192.168.254.1 1234/tcp ALLOW 192.168.43.10 So I can't delete other rules using ufw, I had to directly use iptables. In this case I can only delete 10 rules using ufw. Could you please handle some kind of lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1204579/+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 1204579] Re: ufw doesn't support concurrent updates
the flock worked perfectly thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1204579 Title: ufw doesn't support concurrent updates Status in ufw: Triaged Status in ufw package in Ubuntu: Triaged Status in ufw package in Debian: New Bug description: On a server under Ubuntu 12.04 I automatically update firewall rules and I unfortunately noticed that if 2 rules are processed at the same time it leads to an inconsistent result between iptables and ufw status. In fact it can be reproduced using the python script in attachment. Before executing this script I didn't have any rules matching the ip 192.168.254.1 on my computer. After a launch iptables takes into acount 464 rules. sudo iptables -L -n | grep 192.168.254.1 | wc -l 464 It should be 500 rules but the script stressed a lot my system and all rules can't be processed by iptables sudo ./test_ufw_threads.py iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. [...] Anyway, ufw stores only the last updates (in /lib/ufw/user.rules): sudo ufw status État : actif Vers Action Depuis -- -- 192.168.254.1 1234/tcp ALLOW 192.168.46.9 192.168.254.1 1234/tcp ALLOW 192.168.22.10 192.168.254.1 1234/tcp ALLOW 192.168.32.10 192.168.254.1 1234/tcp ALLOW 192.168.5.10 192.168.254.1 1234/tcp ALLOW 192.168.43.9 192.168.254.1 1234/tcp ALLOW 192.168.40.10 192.168.254.1 1234/tcp ALLOW 192.168.46.10 192.168.254.1 1234/tcp ALLOW 192.168.48.10 192.168.254.1 1234/tcp ALLOW 192.168.42.10 192.168.254.1 1234/tcp ALLOW 192.168.43.10 So I can't delete other rules using ufw, I had to directly use iptables. In this case I can only delete 10 rules using ufw. Could you please handle some kind of lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1204579/+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 1646462] Re: lxc container download error (possibly HSTS related)
I have a suspicion that the error is related to the uid/gid mappings. I need several mappings for different containers. It all starts to creep up on any machine configured like so: /etc/subuid root:10:65536 root:33:1 root:100034:65503 root:503:1 root:100504:65033 /etc/subgid root:10:65536 root:33:1 root:100034:65503 root:109:1 root:100110:65427 My hunch is that the download script fails to recognize which mapping it should use for the container filesystem it is extracting onto the disk. -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: Confirmed Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1646462] Re: lxc container download error (possibly HSTS related)
Problem occurs even with the secondary mappings in /etc/lxc/default.conf hashed out: --- lxc.id_map = u 0 10 65536 lxc.id_map = g 0 10 65536 #lxc.id_map = u 0 10 503 #lxc.id_map = u 503 503 1 #lxc.id_map = u 504 100504 65033 #lxc.id_map = g 0 10 109 #lxc.id_map = g 109 109 1 #lxc.id_map = g 110 100110 65427 --- -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: Confirmed Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1646462] Re: lxc container download error (possibly HSTS related)
Problem also occurs with the defaults in /etc/lxc/default.conf. However, the mappings are defined also in /etc/suguid and /etc/subgid, where the mapping also overlap, like so: /etc/subuid -- lxd:10:65536 root:10:65536 root:33:1 root:100034:65503 root:503:1 root:100504:65033 -- /etc/subgid -- lxd:10:65536 root:10:65536 root:33:1 root:100034:65503 root:109:1 root:100110:65427 -- I don't think I should reset those to default while some containers are running. -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: Confirmed Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1405531] Re: encrypted mdadam raid cannot be unlocked with udev 218
I checked out bug 1404143 and can confirm that was the same error I got. I just for some reason on two systems only got it on the RAID and not on the freestanding partiitions. -- 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/1405531 Title: encrypted mdadam raid cannot be unlocked with udev 218 Status in systemd package in Ubuntu: Fix Released Bug description: Running Ubuntu vivid (alpha) with systemd. Bug same in my customized dracut initramfs , Ubuntu's initramfs-tools initramfs, or post boot from the command line. Udev package is udev_218-2ubuntu3_amd64.deb and its related udev packages. Using udev 217 or earlier cryptsetup opens my 3 disk mdadm raid volume at boot along with two cryptsetup volumes on SDD partitions. Using udev 218 the single device encrypted partitions all open fine, but the RAID volume does not, instead generating "could not remove ioctl" errors listing further details "device temporary-cryptsetup-(various numbers)." It would try five times and give up. The RAID itself does comes up, trying to open it from the command line gave me the errors reported above. A Startpage search said this kind of thing normally come from issues with udev rules. The udev rules for mdadm are not included with the udev packages, I am guessing they are in the mdadm packages so they were not changed by this update. Rolling back to udev 217 fixed this and allowed the mdadm raid volume to unlock normally. On this machine reproduction is simple: update to udev 218, make a new initramfs and try to reboot. The "cryptraid" volume hosted on the 3 disk raid will not unlock and cannot be unlocked post boot-not even be removing the hard drives and putting them back in their hotswap trays. Hardware is AMD FX 8120/Radeon HD 6750, motherboard uses FX 990 chipset. The three 2 TB drives are partitioned, the mdadm volume is assembled from the 3 partitions, the cryptsetup volume hosted on it is not partitioned, contains a single large (6TB) ext4 filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1405531/+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 1420601] [NEW] Systemd_218-6ubuntu1 and later cannot connect to network except via USB
Public bug reported: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: networking -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: New Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
Ubuntu version is Vivid (alpha) on all machines, booting systemd by default with upstart removed -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: New Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
I got this result from your commands, more details in the next comment with journalctl lines relevant to this: sudo systemctl status network-pre.target networking.service network.target ifup@eth0.service ● network-pre.target - Network (Pre) Loaded: loaded (/lib/systemd/system/network-pre.target; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─network-pre.conf Active: active (exited) since Wed 2015-02-11 13:26:25 EST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 1214 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) Feb 11 13:26:25 ubuntu networking[1214]: * Configuring network interfaces... Feb 11 13:26:25 ubuntu networking[1214]: /etc/resolvconf/update.d/libc: Warn...f Feb 11 13:26:25 ubuntu networking[1214]: ...done. ● network.target - Network Loaded: loaded (/lib/systemd/system/network.target; static; vendor preset: enabled) Active: active since Wed 2015-02-11 13:26:26 EST; 54s ago Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● ifup@eth0.service - ifup for eth0 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled) Active: inactive (dead) Feb 11 13:27:21 ubuntu systemd[1]: [/lib/systemd/system/ifup@.service:14] T...g. Hint: Some lines were ellipsized, use -l to show in full. luke@ubuntu:~$ sudo systemctl status -l network-pre.target networking.service network.target ifup@eth0.service ● network-pre.target - Network (Pre) Loaded: loaded (/lib/systemd/system/network-pre.target; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─network-pre.conf Active: active (exited) since Wed 2015-02-11 13:26:25 EST; 1min 35s ago Docs: man:systemd-sysv-generator(8) Process: 1214 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) Feb 11 13:26:25 ubuntu networking[1214]: * Configuring network interfaces... Feb 11 13:26:25 ubuntu networking[1214]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Feb 11 13:26:25 ubuntu networking[1214]: ...done. ● network.target - Network Loaded: loaded (/lib/systemd/system/network.target; static; vendor preset: enabled) Active: active since Wed 2015-02-11 13:26:26 EST; 1min 35s ago Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● ifup@eth0.service - ifup for eth0 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled) Active: inactive (dead) Feb 11 13:27:21 ubuntu systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. Feb 11 13:28:01 ubuntu systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. luke@ubuntu:~$ sudo systemctl status network-pre.target networking.service network.target ifup@eth0.service ● network-pre.target - Network (Pre) Loaded: loaded (/lib/systemd/system/network-pre.target; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─network-pre.conf Active: active (exited) since Wed 2015-02-11 13:26:25 EST; 1min 47s ago Docs: man:systemd-sysv-generator(8) Process: 1214 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) Feb 11 13:26:25 ubuntu networking[1214]: * Configuring network interfaces... Feb 11 13:26:25 ubuntu networking[1214]: /etc/resolvconf/update.d/libc: Warning: /etc/res...onf Feb 11 13:26:25 ubuntu networking[1214]: ...done. ● network.target - Network Loaded: loaded (/lib/systemd/system/network.target; static; vendor preset: enabled) Active: active since Wed 2015-02-11 13:26:26 EST; 1min 46s ago Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ● ifup@eth0.service - ifup for eth0 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset
[Touch-packages] [Bug 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
Journalctl lines relevant to this bug, using a PCI connected wifi card that did NOT come up: Feb 11 13:26:26 ubuntu NetworkManager[1378]: (lo): new Generic device (driver: 'unknown' ubuntu NetworkManager[1378]: WiFi hardware radio set enabled Feb 11 13:26:36 ubuntu NetworkManager[1378]: WWAN hardware radio set disabled Feb 11 13:28:13 ubuntu systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. 6 ubuntu ModemManager[1373]: ModemManager (version 1.4.0) starting in sys Feb 11 13:26:26 ubuntu NetworkManager[1378]: NetworkManager (version 0.9.10.0) is starti Feb 11 13:26:26 ubuntu NetworkManager[1378]: Read config: /etc/NetworkManager/NetworkMan Feb 11 13:26:26 ubuntu NetworkManager[1378]: WEXT support is enabled Feb 11 13:26:26 ubuntu kernel: cfg80211: World regulatory domain updated: Feb 11 13:26:26 ubuntu kernel: cfg80211: DFS Master region: unset Feb 11 13:26:26 ubuntu kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ga Feb 11 13:26:26 ubuntu kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2 Feb 11 13:26:26 ubuntu kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2 Feb 11 13:26:26 ubuntu kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2 Feb 11 13:26:26 ubuntu kernel: cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2 Feb 11 13:26:26 ubuntu kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2 Feb 11 13:26:26 ubuntu NetworkManager[1378]: init! Feb 11 13:26:26 ubuntu NetworkManager[1378]: update_system_hostname Feb 11 13:26:26 ubuntu NetworkManager[1378]:interface-parser: parsing file /etc/n Feb 11 13:26:26 ubuntu NetworkManager[1378]:interface-parser: finished parsing fi Feb 11 13:26:26 ubuntu NetworkManager[1378]: management mode: unmanaged Feb 11 13:26:26 ubuntu NetworkManager[1378]: devices added (path: /sys/devices/pci:0 Feb 11 13:26:26 ubuntu NetworkManager[1378]: device added (path: /sys/devices/pci:00 Feb 11 13:26:26 ubuntu NetworkManager[1378]: devices added (path: /sys/devices/virtual/n Feb 11 13:26:26 ubuntu NetworkManager[1378]: device added (path: /sys/devices/virtual/ne Feb 11 13:26:26 ubuntu NetworkManager[1378]: end _init. Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded plugin ifupdown: (C) 2008 Canonical Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded plugin keyfile: (c) 2007 - 2013 Red Feb 11 13:26:26 ubuntu NetworkManager[1378]: (31315200) ... get_connections. Feb 11 13:26:26 ubuntu NetworkManager[1378]: (31315200) ... get_connections (managed=fal Feb 11 13:26:26 ubuntu sshd[1453]: Server listening on 0.0.0.0 port 22. Feb 11 13:26:26 ubuntu sshd[1453]: Server listening on :: port 22. Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: error in connection /etc/NetworkManager Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: new connection /etc/NetworkManager/system-c Feb 11 13:26:26 ubuntu NetworkManager[1378]: get unmanaged devices count: 0 Feb 11 13:26:26 ubuntu NetworkManager[1378]: monitoring kernel firmware directory '/lib/ Feb 11 13:26:26 ubuntu NetworkManager[1378]: monitoring ifupdown state file '/run/networ Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded device plugin: /usr/lib/x86_64-linux Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded device plugin: /usr/lib/x86_64-linux Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded device plugin: /usr/lib/x86_64-linux Feb 11 13:26:26 ubuntu NetworkManager[1378]: Loaded device plugin: /usr/lib/x86_64-linux Feb 11 13:26:26 ubuntu NetworkManager[1378]: WiFi enabled by radio killswitch; enabled b Feb 11 13:26:26 ubuntu NetworkManager[1378]: WWAN enabled by radio killswitch; disabled Feb 11 13:26:26 ubuntu NetworkManager[1378]: WiMAX enabled by radio killswitch; enabled Feb 11 13:26:26 ubuntu NetworkManager[1378]: Networking is enabled by state file Feb 11 13:26:26 ubuntu NetworkManager[1378]: nm_device_get_device_type: assertion 'NM_IS_DEVICE Feb 11 13:26:26 ubuntu NetworkManager[1378]: (lo): link connected Feb 11 13:26:26 ubuntu NetworkManager[1378]: (lo): carrier is ON Feb 11 13:26:26 ubuntu NetworkManager[1378]: (lo): new Generic device (driver: 'unknown' Feb 11 13:26:26 ubuntu NetworkManager[1378]: (lo): exported as /org/freedesktop/NetworkM Feb 11 13:26:26 ubuntu NetworkManager[1378]: nm_device_get_device_type: assertion 'NM_IS_DEVICE Feb 11
[Touch-packages] [Bug 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
2 of 5 (Device Configure) complete. Feb 13 22:38:39 ubuntu NetworkManager[1248]: Config: set interface ap_scan to 1 Feb 13 22:38:39 ubuntu wpa_supplicant[1329]: wlan0: SME: Trying to authenticate with 44:a7:cf:ec:2a:59 (SSID='VirginMobile MiFi2200 A59 Secure' freq=2417 MHz) Feb 13 22:38:39 ubuntu kernel: wlan0: authenticate with 44:a7:cf:ec:2a:59 Feb 13 22:38:39 ubuntu kernel: wlan0: send auth to 44:a7:cf:ec:2a:59 (try 1/3) Feb 13 22:38:39 ubuntu kernel: wlan0: authenticated Feb 13 22:38:39 ubuntu kernel: ath9k :02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use Feb 13 22:38:39 ubuntu kernel: ath9k :02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP Feb 13 22:38:39 ubuntu kernel: ath9k :02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP Feb 13 22:38:39 ubuntu kernel: wlan0: associate with 44:a7:cf:ec:2a:59 (try 1/3) Feb 13 22:38:39 ubuntu wpa_supplicant[1329]: wlan0: Trying to associate with 44:a7:cf:ec:2a:59 (SSID='VirginMobile MiFi2200 A59 Secure' freq=2417 MHz) Feb 13 22:38:39 ubuntu NetworkManager[1248]: (wlan0): supplicant interface state: inactive -> authenticating Feb 13 22:38:39 ubuntu kernel: wlan0: RX AssocResp from 44:a7:cf:ec:2a:59 (capab=0x431 status=0 aid=2) Feb 13 22:38:39 ubuntu kernel: wlan0: associated Feb 13 22:38:39 ubuntu wpa_supplicant[1329]: wlan0: Associated with 44:a7:cf:ec:2a:59 Feb 13 22:38:39 ubuntu NetworkManager[1248]: (wlan0): supplicant interface state: authenticating -> associating Feb 13 22:38:39 ubuntu NetworkManager[1248]: (wlan0): supplicant interface state: associating -> 4-way handshake Feb 13 22:38:39 ubuntu wpa_supplicant[1329]: wlan0: WPA: Key negotiation completed with 44:a7:cf:ec:2a:59 [PTK=TKIP GTK=TKIP] Feb 13 22:38:39 ubuntu wpa_supplicant[1329]: wlan0: CTRL-EVENT-CONNECTED - Connection to 44:a7:cf:ec:2a:59 completed [id=0 id_str=] Feb 13 22:38:39 ubuntu NetworkManager[1248]: (wlan0): supplicant interface state: 4-way handshake -> completed Feb 13 22:38:39 ubuntu NetworkManager[1248]: Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'VirginMobile MiFi2200 A59 Secure'. Feb 13 22:38:39 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Feb 13 22:38:39 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Feb 13 22:38:39 ubuntu NetworkManager[1248]: (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0] Feb 13 22:38:39 ubuntu NetworkManager[1248]: Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Feb 13 22:38:39 ubuntu NetworkManager[1248]: dhclient started with pid 1332 Feb 13 22:38:39 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Feb 13 22:38:40 ubuntu lightdm[1337]: pam_unix(lightdm-autologin:session): session opened for user luke by (uid=0) Feb 13 22:38:40 ubuntu NetworkManager[1248]: (wlan0): DHCPv4 client pid 1332 killed by signal 15 Feb 13 22:38:40 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Feb 13 22:38:40 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started... Feb 13 22:38:40 ubuntu NetworkManager[1248]: Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Feb 13 22:38:40 ubuntu systemd-logind[1263]: New session c1 of user luke. Feb 13 22:38:40 ubuntu systemd[1351]: pam_unix(systemd-user:session): session opened for user luke by (uid=0) Feb 13 22:38:40 ubuntu systemd[1351]: Starting Paths. Feb 13 22:38:40 ubuntu systemd[1351]: Reached target Paths. Feb 13 22:38:40 ubuntu systemd[1351]: Starting Sockets. Feb 13 22:38:40 ubuntu systemd[1351]: Reached target Sockets. Feb 13 22:38:40 ubuntu systemd[1351]: Starting Timers. Feb 13 22:38:40 ubuntu systemd[1351]: Reached target Timers. Feb 13 22:38:40 ubuntu systemd[1351]: Starting Basic System. Feb 13 22:38:40 ubuntu systemd[1351]: Reached target Basic System. Feb 13 22:38:40 ubuntu systemd[1351]: Starting Default. Feb 13 22:38:40 ubuntu systemd[1351]: Reached target Default. Feb 13 22:38:40 ubuntu systemd[1351]: Startup finished in 238ms. Feb 13 22:38:40 ubuntu lightdm[1337]: pam_ck_connector(lightdm-autologin:session): nox11 mode, ignoring PAM_TTY :0 Feb 13 22:38:40 ubuntu avahi-daemon[1249]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::c617:feff:fe72:d252. Feb 13 22:38:40 ubuntu avahi-daemon[1249]: New relevant interface wlan0.IPv6 for mDNS. Feb 13 22:38:40 ubuntu avahi-daemon[1249]: Registering new address record for fe80::c617:feff:fe72:d252 on wlan0.*. Feb 13 22:38:41 ubuntu avahi-daemon[1249]: Withdrawing workstation service for wlan0. Feb 13 22:38:41 ubuntu avahi-daemon[1249]: Withdrawing workstation service for eth0. Feb 13 22:38:41 ubuntu avahi-daemon[1249]: Withdrawing workstation service for lo. F
[Touch-packages] [Bug 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
UPDATE Systemd 8ubuntu2 worked (without the new patch even) on desktop fitted with PCI wifi card, did NOT work on laptop. Laptop seemed to have another issue with the driver (as above). Today's updates to something else seemed to cause that, with current or rolled back systemd. On that laptop, however, manually stopping and restartng NetworkManager allowed a sucessful connection with the rolled back systemd, about to try it with today's patch. -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: Incomplete Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
Laptop results with new file: After several reboots, one time it connected to the wifi automatically, other time it hung on getting the IP address. When hung, running this script would get it connected: sudo killall NetworkManager sudo NetworkManager After running this it connected without issues. No surprise that, as systemd is just an init system. -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: Incomplete Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
The "trailing garbage-ignoring error is gone, still get these errors on the desktop running a PCI wifi card, even though it connected and is working to send this comment: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed also ubuntu NetworkManager[1430]: urfkill disappeared from the bus and Feb 13 23:56:36 ubuntu ModemManager[1419]: Couldn't find support for device at '/sys/devices/pci:00/:00:14.4/:05:06.0': not supported by any plugin Feb 13 23:56:36 ubuntu ModemManager[1419]: Couldn't find support for device at '/sys/devices/pci:00/:00:15.0/:06:00.0': not supported by any plugin -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: Incomplete Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
FIXED wth replacment ifup@.service file used in Systemd 8ubuntu2 in both desktop machines. One uses the onboard ethernet port, the other was tested with a pci wifi card not normally used for performance reasons. Both worked flawlessly with this fix. The laptop may have a driver issue of some kind, wil try a newer kernel in it. It will sometimes connect, sometimes require manually restarting NetworkManager, so I left a script on its desktop for that purpose. Again, both the card in that laptop and the wifi connection I use the most have always been touchy,. When I first used systemd last May I had to start that from rc.local so it occurred to me last night to try that. -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: Incomplete Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+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 1646462] [NEW] lxc container download error
Public bug reported: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1646462 Title: lxc container download error Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1646462] Re: lxc container download error
I should add that existing containers start OK. ** Description changed: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' - root@s28:~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: - dhcp-host=vold,10.0.3.10 - dhcp-host=sftp,10.0.3.11 + dhcp-host=vold,10.0.3.10 + dhcp-host=sftp,10.0.3.11 -- 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/1646462 Title: lxc container download error Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bug
[Touch-packages] [Bug 1646462] Re: lxc container download error
** Description changed: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test - Trying to download the file with wget: + Trying to download the file with wget gets the file OK with minor + complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 ** Summary changed: - lxc container download error + lxc container download error (possibly HSTS related) -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.1
[Touch-packages] [Bug 1646462] Re: lxc container download error (possibly HSTS related)
adding strace for the command: ~# strace lxc-create -t download -n nginx -- --dist ubuntu --release xenial --arch amd64 2>&1 | tee lxc_strace.log ** Attachment added: "strace run" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+attachment/4785765/+files/lxc_strace.log -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1646462] Re: lxc container download error (possibly HSTS related)
The issue seems permanent, for the time being. Running a more thorough strace (attached) has revealed that the download is indeed handled by the /usr/share/lxc/templates/lxc-download binary, which unfortunately refuses to work if invoked directly by shell, so unfortunately I could not debug this particular process any further. ** Attachment added: "process_dump.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+attachment/4786395/+files/process_dump.tar.bz2 -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1646462] Re: lxc container download error (possibly HSTS related)
My mistake, actually it is a shell script. Will look into it. -- 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/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: New Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+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 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me
** Description changed: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 17 16:58:17 2016 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2016-07-16 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: - default via 192.168.2.1 dev enp2s0 proto static metric 100 - 169.254.0.0/16 dev enp2s0 scope link metric 1000 - 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100 + default via 192.168.2.1 dev enp2s0 proto static metric 100 + 169.254.0.0/16 dev enp2s0 scope link metric 1000 + 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH - Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 - BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- + NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH + Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 + BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: - DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH - enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1 - wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- - loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- + DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1 + wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- + loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. -- 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.launchp
[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime
I fixed it by clearing out anything that was added to ~/.local/share/evolution/ when I added my Gmail account to Online Accounts. Through the various debugging methods I was using, it looked like it was an issue with the calendar events. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1366799] Re: enable copying the stacktrace to clipboard or to export details to a file
I also encountered this issue. As a work around, you can unpack the .stack file from var/crash/ with the following command. apport-unpack /var/crash/_usr_lib_.crash ~/ -- 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/1366799 Title: enable copying the stacktrace to clipboard or to export details to a file Status in apport package in Ubuntu: Confirmed Bug description: I am debugging a custom Java application with native code (i.e. a shared library via JNI). Not surprisingly, it crashes somewhere. Apport shows me the stacktrace which is very nice. I would like to be able to right click and copy to clipboard so that I can file a bug with the library in question. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.3 Uname: Linux 3.14.0-031400rc4-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 8 14:57:12 2014 InstallationDate: Installed on 2014-01-22 (228 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-07-01 (69 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2014-01-22T21:16:50.46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1366799/+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 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
Verified fixed with a clean install of Ubuntu 16.10. $ uname -a Linux luke-PowerEdge-T105 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:58:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Raymond, Thank you so much for all your help on this issue! ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Fix Released ** Summary changed: - No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 + No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-16.04 -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-16.04 Status in alsa-driver package in Ubuntu: Fix Released Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1377996] Re: dialer is freezing on active call screen
Thanks Phil @ #22 - that lead me to the DialerApp.conf.lock file which I could rm and problem solved. Had similar issue with Dekko after an update previously - that these lock files need manually clearing sometimes is frustrating. This dialer freeze issue has been annoying me for months. I was swiping R/L, swiping up, tapping to resume the call then using the dialer when it had finally reloaded. Normally 10 seconds into a silent voicemail if I wasn't quick enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-mir in Ubuntu. https://bugs.launchpad.net/bugs/1377996 Title: dialer is freezing on active call screen Status in Canonical System Image: Incomplete Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Incomplete Status in unity-mir package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. phone device (make sure phone app is not running & the device is awake) 2. accept the call from the incoming snap decision 3. wait until active call screen appears 4. navigate back to the keypad 5. tap the now green indicator bar to return back to call 6. tap the tone dial in call controls 7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if you hang up the phone you called from, the screen remains. Sometimes the screen freezes when you try to navigate back and forth from keypad to active call. Try several different ways. A few times, I was able to hang up the phone I was calling from but the active call screen stayed on the device. The only way to make the phone app work again was to force quit it. As an alternative route. Try to call the phone when the phone-app is running. Accept the call and wait until the active call screen appears. Try to interact with the tone dial icon in the call controls. I was able to reproduce the freeze this way as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377996/+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 1600555] [NEW] Postfix Admin depends strictly on pg-client or mysql-client with no option for mariadb-client
Public bug reported: The dependencies on the Postfix Admin package should be updated to require postgresql-client OR mysql-client OR mariadb-client. Currently the package requires either postgresql-client OR mysql-client. As mariadb-client is a drop-in replacement there is no reason to require mysql (also a single system cannot have both mariadb and mysql, use of one precludes use of the other). ** Affects: postfixadmin (Ubuntu) Importance: Undecided Status: New ** Package changed: apt (Ubuntu) => postfixadmin (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1600555 Title: Postfix Admin depends strictly on pg-client or mysql-client with no option for mariadb-client Status in postfixadmin package in Ubuntu: New Bug description: The dependencies on the Postfix Admin package should be updated to require postgresql-client OR mysql-client OR mariadb-client. Currently the package requires either postgresql-client OR mysql-client. As mariadb-client is a drop-in replacement there is no reason to require mysql (also a single system cannot have both mariadb and mysql, use of one precludes use of the other). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfixadmin/+bug/1600555/+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 1527053] Re: Tab names unreadable in GTK3 in Ubuntu
@ Adolfo Jayme Why did you set this to Invalid with no explanation? It is not an issue for Debian or Fedora and may people are reporting this issue with Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1527053 Title: Tab names unreadable in GTK3 in Ubuntu Status in LibreOffice: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. On Ubuntu 15.4 or 15.10, install or build libreoffice 5.1 2. Open a tabbed dialog box such Format->Paragraph Note the text is white on light gray, which is very hard to read. In Fedora or Debian, when you select a "dark" theme, the tabs are rendered as white text on a black background. In Ubuntu other UI elements such as the toolbar and context menus are rendered the same as Debian's dark theme(white text on black). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1527053/+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 1527053]
Doctor Rover, Thank you for your input, but please do not treat the bug tracker like a discussion forum. See https://wiki.documentfoundation.org/QA/BugReport#One_Report.2C_Five_Bugs "One report should only have a single bug in it. Developers are unlikely to take on a bug that has multiple issues listed." Please do not add noise here. If you want to help, file clear concise bug reports and link them with the "See Also". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1527053 Title: Tab names unreadable in GTK3 in Ubuntu Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. On Ubuntu 15.4 or 15.10, install or build libreoffice 5.1 2. Open a tabbed dialog box such Format->Paragraph Note the text is white on light gray, which is very hard to read. In Fedora or Debian, when you select a "dark" theme, the tabs are rendered as white text on a black background. In Ubuntu other UI elements such as the toolbar and context menus are rendered the same as Debian's dark theme(white text on black). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1527053/+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 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
This may also affect libreoffice. See:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1527053
https://bugs.launchpad.net/ubuntu-themes/+bug/1527910
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1478173
Title:
Ambiance & Radiance themes are missing a "background-color" for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in One Hundred Papercuts:
Confirmed
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance & Radiance GTK3 themes.
They're missing a "background-color" for the .tooltip {...} CSS rule
in their config files. They have a "tooltip_bg_color" variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the ".tooltip" CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+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 1527053] Re: Tab names unreadable in GTK3 in Ubuntu
** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Package changed: libreoffice (Ubuntu) => df-libreoffice ** Bug watch added: Document Foundation Bugzilla #92776 https://bugs.documentfoundation.org/show_bug.cgi?id=92776 ** Changed in: df-libreoffice Importance: Undecided => Unknown ** Changed in: df-libreoffice Status: New => Unknown ** Changed in: df-libreoffice Remote watch: None => Document Foundation Bugzilla #92776 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1527053 Title: Tab names unreadable in GTK3 in Ubuntu Status in LibreOffice: Unknown Status in ubuntu-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. On Ubuntu 15.4 or 15.10, install or build libreoffice 5.1 2. Open a tabbed dialog box such Format->Paragraph Note the text is white on light gray, which is very hard to read. In Fedora or Debian, when you select a "dark" theme, the tabs are rendered as white text on a black background. In Ubuntu other UI elements such as the toolbar and context menus are rendered the same as Debian's dark theme(white text on black). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1527053/+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 1537047] [NEW] GTK3: Selected Button Not Visible
Public bug reported: With Ubuntu's GTK+ 3 Theme, the orange dotted line is so thin, it's practically invisible and the red button highlight is missing. This makes it appear that the window is not in focus and you must use the mouse to select the dialog buttons. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: gtk3 ** Attachment added: "Comparison of gtk2 vs gtk3 dialog buttons in libreoffice" https://bugs.launchpad.net/bugs/1537047/+attachment/4554735/+files/DialogBox.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1537047 Title: GTK3: Selected Button Not Visible Status in ubuntu-themes package in Ubuntu: New Bug description: With Ubuntu's GTK+ 3 Theme, the orange dotted line is so thin, it's practically invisible and the red button highlight is missing. This makes it appear that the window is not in focus and you must use the mouse to select the dialog buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1537047/+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 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
I am having the same issue on my Thinkpad T490. Very tinny/high treble audio with no bass. -- 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/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s Status in alsa-driver package in Ubuntu: New Bug description: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
FWIW, I was able to apply bb96fc4295 cleanly to the current 20.04 package (2:3.3.16-1ubuntu2) and it works for me. apt-get -y source procps && cd procps-* curl -fSsL -o debian/patches/sc_arg_max https://gitlab.com/procps-ng/procps/-/commit/bb96fc4295.patch echo sc_arg_max >>debian/patches/series dch --local myorg 'Apply patch: "pgrep: check sanity of SC_ARG_MAX"' debuild -us -uc -G -i -tc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Triaged Status in procps source package in Focal: Confirmed Status in procps source package in Groovy: Confirmed Status in procps source package in Hirsute: Triaged Status in procps package in Debian: New Bug description: If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Until the fix gets pushed to bionic and cosmic, you should able to get
stereo playback using the headphone jack adapter for the headsets that
should be included with them. Cable's a bit short, but it works.
--
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/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1751657] Re: man journalctl gives info about -g option not present in command
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1751657 Title: man journalctl gives info about -g option not present in command Status in systemd package in Ubuntu: Confirmed Bug description: man journalctl documents a --grep option, however: $ journalctl -g a journalctl: invalid option -- 'g' $ journalctl --grep a Compiled without pattern matching support ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Feb 25 21:53:29 2018 InstallationDate: Installed on 2017-06-21 (248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 004: ID 10d7:1102 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash acpi_rev_override=5 pci=noaer vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago) dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751657/+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 1815509] Re: Shutdown hung by firmware update daemon
I have this issue on Ubuntu 18.04 running on late 2009 iMac with Intel Core 2 Duo, 8G RAM. -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1843201] [NEW] Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
Public bug reported: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- 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/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in openssh package in Ubuntu: New Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1843201/+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 1483751] Re: Issues traversing a sftp server when files or folders contain the character "]"
Can confirm: sftp> cd Foo\ \[bar\] sftp> ls hello.txt sftp> get hello.txt File "/home/lfaraone/Foo [bar]/hello.txt" not found. sftp> ** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Triaged -- 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/1483751 Title: Issues traversing a sftp server when files or folders contain the character "]" Status in openssh package in Ubuntu: Triaged Bug description: I am unsure if the bug is with openssh sftp client or within openssh- sftp-server When traversing an sftp server, I encounter issues for files and, in particular, directories containing the character "]". Tab completion does not escape the character in sftp shell, however, in bash it will escape the character for tab completion. If I "cd" into a directory that contains the character I cannot get any files with in that directory and I have to rename the directory outside of the sftp shell to remove the character in order to be able to correctly get files. Ex: sftp> cd Movie\ \[1080p]/ sftp> ls Movie.1080p.mp4 sftp> get Movie.1080p.mp4 File "/home/hitsuji/movies/Movie [1080p]/Movie.1080p.mp4" not found. sftp> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 11 14:36:00 2015 InstallationDate: Installed on 2015-05-01 (101 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1483751/+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 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
Thanks for looking into this, and the pointer. I guess, another option would be to not request shortcut inhibition, unless I'm misunderstanding its value? Unless there's a worry that some other application will be able to steal your password this way — it doesn't seem obviously warranted to me. For example, `ssh-askpass-fullscreen` does not generate this prompt. It isn't clear to me that the fullscreen-ness of this implementation materially changes the risk profile, so either shortcut inhibition isn't useful, or I should file a bug against `ssh-askpass-fullscreen` to either request this privilege or document the gap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in gnome-desktop package in Ubuntu: New Status in openssh package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1843201/+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 1810471] [NEW] Styled-output incorrectly uses double-underline attribute
Public bug reported: Using --styled-output (which is the default running cURL interactive terminal) results in the double-underline text attribute being set incorrectly and remaining on after cURL exits. For example, running this in xfce4-terminal: curl -I google.com Results in double-underlined text starting from the ":" after "Location", and running into the shell prompt after cURL has exited. The intended behaviour of this feature is HTTP header names to be bold, and header values to be normal. While I noticed the problem in xfce4-terminal on Xubuntu, others have reported the issue on other terminal emulators, so I don't think this is specific to xfce4-terminal. Man page for --styled-output doesn't mention setting double underline either: Enables the automatic use of bold font styles when writing HTTP headers to the terminal. Use --no-styled-output to switch them off. Added in 7.61.0. This has already been fixed upstream by using the correct font attribute control code. Upstream cURL bug report: https://github.com/curl/curl/issues/2736 Fixed upstream in: https://github.com/curl/curl/pull/2738 ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Affects: curl (openSUSE) Importance: Medium Status: Fix Released ** Attachment added: "Screenshot of problem" https://bugs.launchpad.net/bugs/1810471/+attachment/5226802/+files/curl-double-underline.png ** Bug watch added: bugzilla.suse.com/ #1105624 https://bugzilla.suse.com/show_bug.cgi?id=1105624 ** Also affects: curl (openSUSE) via https://bugzilla.suse.com/show_bug.cgi?id=1105624 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1810471 Title: Styled-output incorrectly uses double-underline attribute Status in curl package in Ubuntu: New Status in curl package in openSUSE: Fix Released Bug description: Using --styled-output (which is the default running cURL interactive terminal) results in the double-underline text attribute being set incorrectly and remaining on after cURL exits. For example, running this in xfce4-terminal: curl -I google.com Results in double-underlined text starting from the ":" after "Location", and running into the shell prompt after cURL has exited. The intended behaviour of this feature is HTTP header names to be bold, and header values to be normal. While I noticed the problem in xfce4-terminal on Xubuntu, others have reported the issue on other terminal emulators, so I don't think this is specific to xfce4-terminal. Man page for --styled-output doesn't mention setting double underline either: Enables the automatic use of bold font styles when writing HTTP headers to the terminal. Use --no-styled-output to switch them off. Added in 7.61.0. This has already been fixed upstream by using the correct font attribute control code. Upstream cURL bug report: https://github.com/curl/curl/issues/2736 Fixed upstream in: https://github.com/curl/curl/pull/2738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/+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 1767098] [NEW] Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"
Public bug reported: On a fresh installation of Ubuntu 18.04, both DVI outputs on the back of the card function as expected but it is not possible to enable the HDMI output. I can reliably reproduce the issue under both X and Wayland. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:22:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (rev f1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 285/380] [1462:2015] InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V 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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1767098 Title: Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected" Status in xorg package in Ubuntu: New Bug description: On a fresh installation of Ubuntu 18.04, both DVI outputs on the back of the card function as expected but it is not possible to enable the HDMI output. I can reliably reproduce the issue under both X and Wayland. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:22:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (rev f1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 285/380] [1462:2015] InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V 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: C
[Touch-packages] [Bug 1760341] [NEW] Intermittent freeze in display output, XPS 9530 with nouveau
Public bug reported: Display output intermittently pauses for approximately a second, causing the system to appear "stuttery". During freezes mouse input doesn't seem to be registered and keyboard input is repeated, as though keys are being held down. Watching the journal via `journalctl -f`, the following message appears each time the problem occurs: Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 31 20:11:01 2018 DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05fe] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe] InstallationDate: Installed on 2018-01-29 (61 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=58327001-b3e0-4118-a0e6-03e8221a44f2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-31 (0 days ago) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze regression reproducible ubuntu wayland-session -- 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/1760341 Title: Intermittent freeze in display output, XPS 9530 with nouveau Status in xorg package in Ubuntu: New Bug description: Display output intermittently pauses for approximately a second, causing the system to appear "stuttery". During freezes mouse input doesn't seem to be registered and keyboard input is repeated, as though keys are being held down. Watching the journal via `journalctl -f`, the following message appears each time the problem occurs: Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 31 20:11:01 2018 DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05fe] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe] InstallationDate: Installed on 2018-01-29 (61 days ago) Install
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG display, then flashes purple for a second (Grub menu splash before the Ubuntu splash logo, which doesn't display on the laptop, but does on the HDMI display) then goes blank and never comes online. Even pressing CTRL+ALT+F1-6 does not switch between virtual terminals on the laptop display, it does shift on the mirrored HDMI display. The only way to get a display is to hook up a monitor to the HDMI port and then logging in and setting the display to mirror mode. In fact, this is the only way to install Bionic on the device as even booting the install media with nouveau blacklisted doesn't work. In previous releases, running nouveau.modeset=0 would bring up the display properly and then you could install, but with Bionic, this is does not work. Also, installing the Bionic kernel in Xenial or Artful creates the same condition for those releases. I have looked at the logs and settings everywhere, and from what I can tell everything appears to be loading properly. Gnome sees both displays when connected, but the laptop display remains black. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1779240] [NEW] Unable to Remove Trusted Software Providers From Authentication Tab
Public bug reported: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1779240 Title: Unable to Remove Trusted Software Providers From Authentication Tab Status in software-properties package in Ubuntu: New Bug description: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1779240/+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 1656100] Re: Unable to remove signing keys using gnome-software-properties
I can confirm this. Also, specifying the -d flag upon executing this program through a terminal emulator returns no useful debug info to help us. -- 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/1656100 Title: Unable to remove signing keys using gnome-software-properties Status in Ubuntu GNOME: Invalid Status in software-properties package in Ubuntu: Confirmed Bug description: I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am unable to remove signing keys in the Authentication tab. If I select a key I wish to remove and click the Remove button, either nothing will happen, or it will ask me for authentication, upon giving it the correct password all that will happen is it will deselect the key I select, but at no point will it actually remove it, which is rather annoying. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 12 21:35:55 2017 InstallationDate: Installed on 2017-01-09 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1656100/+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 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1719302 Title: Please include mlx4 and mlx5 InfiniBand modules Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: New Bug description: Mellanox ConnectX architecture is: mlx4_core is the lower level PCI driver which register on the PCI id, and protocol specific drivers are depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC could have multiple ports which can change their type dynamically. We use the request_module() call to load the relevant protocol driver when needed: on loading time or at port type change event. The mlx4_core and mlx5_core modules are included in the initrd, but not mlx4_ib and mlx5_ib. Thus the request_module() call will not find these modules and fail load them. The mlx*_ib module loading will not be retried. Therefore also include mlx4_ib and mlx5_ib in the initrd to make autoloading them work. A patch is attached to the related Debian bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
** Also affects: ufw Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: New Status in ufw package in Ubuntu: Confirmed Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 8949] Re: Opening a deleted 'recent document' results in a new file.
I can confirm this issue no longer affects Ubuntu 18.04, as recently viewed items are removed upon deletion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/8949 Title: Opening a deleted 'recent document' results in a new file. Status in GNOME Panel: Invalid Status in GTK+: Won't Fix Status in One Hundred Papercuts: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: http://bugzilla.gnome.org/show_bug.cgi?id=143385 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/8949/+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 1801264] [NEW] Wifi drops out 1-30 minutes after boot on Ubuntu 18.10
Public bug reported: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected/org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1801264 Title: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10 Status in network-manager package in Ubuntu: New Bug description: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected /org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled
[Touch-packages] [Bug 1740484] Re: video corruption with amd RX560 and 2k display
w it's real. Try using an older motherboard like the same as mine with OLDER AMI EFI bios driver version. That EFI version will be right at the top of the dmesg. Details on my motherboard etc are in the original post. Yo [0.00] efi: EFI v2.60 by American Megatrends [0.00] efi: ACPI 2.0=0xd48df000 ACPI=0xd48df000 SMBIOS=0xdb92f000 SMBIOS 3.0=0xdb92e000 ESRT=0xd815b998 [0.00] random: fast init done [0.00] SMBIOS 3.0.0 present. [0.00] DMI: System manufacturer System Product Name/PRIME B350M-A, BIOS 3401 12/04/2017 Finding exactly what is required to replicate this at your end will be useful. Just search amdgpu in the ubuntu bug ticket to see other users who are suffering. https://bugs.launchpad.net/ubuntu?field.searchtext=amdgpu&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package = Cheers, Luke Среда, 24 января 2018, 16:10 +07:00 от MSI OCSS : Ticket: MSI/AMI EFI-ACPI firmware & MSI GPU SBIOS/ATOMBIOS break AMD Power Play in Stable linux - request new firmware builds for me (and others) Content: Hi, Sir, As you know, there are two install file in the AMD lLinux driver package, 'amdgpu-pro-install' and 'amdgpu-install', 'amdgpu-pro-install' is for Radeon Pro GPU which is for use in workstations, and amdgpu-intall is for all other product. And we are endeavoring to reproduce the fan issue with Linux, although we had tried it with Ubuntu, but the fan work fine without any settings. For gather more information, as you said before, did the issue fix while amdgpu.dc=1 enabled? Thanks. ** Bug watch added: freedesktop.org Bugzilla #100443 https://bugs.freedesktop.org/show_bug.cgi?id=100443 -- 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/1740484 Title: video corruption with amd RX560 and 2k display Status in xorg package in Ubuntu: New Bug description: I have a new PC. Freshly installed ubuntu 17.10 I get a lot of video corruption on my 2k display. It usually shows up as bands of the background image or gnome-shell status bar flickering across the display at different vertical positions. Everything works fine if I select 'Gnome under X.Org' from the login screen instead of wayland. GNOME 3.26.2, Linux 4.13, Radeon RX560 using amdgpu, Lenovo l24q-10 monitor running at 2k (2560x1440@ 59.95Hz). There is a Fedora Bug with same info: https://bugzilla.redhat.com/show_bug.cgi?id=1417778 with a video showing the problem in there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 11:06:18 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-21-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Baffin [Radeon RX 560] [1da2:e348] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=2452d0da-14e9-4f88-9660-5a86aee79ff4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.
[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Description changed: - I've found an issue on some of our Xenial office machines, causing - NetworkManager to drop its IP address lease in some cases when it - shouldn't. I'm not sure if the actual bug is in NetworkManager or - perhaps dbus or dhclient, but I'll do my best to help to figure out - where it is. + SRU REQUEST: + + Debdiff (nm-dhcp-helper.debdiff) attached. + + Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug + was fixed upstream in 1.4. + + [Impact] + + * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP + lease renewal due to a DBus race condition. + + * Upstream NetworkManager 1.4 fixes the race condition by changing + nm-dhcp-helper's DBus notification from signal "Event" to method + "Notify". + + * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's + NM 1.2.x. + + [Test Case] + + * Not reliably reproducible. Out of hundreds of machines, only a + dozen or so fail to notify NetworkManager of a DHCP lease + renewal about 30-50% of the time. (i.e. It's always the same + handful of machines that fail.) + + * All such machines with the patched packages have been fine for weeks, + over many dozens of lease renewals. + + [Regression Potential] + + * The patch changes both nm-dhcp-helper and NetworkManager itself. As + soon as the new packages are unpacked, the new nm-dhcp-helper will be + used on DHCP lease renewals, with the new Notify mechanism. Since the + running, old NetworkManager is still expecting Event notifications, the + patched nm-dhcp-helper has fallback capability to Event. + + * Once NetworkManager is restarted and is running the patched version, + it will have the new Notify support. + + [Other Info] + + * Upstream bug w/ patch: + https://bugzilla.gnome.org/show_bug.cgi?id=784636 + + * RHEL bug with links to the 1.4 commits from which the patch was + derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 + + * NOTE: The final comment on the upstream GNOME bug claims that the + fix is incomplete. However, it is possible that the running + NetworkManager was not restarted (see Regression Potential notes above), + which is why nm-dhcp-helper is falling back to Event. The remainder of + the log messages in that final comment are from a custom wrapper the + submitter was running around nm-dhcp-helper. I have deployed the exact + same patch (without said wrapper) to real-world systems and tested + extensively, and see nothing but successful DHCP lease renewal + notifications using D-Bus Notify, not D-Bus Event. + + + + I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** No longer affects: ubuntu ** Changed in: initramfs-tools (Ubuntu) Assignee: omesalim (omesalim) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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
Re: [Touch-packages] [Bug 1516078] Re: pulseaudio fails to load modules
Yeah this has been on my radar since it was filed, wanted/had to upgrade to Xenial first. Will certainly be having a look. -- 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/1516078 Title: pulseaudio fails to load modules Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio 1:7.1-1ubuntu1 in xenial is unable to load some of its modules, more importantly at least the bluez module and the cli module: Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-bluez5-device.so : module-bluez5-device.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open module "module-bluez5-device". Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module-bluez5-discover.c: Failed to load module for device /org/bluez/hci0/dev_30_22_04_06_16_46 Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-cli-protocol-unix.so : module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open module "module-cli-protocol-unix". Nov 13 10:16:11 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-cli-protocol-unix.so : module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Using the version of pulseaudio from wily; things appear to work as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mtrudel 12148 F pulseaudio /dev/snd/pcmC0D0p: mtrudel 12148 F...m pulseaudio /dev/snd/controlC0: mtrudel 12148 F pulseaudio /dev/snd/controlC1: mtrudel 12148 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 11:17:34 2015 InstallationDate: Installed on 2015-03-30 (228 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-M PRO 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.:bvr0603:bd11/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z68-MPRO: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/1516078/+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
Re: [Touch-packages] [Bug 1516078] [NEW] pulseaudio fails to load modules
Hi Mathieu. Doing testing with bluetooth here, and I don't seem to be having a problem. Could you please get a log from PulseAudio as outlined here, https://wiki.ubuntu.com/PulseAudio? Thanks. -- 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/1516078 Title: pulseaudio fails to load modules Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio 1:7.1-1ubuntu1 in xenial is unable to load some of its modules, more importantly at least the bluez module and the cli module: Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-bluez5-device.so : module-bluez5-device.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open module "module-bluez5-device". Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module-bluez5-discover.c: Failed to load module for device /org/bluez/hci0/dev_30_22_04_06_16_46 Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-cli-protocol-unix.so : module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open module "module-cli-protocol-unix". Nov 13 10:16:11 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: Impossible d'ouvrir le module module-cli-protocol-unix.so : module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Using the version of pulseaudio from wily; things appear to work as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mtrudel 12148 F pulseaudio /dev/snd/pcmC0D0p: mtrudel 12148 F...m pulseaudio /dev/snd/controlC0: mtrudel 12148 F pulseaudio /dev/snd/controlC1: mtrudel 12148 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 11:17:34 2015 InstallationDate: Installed on 2015-03-30 (228 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-M PRO 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.:bvr0603:bd11/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z68-MPRO: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/1516078/+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 1453429] Re: Add a new variant to symbols/lk
** Package changed: ubuntu => libxcb (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1453429 Title: Add a new variant to symbols/lk Status in libxcb package in Ubuntu: New Bug description: We have registered a new variant for the X11\kbd\symbols\lk file: https://bugs.freedesktop.org/show_bug.cgi?id=90345 What is the procedure to make that layout variant also available in the upcoming Ubuntu releases? Thank you. JC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1453429/+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 1453452] Re: Cannot unlock lockscreen
*** This bug is a duplicate of bug 1435988 *** https://bugs.launchpad.net/bugs/1435988 ** This bug has been marked a duplicate of bug 1435988 sometime right edge swip stop working on the lockscreen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1453452 Title: Cannot unlock lockscreen Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: This is something I am experiencing more and more. I am unable to unlock the screen. What doesn't work: - Swiping left or right does nothing. Normally the lockscreen would go away and I would see the app I was on previously. - Swiping from the right edge to the left does nothing either. What does work - Opening the top menu or the left menu works, however. - Swiping from the left edge to the right works. This brings me back to the scopes screen. After restart, everything is back to normal. bq phone syslog as attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1453452/+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 1453533] Re: USB sound card not detected
Triaging changes made in accordance with: https://wiki.ubuntu.com/DebuggingSoundProblems ** Tags removed: apport-bug i386 vivid ** Tags added: kernel-sound ** Package changed: alsa-driver (Ubuntu) => linux -- 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/1453533 Title: USB sound card not detected Status in linux package in Ubuntu: New Bug description: 1) Description: Ubuntu 15.04 Release: 15.04 3) Since my internal sound card is not working any longer, I am using a Storite external USB soundcard. It was working perfectly well with Windows, but is giving me problems in Ubuntu 15.04. 4) The USB device is shown in lsusb but the same is not available in sound preferences. I am unable to get sound output into my headphone. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: truman 4558 F pulseaudio CurrentDesktop: Unity Date: Sun May 10 17:00:08 2015 InstallationDate: Installed on 2015-05-09 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/07 dmi.bios.vendor: Lenovo dmi.bios.version: v2.04 dmi.board.name: F50X dmi.board.vendor: Lenovo dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLenovo:bvrv2.04:bd03/16/07:svnLenovo:pnLENOVO3000Y500:pvr:rvnLenovo:rnF50X:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: LENOVO3000 Y500 dmi.product.version: dmi.sys.vendor: Lenovo mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-05-09T23:59:29.657312 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453533/+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 1274613] Re: module-bluetooth-discover does not load on login
The complete set of steps for the workaround are: * In a terminal, run `pactl load-module module-bluetooth-discover` * Right-click on the device in blueman, select "connect to audio sink" * Open Puleseaudio volume control (pavucontrol), browse to "configuration" , use the dropdown to turn the Built-in audio profile "off" * use the other dropdown to set the bluetooth device to use A2DP I think the desirable behavior is you would hit "connect to audio sink" and audio would start flowing through the bluetooth device, and then if you hit disconnect it would start flowing through the default profile again. However, there's an additional bug here, which is that after disconnecting (and manually switching the sink back on,) the default profile seems altered. I'm a little confused by what the underlying configuration change is, but xfce4-volumed can't control the volume of the built-in audio until I kill it and restart it: killall xfce4-volumed xfce4-volumed -- 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 302209] Re: software-properties only adds central Ubuntu repository for security updates (doesn't respect choice of local mirror)
** Changed in: software-properties (Ubuntu) Importance: Low => Wishlist -- 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/302209 Title: software-properties only adds central Ubuntu repository for security updates (doesn't respect choice of local mirror) Status in software-properties package in Ubuntu: Triaged Bug description: Binary package hint: synaptic When we remove than add again the security repository the result in source.list is always http://security and nor the URI of the server ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/sbin/synaptic Package: synaptic 0.62.1ubuntu10 ProcAttrCurrent: unconfined ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: synaptic Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/302209/+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 561479] Re: Windows executable on unwritable removable media cannot execute with Wine due to lack of executable bit
Now this is fixed in mime-support, do we still need to make a change to udisks? If so, what is it? ** Changed in: udisks (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/561479 Title: Windows executable on unwritable removable media cannot execute with Wine due to lack of executable bit Status in One Hundred Papercuts: Triaged Status in udisks: New Status in mime-support package in Ubuntu: Fix Released Status in udisks package in Ubuntu: Incomplete Status in mime-support source package in Lucid: Won't Fix Status in udisks source package in Lucid: Won't Fix Status in mime-support source package in Maverick: Invalid Status in udisks source package in Maverick: Invalid Status in Baltix: New Bug description: I would like to install Far Cry from the DVD on Ubuntu Lucid but I wasn't able to do so because the installation executable was lacking the executable bit. I verified in fstab and there was the exec option on the cdrom line. Furthermore I was able to install Counter Strike from the CDROM (is there a difference between how DVD and CDROM are managed?). I had to umount the DVD and mount it again in an other folder, /usr/cd (/mnt/cd didn't work) to get the install executable work. == Regression details == Discovered in version: lucid Last known good version: karmic, which had no cautious-launcher == Workaround == Install Wine from the Wine Team PPA, which disables the use of cautious-launcher To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/561479/+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 1439313] Re: apt-key del keyid is case sensitive
Fixed in 1.0.9.9ubuntu1 ** Changed in: apt (Ubuntu) Status: Triaged => Fix Released ** Changed in: apt (Ubuntu) Milestone: vivid-updates => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1439313 Title: apt-key del keyid is case sensitive Status in apt package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Bug description: Note: Confirmed on Ubuntu utopic with apt 1.0.9.2ubuntu2 Confirmed on Debian jessie apt 1.0.9.7 Behavior NOT seen on Ubuntu precise with apt 0.8.16~exp12ubuntu10.22 Behavior NOT seen on Debian wheezy apt 0.9.7.9+deb7u7 apt-key export is not case-sensitive to the hex keyid specified. Inconsistently, apt-key del is case-sensitive and won't match unless the hex keyid is uppercase. This is highly exacerbated by bug #1256565 which results in "OK" being printed and success being returned when apt-key del doesn't match anything. The user is reasonably left to conclude that the key has been deleted from the trusted keyring when it has not. Example: # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7fac5991 OK # echo $? 0 # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7FAC5991 OK # echo $? 0 # apt-key export 7fac5991 gpg: WARNING: nothing exported To manage notifications about this bug g
[Touch-packages] [Bug 370795] Re: update-manager is downloading all packages although its configured for security updates only
Thank you for reporting this bug to Ubuntu. Jaunty has reached EOL. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again. Do feel free to report any other bugs you may find. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Incomplete -- 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/370795 Title: update-manager is downloading all packages although its configured for security updates only Status in software-properties package in Ubuntu: Incomplete Bug description: Binary package hint: update-manager It seems that update-manager is currently downloading packages in the background when not configured to do so. I have been feeling this is true for some time, and likely ever since I upgraded to Jaunty but I have no confirmation of this behaviour until now. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: update-manager 1:0.111.9 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Uname: Linux 2.6.28-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/370795/+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 1485089] Re: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100
*** This bug is a duplicate of bug 1485396 *** https://bugs.launchpad.net/bugs/1485396 ** This bug has been marked a duplicate of bug 1485396 impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1485089 Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 Status in isc-dhcp package in Ubuntu: New Bug description: install failure during do-release-upgrade from vivid to wily seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately after. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 Date: Fri Aug 14 12:10:01 2015 DhServerLeases: DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new pre-removal script returned error exit status 100 ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationDate: Installed on 2014-04-15 (485 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro SourcePackage: isc-dhcp Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago) upstart.isc-dhcp-server.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485089/+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
Re: [Touch-packages] [Bug 1120658] Re: dash launcher icons don't get spoken with orca
*** This bug is a duplicate of bug 1066157 *** https://bugs.launchpad.net/bugs/1066157 duplicate 1066157 ** This bug has been marked a duplicate of bug 1066157 dash +orca does not speak the names of application icons ** This bug has been marked a duplicate of bug 1066157 dash +orca does not speak the names of application icons -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1120658 Title: dash launcher icons don't get spoken with orca Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: using raring daily build start the orca screen reader from the universal access settings, hit super to load the dash then navigate around using the keyboard (tab to get to the icon panels) The icons don't get spoken, but each category does get announced. The lens list at the bottom of the dash also doesn't get spoken and the filters don't get spoken. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1120658/+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
Re: [Touch-packages] [Bug 1120658] Re: dash launcher icons don't get spoken with orca
*** This bug is a duplicate of bug 1066157 *** https://bugs.launchpad.net/bugs/1066157 Everything in the dash except for the text search field should be accessible as of Wily. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1120658 Title: dash launcher icons don't get spoken with orca Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: using raring daily build start the orca screen reader from the universal access settings, hit super to load the dash then navigate around using the keyboard (tab to get to the icon panels) The icons don't get spoken, but each category does get announced. The lens list at the bottom of the dash also doesn't get spoken and the filters don't get spoken. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1120658/+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 1693503] Re: Remove mlx4.conf
** Changed in: kmod (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1693503 Title: Remove mlx4.conf Status in kmod package in Ubuntu: Confirmed Bug description: Hi, we are working on debianizing rdma-core package, it will contain a rdma service that manage the mlx4.conf file, so the conf file “/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not needed anymore, and must be removed. This conf file conflicts with “/lib/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+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
Re: [Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
Hui, do you know which patch in the pulseaudio package is responsible for this revert? A quick glance and I cannot find it. Luke -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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
Re: [Touch-packages] [Bug 1684324] [NEW] [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
Try moving your pulseaudio config out of the way. Log out of your desktop session, switch to a text virtual terminal by pressing control + alt + f1, logging in there, and moving the pulseaudio config like so: mv .config/pulse .config/pulse.old Log out of the text terminal, switch back to the GUI login by pressing Alt + F7, and then log in as normal, and see how things go. -- 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/1684324 Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: Upgraded to 17.04 from 16.10 today. Sound worked ok in previous versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1857 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 19:36:52 2017 InstallationDate: Installed on 2015-03-28 (753 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1857 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago) dmi.bios.vendor: Dell Inc. dmi.board.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1684324/+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 1686803] Re: Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the"
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" Status in sudo: Unknown Status in sudo package in Ubuntu: New Bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+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 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
This may have security implications in edge cases. E.g. if an application is checking the status code of `sudo` and using `0` as "good to go", this may allow for access to a resource to be permitted when it should not be. ** Summary changed: - Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" + sudo returns exit code 0 if child is killed with SIGTERM ** Tags added: regression-release ** Changed in: sudo (Ubuntu) Importance: Undecided => Medium ** Changed in: sudo (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Triaged Bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
The upload was rejected due to lack of SRU information. Could you please add that according to https://wiki.ubuntu.com/StableReleaseUpdates#Procedure Thanks. -- 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/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Trusty: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+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
Re: [Touch-packages] [Bug 1655386] [NEW] Ability to combine multiple devices into single speaker configuration
I believe this is possible, but there is no user interface to do this yet. I think module-combine-sink may do what you are after if you are willing to get your hands dirty with pacmd. -- 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/1655386 Title: Ability to combine multiple devices into single speaker configuration Status in pulseaudio package in Ubuntu: New Bug description: Hi, It would be very handy if we could combine multiple devices into one speaker configuration. For example if I could use my Bluetooth sound bar as rear left and right channels together with laptop's built in speakers as front left and right unto a 4.0 speaker configuration for surround sound. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1655386/+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 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off
** Tags removed: verification-needed -- 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/1641954 Title: Output switches from HDMI speakers to internal speakers on DPMS off Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: Impact: This bug affects users of audio via HDMI to their monitor or another HDMI device like an audio receiver. Regression potential: The regression potential should be low to non-existant. Test case: (1) Play some music through speakers connected through an HDMI display. (2) type `xset dpms force off` (3) Move mouse to bring screen back up. With the version of PulseAudio in Xenial now, music plays in internal speakers, even after display wakes up Once the version of PulseAudio from xenial-proposed is installed, music plays in HDMI speaker after display wakes up Original bug report PulseAudio 8.0 includes a well-known user-experience regression: Its new auto-routing algorithm tries to switch to another output, as soon as the active output gets disconnected. This leads to the following bad user experience: (1) Alice listens to music on her speakers, which are connected to the screen, which is connected through HDMI to the computer. (2) Alice leaves the computer, the screen gets suspended (DPMS off). (3) PulseAudio sees that the HDMI output got disconnected (although only for a short interval) and switches to internal speaker. (4) Alice returns to the computer but finds that the music is now playing through the internal speakers. (5) Alice can switch the output to the HDMI speakers manually, but the above user experience bug will reoccur when she leaves the computer again. This is a well-known upstream bug that was fixed in PulseAudio 9.0. Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is desirable to backport this fix to PulseAudio 8.0, so that all LTS users have better experience. Upstream said they would not do this and that I should report this to Ubuntu directly. Other information: * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946 * Fix 1: https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09 * Fix 2: https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: gintassi (gintassi) => (unassigned) ** Changed in: initramfs-tools (Ubuntu) Assignee: gintassi (gintassi) => Luke Faraone (lfaraone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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
Re: [Touch-packages] [Bug 1658528] [NEW] Sound not working anymore
Had you updated your system that you can remember prior to this problem occurring? If you were to boot 14.04 live media, does the problem exist there? If you have Windows or another distro installed, does the problem occur there? -- 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/1658528 Title: Sound not working anymore Status in pulseaudio package in Ubuntu: New Bug description: Didn't do anything strange but the sound just stopped working for my headphones. Just like that. I have multiple soundcards. The one affected is CA0132 which is the built-in card of the motherboard. The other card isn't affected (CA0106) and is working fine with external speakers. I also tried with a plug and play usb soundcard (USB PnP Sound Device). also not affected and is working (as expected I guess). Tried restarting. Tried playing around with alsamixer and pavucontrol. Tried checking for updates and updating to latest. ...Didn't try doing a back-flip tho hehe XD ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf] ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39 Uname: Linux 3.13.0-107-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 22 23:30:29 2017 InstallationDate: Installed on 2015-02-19 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper Z87 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.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: G1.Sniper Z87 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1658528/+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
Re: [Touch-packages] [Bug 1658528] Re: Sound not working anymore
What if you unplug and re-plug? If that doesn't work, then its likely something may have happened to your hardware. Do you have other outputs you could test? -- 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/1658528 Title: Sound not working anymore Status in pulseaudio package in Ubuntu: New Bug description: Didn't do anything strange but the sound just stopped working for my headphones. Just like that. I have multiple soundcards. The one affected is CA0132 which is the built-in card of the motherboard. The other card isn't affected (CA0106) and is working fine with external speakers. I also tried with a plug and play usb soundcard (USB PnP Sound Device). also not affected and is working (as expected I guess). Tried restarting. Tried playing around with alsamixer and pavucontrol. Tried checking for updates and updating to latest. ...Didn't try doing a back-flip tho hehe XD ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf] ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39 Uname: Linux 3.13.0-107-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 22 23:30:29 2017 InstallationDate: Installed on 2015-02-19 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper Z87 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.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: G1.Sniper Z87 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1658528/+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
Re: [Touch-packages] [Bug 1658528] Re: Sound not working anymore
Ok, do you have a 16.04 image handy? You may want to consider downloading 16.04, and testing with that. If that works, then maybe its worth considering an upgrade. -- 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/1658528 Title: Sound not working anymore Status in pulseaudio package in Ubuntu: New Bug description: Didn't do anything strange but the sound just stopped working for my headphones. Just like that. I have multiple soundcards. The one affected is CA0132 which is the built-in card of the motherboard. The other card isn't affected (CA0106) and is working fine with external speakers. I also tried with a plug and play usb soundcard (USB PnP Sound Device). also not affected and is working (as expected I guess). Tried restarting. Tried playing around with alsamixer and pavucontrol. Tried checking for updates and updating to latest. ...Didn't try doing a back-flip tho hehe XD ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf] ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39 Uname: Linux 3.13.0-107-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 22 23:30:29 2017 InstallationDate: Installed on 2015-02-19 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper Z87 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.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: G1.Sniper Z87 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1658528/+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
Re: [Touch-packages] [Bug 1671556] [NEW] [bytcr-rt5640 - bytcr-rt5640, playback] Pulseaudio fails to detect card
Could you plesae get a log from PulseAudio as outlined here: https://wiki.ubuntu.com/PulseAudio/Log. Thanks. -- 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/1671556 Title: [bytcr-rt5640 - bytcr-rt5640, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have a quantum byte Intel® Atom™ CPU Z3735F @ 1.33GHz × 4 Intel® Bay Trail 64-bit the audio shows as dummy input OS is ubuntu 16.10 I followed the help file and this is the screen text (below) any help or direction would be appreciated steve@elmoviii:~$ aplay -l List of PLAYBACK Hardware Devices card 0: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 steve@elmoviii:~$ sudo lspci [sudo] password for steve: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0f) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0f) 00:03.0 Multimedia controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera ISP (rev 0f) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0f) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0f) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0f) steve@elmoviii:~$ sudo lspci -v 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0f) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register Flags: bus master, fast devsel, latency 0 Kernel driver in use: iosf_mbi_pci 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0f) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display Flags: bus master, fast devsel, latency 0, IRQ 262 Memory at 9040 (32-bit, non-prefetchable) [size=4M] Memory at 8000 (32-bit, prefetchable) [size=256M] I/O ports at 1000 [size=8] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [d0] Power Management version 2 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [b0] Vendor Specific Information: Len=07 Kernel driver in use: i915 Kernel modules: i915 00:03.0 Multimedia controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera ISP (rev 0f) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera ISP Flags: bus master, fast devsel, latency 0 Memory at 9000 (32-bit, non-prefetchable) [size=4M] Capabilities: [80] Power Management version 2 Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0f) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI Flags: bus master, medium devsel, latency 0, IRQ 261 Memory at 90c0 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0f) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine Flags: bus master, fast devsel, latency 0, IRQ 263 Memory at 90b0 (32-bit, non-prefetchable) [size=1M] Memory at 90a0 (32-bit, non-prefetchable) [size=1M] Capabilities: [80] Power Management version 3 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit- Kernel driver in use: mei_txe Kernel modules: mei_txe 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0f) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c Kernel driver in use: lpc_ich Kernel modules: lpc_ich ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Re: [Touch-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps
Are any of those logs taken from when you are trying to use the microphone or when you try and adjust the settings for it in control- center? If not, try getting a log when trying to use both pavucontrol and unity- control-center to change microphone settings, since you did indicate that pavucontrol was at least showing something. Could you also run apport-collect 1667328 so I can get some info about your actual hardware? Thanks. -- 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/1667328 Title: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps Status in gstreamer package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic #42-Ubuntu In the last days the microphone stopped working when I am on the Google Hangouts video conference in the Chromium browser. I checked the sound settings of the System Settings and on the "input" tab the slider for the microphone volume is grayed out and cannot be moved away from the zero position. The microphone level monitor bar does not move when talking or touching the microphone. Then I found the following on the internet http://askubuntu.com/questions/508221/sound-input-device-microphone- not-working and tried to solve the problem following the hints: - Reboot does not solve the problem. - I could not do any tests with gstreamer-properties as it seems to have been removed from gstreamer (what is the successor?). - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices" Tab that the microphone of the laptop is OK and that the kernel works with it. The Level monitor bar is moving according to environment noise and touching of the microphone. - "sudo alsa force-reload" does not solve the problem. - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does not solve the problem. - audacity is recording through the microphone correctly. - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d /alsa-base.conf and rebooting does not solve the problem. I hope that is a known problem. Please tell me if you need further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer/+bug/1667328/+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
Re: [Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog
Please run apport-collect 1673942 in a terminal so we can get some more information about your hardware. -- 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/1673942 Title: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog Status in pulseaudio package in Ubuntu: New Bug description: this only happens when sound is through the PCI sound card. When i connect speakers to the motherboard output (I lose the 5.1 component), pulseaudio never dies. I have switched and replaced the sound card to no effect but I never really thought that was the issue. There seems to be no evidence of the failure unless I run it from the command line with -, when eventually I see a 'killed' message. The pulseaudio log collects initial messages, but nothing else is echoed to the log - which could be anything from 3-20 minutes [typically]. I'm more than happy to assist in getting whatever logs are required, but nothing I've seen documented seems to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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
Re: [Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog
Could you also get a log from PulseAudio as per https://wiki.ubuntu.com/PulseAudio/Log. Thanks. -- 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/1673942 Title: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog Status in pulseaudio package in Ubuntu: New Bug description: this only happens when sound is through the PCI sound card. When i connect speakers to the motherboard output (I lose the 5.1 component), pulseaudio never dies. I have switched and replaced the sound card to no effect but I never really thought that was the issue. There seems to be no evidence of the failure unless I run it from the command line with -, when eventually I see a 'killed' message. The pulseaudio log collects initial messages, but nothing else is echoed to the log - which could be anything from 3-20 minutes [typically]. I'm more than happy to assist in getting whatever logs are required, but nothing I've seen documented seems to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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
Re: [Touch-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps
Ok, I see pavucontrol changing the volume, and I see the control center connecting, but I don't see anything about it not being able to change the microphone volume, same with Chromium. Are you able to change the microphone volume with the sound indicator? One thing you could try, is to move your pulseaudio configuration out of the way temporarily to see if that resolves things. The best time to do this is when not logged into a graphical session, and do the move in a console. You want to move ~/.config/pulse out of the way. Once done, try the control center, and chromium again. No need to test pavucontrol, we know that its working. -- 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/1667328 Title: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps Status in gstreamer package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic #42-Ubuntu In the last days the microphone stopped working when I am on the Google Hangouts video conference in the Chromium browser. I checked the sound settings of the System Settings and on the "input" tab the slider for the microphone volume is grayed out and cannot be moved away from the zero position. The microphone level monitor bar does not move when talking or touching the microphone. Then I found the following on the internet http://askubuntu.com/questions/508221/sound-input-device-microphone- not-working and tried to solve the problem following the hints: - Reboot does not solve the problem. - I could not do any tests with gstreamer-properties as it seems to have been removed from gstreamer (what is the successor?). - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices" Tab that the microphone of the laptop is OK and that the kernel works with it. The Level monitor bar is moving according to environment noise and touching of the microphone. - "sudo alsa force-reload" does not solve the problem. - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does not solve the problem. - audacity is recording through the microphone correctly. - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d /alsa-base.conf and rebooting does not solve the problem. I hope that is a known problem. Please tell me if you need further information. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: till 2897 F pulseaudio /dev/snd/controlC1: till 2897 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-04-30 (686 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: pulseaudio 1:9.0-2ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Tags: yakkety third-party-packages Uname: Linux 4.8.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET40WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A8X50300 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8X50300:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8X50300:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A8X50300 dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer/+bug/1667328/+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
Re: [Touch-packages] [Bug 1676232] [NEW] No HDMI 5.1 profile listed for card, only 7.1
Could you please get a log from PulseAudio, as outlined here: https://wiki.ubuntu.com/PulseAudio/Log? Thanks. -- 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/1676232 Title: No HDMI 5.1 profile listed for card, only 7.1 Status in alsa-driver package in Ubuntu: New Bug description: I have researched and requested help on Launchpad two times and not had any responses what do to next. There is no HDMI 5.1 profile available There is 7.1 HDMI and it functions perfectly (sans missing channels on a 5.1 audio system). Please see below how the profile isn't detected and made available? Please direct me to a proper way to fix this. On a fresh install Ubuntu 16.04.2 LTS Release: 16.04 Thanks. ___1 card(s) available. index: 0 name: driver: owner module: 6 properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.long_card_name = "HDA Intel at 0xdf40 irq 33" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "293e" device.product.name = "82801I (ICH9 Family) HD Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: unknown) output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: unknown) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: unknown) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460, available: unknown) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 300, available: unknown) output:hdmi-surround71+input:analog-stereo: Digital Surround 7.1 (HDMI) Output + Analog Stereo Input (priority 360, available: unknown) off: Off (priority 0, available: unknown) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: fhess 5316 F...m pulseaudio /dev/snd/controlC0: fhess 5316 F pulseaudio CurrentDesktop: GNOME Date: Sun Mar 26 19:03:55 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [HP Pavilion dv7 Notebook PC, Nvidia MCP77/78 HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F4 dmi.board.vendor: Compal dmi.board.version: 99.75 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd10/01/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.13:rvnCompal:rn30F4:rvr99.75:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-03-26T01:09:33.814682 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1676232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https
[Touch-packages] [Bug 1693503] Re: Remove mlx4.conf
** Changed in: kmod (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1693503 Title: Remove mlx4.conf Status in kmod package in Ubuntu: Confirmed Bug description: Hi, we are working on debianizing rdma-core package, it will contain a rdma service that manage the mlx4.conf file, so the conf file “/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not needed anymore, and must be removed. This conf file conflicts with “/lib/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+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 1693503] Re: Remove mlx4.conf
Removing the mlx4.conf from kmod package is not going to cause a regression of bug LP: 1115710? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1693503 Title: Remove mlx4.conf Status in kmod package in Ubuntu: Confirmed Bug description: Hi, we are working on debianizing rdma-core package, it will contain a rdma service that manage the mlx4.conf file, so the conf file “/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not needed anymore, and must be removed. This conf file conflicts with “/lib/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+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 1661745] [NEW] ssh-keyscan does not exit with non-zero return code on error
Public bug reported: On xenial, ssh-keyscan returns zero indicating success, when the command fails. root@cp1:~# lsb_release -d Description:Ubuntu 16.04.1 LTS root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@cp1:~# echo $? 0 On trusty, the exit status is non-zero as expected. root@integration-deployer:/home/ubuntu# lsb_release -d Description:Ubuntu 14.04.5 LTS root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@integration-deployer:/home/ubuntu# echo $? 255 This is a incompatibility between Ubuntu 14.04 and 16.04 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1661745 Title: ssh-keyscan does not exit with non-zero return code on error Status in openssh package in Ubuntu: New Bug description: On xenial, ssh-keyscan returns zero indicating success, when the command fails. root@cp1:~# lsb_release -d Description: Ubuntu 16.04.1 LTS root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@cp1:~# echo $? 0 On trusty, the exit status is non-zero as expected. root@integration-deployer:/home/ubuntu# lsb_release -d Description: Ubuntu 14.04.5 LTS root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@integration-deployer:/home/ubuntu# echo $? 255 This is a incompatibility between Ubuntu 14.04 and 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1661745/+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
Re: [Touch-packages] [Bug 1662147] Re: Cannot stop pulseaudio
Do you have pulseaudio-module-jack installed? I believe that includes a module that will talk to jack and have pulse move out of the way, and reroute itself through jack. -- 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/1662147 Title: Cannot stop pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: I need to kill pulseaudio as I'm using Jackd instead. I don't want to delete it as I may need it back again. So far the only workaround I found was to delete /usr/bin/pulseaudio (or move it out of the way). norru@GBWWSRUNUBWS02:~$ pulseaudio -k norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru29938 8557 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29940 29938 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29941 29940 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30111 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru29938 8557 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29940 29938 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29941 29940 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30230 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru29938 8557 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29940 29938 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru29941 29940 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30250 28914 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30252 28942 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30297 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru29941 1 1 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30469 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru29941 1 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30486 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ pulseaudio -k norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru30489 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru30493 1 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru30506 29396 0 11:27 pts/000:00:00 grep --color=auto pulse norru@GBWWSRUNUBWS02:~$ ubuntu-bug pulseaudio norru@GBWWSRUNUBWS02:~$ sudo service pulseaudio stop norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru30493 1 0 11:27 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru@GBWWSRUNUBWS02:~$ kill 30493 norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru32318 1 1 11:32 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru@GBWWSRUNUBWS02:~$ kill -9 32318 norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru32361 8557 0 11:34 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru32363 32361 0 11:34 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru32364 32363 1 11:34 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse norru32364 1 1 11:34 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog norru32381 29396 0 11:34 pts/000:00:00 grep --color=auto pulse ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: norru 30493 F pulseaudio /dev/snd/controlC0: norru 30493 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Feb 6 11:28:49 2017 InstallationDate: Installed on 2015-06-10 (606 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to yakkety on 2016-10-31 (97 days ago) dmi.bios.date: 10/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4502 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPU
Re: [Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
After making the changes you made, are you still getting crashes? -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in pulseaudio package in Ubuntu: New Bug description: Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528/+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
Re: [Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
affects ubuntu/pulseaudio status invalid Ok, closing for now. Feel free to re-open if this crops up again. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in pulseaudio package in Ubuntu: Invalid Bug description: Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
** Bug watch added: freedesktop.org Bugzilla #65520 https://bugs.freedesktop.org/show_bug.cgi?id=65520 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=65520 Importance: Unknown Status: Unknown -- 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/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1670022] [NEW] Pulseaudio volume master breaks after plugging in headphones
Public bug reported: The only way I've found to restore it is by rebooting. I can control the volume with amixer, and pavucontrol's per-application sliders work fine, but the master in pavucontrol doesn't work. (So naturally the volume keys don't work either.) ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-utils (Ubuntu) => xubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1670022 Title: Pulseaudio volume master breaks after plugging in headphones Status in xubuntu-meta package in Ubuntu: New Bug description: The only way I've found to restore it is by rebooting. I can control the volume with amixer, and pavucontrol's per-application sliders work fine, but the master in pavucontrol doesn't work. (So naturally the volume keys don't work either.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1670022/+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 1691420] [NEW] package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in pack
Public bug reported: Not quite sure what triggered this bug Description:Ubuntu 16.04.2 LTS Release:16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 13 22:35:12 2017 DuplicateSignature: package:account-plugin-google:(not installed) Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2017-05-13 (4 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1691420 Title: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: Not quite sure what triggered this bug Description:Ubuntu 16.04.2 LTS Release:16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 13 22:35:12 2017 DuplicateSignature: package:account-plugin-google:(not installed) Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2017-05-13 (4 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1691420/+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
