[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
1. top
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
19147 systemd+ 20 0 50848 6232 4572 R 99.0 0.1 5:43.81
systemd-resolve
1472 dnsmasq 20 0 57020 3084 2620 R 63.1 0.0 44:03.49 dnsmasq
2. journalctl -u systemd-resolved.service
Apr 16 13:01:59 Danny systemd-resolved[19147]: DNSSEC validation failed for
question clients-china.l.google.com IN A: failed-auxiliary
Apr 16 13:02:02 Danny systemd-resolved[19147]: Using degraded feature set
(UDP+EDNS0) for DNS server 127.0.0.1.
Apr 16 13:02:08 Danny systemd-resolved[19147]: Server 127.0.0.1 does not
support DNSSEC, downgrading to non-DNSSEC mode.
Apr 16 13:06:24 Danny systemd-resolved[19147]: Server 192.168.128.1 does not
support DNSSEC, downgrading to non-DNSSEC mode.
Apr 16 13:11:24 Danny systemd-resolved[19147]: Grace period over, resuming full
feature set (UDP+EDNS0+DO+LARGE) for DNS server 127.0.0.1.
3. journalctl -u dnsmasq.service
Apr 16 13:18:27 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries
reached (max: 150)
Apr 16 13:18:33 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries
reached (max: 150)
Apr 16 13:18:39 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries
reached (max: 150)
Apr 16 13:18:45 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries
reached (max: 150)
Apr 16 13:18:51 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries
reached (max: 150)
4. lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename: zesty
5. sudo strace -p 1472 --- dnsmasq
bind(12, {sa_family=AF_INET, sin_port=htons(37051),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
sendto(12, "g\325\1\20\0\1\0\0\0\0\0\1\rclients-china\1l\6goo"..., 55, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, 16)
= 55
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN},
{fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9,
events=POLLIN}, {fd=12, events=POLLIN}], 8, -1) = 2 ([{fd=4, revents=POLLIN},
{fd=12, revents=POLLIN}])
recvfrom(12, "g\325\201\200\0\1\0\6\0\0\0\1\rclients-china\1l\6goo"..., 5131,
0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")},
[16]) = 151
sendmsg(4, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33355),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"\272\303\201\220\0\1\0\6\0\0\0\1\rclients-china\1l\6goo"...,
151}], msg_controllen=0, msg_flags=0}, 0) = 151
close(12) = 0
recvmsg(4, {msg_name(16)={sa_family=AF_INET, sin_port=htons(57326),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"C\21\1\20\0\1\0\0\0\0\0\1\rclients-china\1l\6goo"..., 4096}],
msg_controllen=0, msg_flags=0}, 0) = 55
socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 12
fcntl(12, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(12, F_SETFL, O_RDWR|O_NONBLOCK) = 0
6. sudo strace -p 1914
clock_gettime(CLOCK_BOOTTIME, {5858, 172230641}) = 0
open("/run/systemd/netif/links/2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=1040890848,
u64=94559040879584}}) = 0
write(18, ";q\1\20\0\1\0\0\0\0\0\1\17ec2-52-7-217-10\tcom"..., 68) = 68
clock_gettime(CLOCK_BOOTTIME, {5858, 172456596}) = 0
clock_gettime(CLOCK_BOOTTIME, {5858, 172482649}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
sendmsg(15, {msg_name(16)={sa_family=AF_INET, sin_port=htons(45041),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"qX\201\200\0\1\0\1\0\0\0\1\17ec2-52-7-217-10\tcom"..., 84}],
msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
{ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_flags=0}, 0) = 84
epoll_wait(4, [{EPOLLIN, {u32=1039855040, u64=94559039843776}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {5858, 172675790}) = 0
recvfrom(15, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 68
recvmsg(15, {msg_name(16)={sa_family=AF_INET, sin_port=htons(48677),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"\313{\1\20\0\1\0\0\0\0\0\1\17ec2-52-7-217-10\tcom"..., 3936}],
msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
{ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}, {cmsg_len=20, cmsg_level=SOL_IP,
cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) = 68
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\213\235", 2, GRND_NONBLOCK) = 2
stat("/etc/resolv.conf",
[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
Sorry to bang on, but (1) previous comments don't seem editable, (2) running the aforementioned script through http://www.shellcheck.net/ identifies some potential problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early Status in D-Bus: Won't Fix Status in dbus package in Ubuntu: Fix Released Bug description: (part of bug 1431774). During shutdown, D-Bus stops too early. In particular, it stops before NetworkManager and remote-fs.target, so that any network unmount will cause errors and hang the boot. This can be seen with $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)' Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus... Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager... Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager. Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket. A quick workaround is to add After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section, but this should be fixed in a more general fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+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 1670959] Re: systemd-resolved using 100% CPU
This bug still exists in ubuntu 17.04 release version!
100% CPU with "Unassigned", OMG!
--
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/1670959
Title:
systemd-resolved using 100% CPU
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M77 Ver. 01.05
dmi.board.name: 2271
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.4C
dmi.chassis.asset.tag: CNU51199KV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
(But I've removed the cups and the 'up' bits.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early Status in D-Bus: Won't Fix Status in dbus package in Ubuntu: Fix Released Bug description: (part of bug 1431774). During shutdown, D-Bus stops too early. In particular, it stops before NetworkManager and remote-fs.target, so that any network unmount will cause errors and hang the boot. This can be seen with $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)' Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus... Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager... Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager. Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket. A quick workaround is to add After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section, but this should be fixed in a more general fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+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 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array
Followed up on bug 1683105 . I've worked out the exact thing that needs to be done. -- 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/1313169 Title: Ubuntu Trusty Tahr cannot boot on RAID5 array Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Raid array is three identical Western Digital Green series 500GB hard drives on an NVIDIA controller set to RAID5 for a total of 1TiB (931.52GB) storage. Installation was done using the Ubuntu LiveCD. Partitions on the filesystem was created beforehand using gparted. The partition table is set up to be GPT with a 8MB bios_grub partition, a 256MB fat32 EFIBoot partition (not used for this setup, board does not support EFI and is expected to boot from the bios_grub legacy partition), a 4GB swap, 80GB root partition, and the rest for /home. Then the installer is invoked and the partitions are set up. GRUB is told to install to the root of the RAID array in /dev/mapper . The installation went flawlessly. Upon reboot, GRUB loads as expected, and loads the kernel and initrd as expected. However, the kernel gives up on waiting for the root partition and drops to initramfs busybox. "dmesg|grep device" shows the following errors: device-mapper: table: 252:0: raid: unknown target type device-mapper: ioctl: error adding target to table Trying to invoke dmraid -a y results in the following error: ERROR: device-mapper target type "raid" is not in the kernel RAID set "nvidia_babddecf" was not activated. nvidia_babddecf is the assigned volume name by the controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+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 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
@Adam Felson I'm trying out your script, combined with autofs (which doesn't work via fstab). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early Status in D-Bus: Won't Fix Status in dbus package in Ubuntu: Fix Released Bug description: (part of bug 1431774). During shutdown, D-Bus stops too early. In particular, it stops before NetworkManager and remote-fs.target, so that any network unmount will cause errors and hang the boot. This can be seen with $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)' Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus... Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager... Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager. Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket. A quick workaround is to add After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section, but this should be fixed in a more general fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+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 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
I suffer from this too. It affects both systemd's automounts and autofs. It's driving me nuts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early Status in D-Bus: Won't Fix Status in dbus package in Ubuntu: Fix Released Bug description: (part of bug 1431774). During shutdown, D-Bus stops too early. In particular, it stops before NetworkManager and remote-fs.target, so that any network unmount will cause errors and hang the boot. This can be seen with $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)' Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus... Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager... Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager. Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket. A quick workaround is to add After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section, but this should be fixed in a more general fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+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 388553] Re: Wi-Fi Protected Setup (WPS) not supported
** Changed in: network-manager Status: Confirmed => In Progress -- 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/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: In Progress Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1683096] [NEW] [37722QP, Realtek ALC269VC, Black Headphone Out, Left] audio balance slider problem
Public bug reported: Sound works normally on the standard speakers, but when I put on the headphone I notice that only the left side emits sound, so I go to the settings and notice that the audio balance slider is well to the left, I set it to The center and everything goes on working normally. In many cases I also notice that the sound is only emitted on the left side, even though the slider is centered, so again in this case I take the slider and move it out of the center and then center it again, and the sound is properly balanced normally. I already checked if it was the plugs and jacks, and they are perfect, otherwise I would not be able to get around the problem by changing the "slider" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: titan 2299 F...m pulseaudio /dev/snd/controlC0: titan 2299 F pulseaudio CurrentDesktop: GNOME Date: Sat Apr 15 23:30:18 2017 InstallationDate: Installed on 2017-01-28 (77 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Volume slider, or mixer problems Title: [37722QP, Realtek ALC269VC, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H1ET82BX(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 37722QP dmi.board.vendor: LENOVO dmi.board.version: Win8 STD EM DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH1ET82BX(1.21):bd11/21/2013:svnLENOVO:pn37722QP:pvrLenovoB490:rvnLENOVO:rn37722QP:rvrWin8STDEMDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37722QP dmi.product.version: Lenovo B490 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1683096 Title: [37722QP, Realtek ALC269VC, Black Headphone Out, Left] audio balance slider problem Status in alsa-driver package in Ubuntu: New Bug description: Sound works normally on the standard speakers, but when I put on the headphone I notice that only the left side emits sound, so I go to the settings and notice that the audio balance slider is well to the left, I set it to The center and everything goes on working normally. In many cases I also notice that the sound is only emitted on the left side, even though the slider is centered, so again in this case I take the slider and move it out of the center and then center it again, and the sound is properly balanced normally. I already checked if it was the plugs and jacks, and they are perfect, otherwise I would not be able to get around the problem by changing the "slider" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: titan 2299 F...m pulseaudio /dev/snd/controlC0: titan 2299 F pulseaudio CurrentDesktop: GNOME Date: Sat Apr 15 23:30:18 2017 InstallationDate: Installed on 2017-01-28 (77 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Volume slider, or mixer problems Title: [37722QP, Realtek ALC269VC, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H1ET82BX(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 37722QP dmi.board.vendor: LENOVO dmi.board.version: Win8 STD EM DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Touch-packages] [Bug 1683095] [NEW] rsync has -C / --cvs-exclude enabled permanently
Public bug reported: After upgrading to Ubuntu 17.04 I've noticed that every rsync command has the -C option added and I can see no way to disable this very unwanted behavior. I've been running the same set of rsync commands for years and the -C option was never tacked on like it is now (as far as I can tell). I've read the man pages, checked the various config files, tried adding --no-C to all of my scripts (as annoying as that is) and still see no functioning way to disable this. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1683095 Title: rsync has -C / --cvs-exclude enabled permanently Status in rsync package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 I've noticed that every rsync command has the -C option added and I can see no way to disable this very unwanted behavior. I've been running the same set of rsync commands for years and the -C option was never tacked on like it is now (as far as I can tell). I've read the man pages, checked the various config files, tried adding --no-C to all of my scripts (as annoying as that is) and still see no functioning way to disable this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1683095/+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 1683094] [NEW] Upgrade conflict DNS broken between Network Manager and systemd-resolved
Public bug reported: After upgrading my laptop from 16.10 ubuntu studio to 17.04, no DNS names could be resolved with either an ethernet or wifi connection. Something as simple as "ping myOtherHost" failed... The Zesty 17.04 release notes clearly state "The default DNS resolver is now systemd-resolved", but there is NO warning that this change will break many mature and working NetworkManager configurations. NetworkManager is still started by systemd, but it seems to be oblivious to the presence of systemd-resolved, which in my case had over-written the /etc/resolv.conf symlink created by NM. There is a lot of relevant but confusing posts out there, some for earlier releases of ubuntu. I managed to fight my way through the problem, but I suspect many people will be stuck and become angry. In particular, anyone who upgrades a working NM system with a configuration that is too complex for systemd-resolved (wifi seems to be the obvious problem area) won't even be able to search the internet for known problems unless he or she has access to a different computer! The circumvention is fairly simple and is documented elsewhere... the user MUST prevent systemd-resolved ever running and then repair Network Manager if it has been left damaged after the upgrade. First, prevent systemd-resolved from ever running: sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved sudo systemctl mask systemd-resolved (yes, that is correct. Without the mask "something" re-enabled it on my system!) Second (belts and braces), get NetworkManager re-configured properly: sudo apt-get install --reinstall network-manager (I think this was the trigger that re-enabled systemd-resolved, but can't be sure). Third, fix NetworkManager if DNS names are still not resolved properly: dpkg -l dnsmasq-base (make sure its status is "ii" meaning properly installed) edit /etc/NetworkManager/NetworkManager.conf and make sure "dns=dnsmasq" is in the [Main] section. Reboot and confirm your NM connections work and DNS resolution is working properly. (/etc/resolv.conf should be a soft link to /var/run/NetworkManager/resolv.conf and "ps aux | grep dns" should confirm dnsmasq is running. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Uname: Linux 4.10.0-19-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 16 11:28:13 2017 InstallationDate: Installed on 2016-06-04 (315 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6417 Microdia Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Studio 1558 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-lowlatency root=UUID=5236cad2-f68b-4cf0-93d2-0f725e609514 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago) dmi.bios.date: 03/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0874P6 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd03/30/2011:svnDellInc.:pnStudio1558:pvrA12:rvnDellInc.:rn0874P6:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Studio 1558 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1683094 Title: Upgrade conflict DNS broken between Network Manager and systemd- resolved Status in systemd package in Ubuntu: New Bug description: After upgrading my laptop from 16.10 ubuntu studio to 17.04, no DNS names could be resolved with either an ethernet or wifi connection. Something as simple as "ping myOtherHost" failed... The Zesty 17.04 release notes clearly state "The default DNS resolver is now systemd-resolved", but there is NO warning that this change will break many mature and working NetworkManager configurations. NetworkManager is still started by systemd, but it seems to be oblivious to the presence of systemd-resolved, which in my case had over-written the /etc/resolv.conf symlink created by NM. There is a lot of relevant but confusing posts out there, some for earlier releases of ubuntu. I managed to fight my way through the problem, but I suspect many people will be stuck and become angry. In particular, anyone who
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
but did you boot into recovery mode in grub? Might be a different bug if not -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 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 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1683083] [NEW] Sound Blaster Z Card does not work
Public bug reported: I have a Sound Blaster Z Card but does not work on my Ubuntu 17.04 What I supposed to do? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-46.49-lowlatency 4.8.17 Uname: Linux 4.8.0-46-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: german 1918 F...m pulseaudio /dev/snd/controlC2: german 1918 F pulseaudio /dev/snd/controlC0: german 1918 F pulseaudio /dev/snd/controlC1: german 1918 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Apr 15 18:11:26 2017 InstallationDate: Installed on 2016-10-23 (174 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [GeForce 8000 series, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) dmi.bios.date: 08/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: GeForce 8000 series dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/27/2009:svnECS:pnGeForce8000series:pvr1.0:rvnECS:rnGeForce8000series:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: GeForce 8000 series dmi.product.version: 1.0 dmi.sys.vendor: ECS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1683083 Title: Sound Blaster Z Card does not work Status in alsa-driver package in Ubuntu: New Bug description: I have a Sound Blaster Z Card but does not work on my Ubuntu 17.04 What I supposed to do? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-46.49-lowlatency 4.8.17 Uname: Linux 4.8.0-46-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: german 1918 F...m pulseaudio /dev/snd/controlC2: german 1918 F pulseaudio /dev/snd/controlC0: german 1918 F pulseaudio /dev/snd/controlC1: german 1918 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Apr 15 18:11:26 2017 InstallationDate: Installed on 2016-10-23 (174 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [GeForce 8000 series, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) dmi.bios.date: 08/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: GeForce 8000 series dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/27/2009:svnECS:pnGeForce8000series:pvr1.0:rvnECS:rnGeForce8000series:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: GeForce 8000 series dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683083/+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 1681175] Re: network-manager don't work normally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1681175 Title: network-manager don't work normally Status in network-manager package in Ubuntu: Confirmed Bug description: Network manager sometimes do not connect, and requires a reboot to normal operation ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 9 10:02:33 2017 IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.102 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 Alex_K 326fd280-ba5b-4fbb-92bf-5bce191aa86b /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- ttyACM1 gsm unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681175/+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 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1681884 Title: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty Status in network-manager package in Ubuntu: Confirmed Bug description: Upon a "clean" upgrade (No software installed except base system from ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360, Network Manager fails to detect wiFi device in 17.04 Zesty after a few boots/updates. Wifi works initially. I apply Zesty updates. I autoremoved some packages. I reboot. Wifi is killed. I cannot report the bug using "ubuntu-bug" because I have no network connectivity. The wifi device was not detected despite re-enabling Dell's Xenial repos after upgrades. I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0. Plugging ethernet cable into that does not work either. It seemed the adapter was "half" recognized. Something did show up in Network Manager after fiddling with settings, but no network connectivity ever occurred. I can create a separate bug for that if needed. I subsequently had to revert back to 16.04 LTS with a clean install to report the bug. I'm not so familiar with what the Dell repos provide for Xenial. Do they provide the drivers needed for the wifi? Or is that supplied through the kernel? Could the autoremove have caused the wifi drivers to be removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+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 1683077] [NEW] package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: podproces nový pre-removal skript vrátil chybový status 1
Public bug reported: Problem dialog raised after upgrade to Ubuntu 17.04. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Apr 15 02:04:01 2017 ErrorMessage: podproces nový pre-removal skript vrátil chybový status 1 InstallationDate: Installed on 2011-03-16 ( days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: podproces nový pre-removal skript vrátil chybový status 1 UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago) ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1683077 Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: podproces nový pre-removal skript vrátil chybový status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: Problem dialog raised after upgrade to Ubuntu 17.04. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Apr 15 02:04:01 2017 ErrorMessage: podproces nový pre-removal skript vrátil chybový status 1 InstallationDate: Installed on 2011-03-16 ( days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: podproces nový pre-removal skript vrátil chybový status 1 UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1683077/+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 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)
*** This bug is a duplicate of bug 1654918 *** https://bugs.launchpad.net/bugs/1654918 I have a similar issue with the bcmwl-kernel-source for Broadcom BCM4359 802.11 Hybrid Wireless Controller 6.30.223.271 (r58733). If I reset network service, the wifi network works for a few minutes: sudo service network-manager restart This is what dmesg says: wl: loading out-of-tree module taints kernel. [ 14.318743] wl: module license 'MIXED/Proprietary' taints kernel. [ 14.318744] Disabling lock debugging due to kernel taint [ 14.320217] wl: module verification failed: signature and/or required key missing - tainting kernel [ 14.393619] wlan0: Broadcom BCM4359 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) wlo1 Scan_results error (-22) [ 502.407031] usb 3-3: USB disconnect, device number 2 [ 909.203000] ERROR @wl_cfg80211_scan : [ 909.203002] WLC_SCAN error (-22) [ 910.204637] ERROR @wl_cfg80211_scan : [ 910.204640] WLC_SCAN error (-22) [ 911.206039] ERROR @wl_cfg80211_scan : [ 911.206043] WLC_SCAN error (-22) -- 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/1679535 Title: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails) Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, I think this is a bug in the WIFI-driver or kernel. Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server to get to the internet. I have periodically *serious* problems with WIFI in Ubuntu 17.04. The network icon shows "connected" to the router and internet, but browsers and other attempts to get data report DNS error / or not connected. This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME etc.). Same laptop with Ubuntu 16.10 works flawlessly. The connection works fine after I reboot (power off/on) the router box. Then the bug may return (or may not return) after I turn on my laptop next time. This laptop is Toshiba Stellite P50 C. The laptop has Intel Corporation Wireless 3165 (rev 81). $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep 'iwlwifi-7265d' 0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010] Kernel driver in use: iwlwifi -- 0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1179:f840] Kernel driver in use: r8169 Kernel modules: r8169 4.11.0-041100rc4-generic Ref: https://wiki.debian.org/iwlwifi Restarting the network.manager does not help. $ sudo service network-manager restart Network manager connects (and sees) to the router, but cannot access internet. - Please see also: https://ubuntuforums.org/search.php?searchid=14761184 and https://ubuntuforums.org/showthread.php?t=2356828 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 Uname: Linux 4.11.0-041100rc4-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 4 08:22:23 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-27 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev wlp13s0 proto static metric 600 169.254.0.0/16 dev wlp13s0 scope link metric 1000 192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp13s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 Ubuntu-Linux-Network dda6e4cf-5cd9-4e01-b638-418985262413 /org/freedesktop/NetworkManager/ActiveConnection/5 enp14s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 ------ lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 ------ nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled
[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)
** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+attachment/4862776/+files/UdevDb.txt ** Description changed: When connected via 4G to Three/3 (UK), DNS lookups fail (though the internet is otherwise working). The connection receives the correct DNS servers, but as far as I can work out systemd-resolve is unaware of them. Connection info screenshot is attached. DNS lookups time out: $ nslookup www.bbc.co.uk ;; connection timed out; no servers could be reached However they work when manually specifying the DNS server: $ nslookup www.bbc.co.uk 217.171.132.0 Server: 217.171.132.0 Address: 217.171.132.0#53 Non-authoritative answer: www.bbc.co.uk canonical name = www.bbc.net.uk. Name: www.bbc.net.uk Address: 212.58.246.54 Name: www.bbc.net.uk Address: 212.58.244.26 Connections to IP addresses work (though redirect to a Three page at present): $ curl http://212.58.246.54 -v * Rebuilt URL to: http://212.58.246.54/ * Trying 212.58.246.54... * TCP_NODELAY set * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0) > GET / HTTP/1.1 > Host: 212.58.246.54 > User-Agent: curl/7.52.1 > Accept: */* - > + > < HTTP/1.1 302 Moved Temporarily < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html < Content-Type: text/plain; charset=UTF-8 < Content-Length: 0 - < + < * Curl_http_done: called premature == 0 * Connection #0 to host 212.58.246.54 left intact Below is the output of systemd-resolve --status: $ systemd-resolve --status Global - DNS Servers: 8.8.8.8 - 8.8.4.4 - 2001:4860:4860:: - 2001:4860:4860::8844 - DNSSEC NTA: 10.in-addr.arpa - 16.172.in-addr.arpa - 168.192.in-addr.arpa - 17.172.in-addr.arpa - 18.172.in-addr.arpa - 19.172.in-addr.arpa - 20.172.in-addr.arpa - 21.172.in-addr.arpa - 22.172.in-addr.arpa - 23.172.in-addr.arpa - 24.172.in-addr.arpa - 25.172.in-addr.arpa - 26.172.in-addr.arpa - 27.172.in-addr.arpa - 28.172.in-addr.arpa - 29.172.in-addr.arpa - 30.172.in-addr.arpa - 31.172.in-addr.arpa - corp - d.f.ip6.arpa - home - internal - intranet - lan - local - private - test + DNS Servers: 8.8.8.8 + 8.8.4.4 + 2001:4860:4860:: + 2001:4860:4860::8844 + DNSSEC NTA: 10.in-addr.arpa + 16.172.in-addr.arpa + 168.192.in-addr.arpa + 17.172.in-addr.arpa + 18.172.in-addr.arpa + 19.172.in-addr.arpa + 20.172.in-addr.arpa + 21.172.in-addr.arpa + 22.172.in-addr.arpa + 23.172.in-addr.arpa + 24.172.in-addr.arpa + 25.172.in-addr.arpa + 26.172.in-addr.arpa + 27.172.in-addr.arpa + 28.172.in-addr.arpa + 29.172.in-addr.arpa + 30.172.in-addr.arpa + 31.172.in-addr.arpa + corp + d.f.ip6.arpa + home + internal + intranet + lan + local + private + test Link 4 (wlp4s0) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade + DNSSEC supported: yes Link 3 (wwp0s20f0u6i12) - Current Scopes: LLMNR/IPv4 LLMNR/IPv6 -LLMNR setting: yes + Current Scopes: LLMNR/IPv4 LLMNR/IPv6 + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade + DNSSEC supported: yes Link 2 (enp0s31f6) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade +
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kstars (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in kstars package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+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 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)
Update: The ISP redirect has now gone away and the internet now works. However, if the output of systemd-resolve --status is anything to go by systemd-resolve appears to still be using Google DNS instead of my ISP's (which seems utterly bizarre). I would surmise that while the redirect was in place, systemd-resolve was using Google DNS and access to the Google DNS servers was blocked until the SIM had been set up. This basically makes it impossible to set up the type of SIM I had (https://www.three.co.uk/Free_SIM_MBB/Order) on Ubuntu (I had to do that on Windows). That's because the SIM requires registration, which you have to do via mobile internet while using the SIM. -- 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/1683066 Title: Broken DNS when using Three UK mobile internet (17.04 zesty) Status in systemd package in Ubuntu: New Bug description: When connected via 4G to Three/3 (UK), DNS lookups fail (though the internet is otherwise working). The connection receives the correct DNS servers, but as far as I can work out systemd-resolve is unaware of them. Connection info screenshot is attached. DNS lookups time out: $ nslookup www.bbc.co.uk ;; connection timed out; no servers could be reached However they work when manually specifying the DNS server: $ nslookup www.bbc.co.uk 217.171.132.0 Server: 217.171.132.0 Address: 217.171.132.0#53 Non-authoritative answer: www.bbc.co.uk canonical name = www.bbc.net.uk. Name: www.bbc.net.uk Address: 212.58.246.54 Name: www.bbc.net.uk Address: 212.58.244.26 Connections to IP addresses work (though redirect to a Three page at present): $ curl http://212.58.246.54 -v * Rebuilt URL to: http://212.58.246.54/ * Trying 212.58.246.54... * TCP_NODELAY set * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0) > GET / HTTP/1.1 > Host: 212.58.246.54 > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 302 Moved Temporarily < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html < Content-Type: text/plain; charset=UTF-8 < Content-Length: 0 < * Curl_http_done: called premature == 0 * Connection #0 to host 212.58.246.54 left intact Below is the output of systemd-resolve --status: $ systemd-resolve --status Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 3 (wwp0s20f0u6i12) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Note: Everything works fine on Wi-Fi, this problem is only happening on 4G. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu2 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 CurrentDesktop: Unity:Unity7 Date: Sat Apr 15 20:54:33 2017 InstallationDate: Installed on 2017-04-08 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) MachineType: LENOVO 20HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1683072] [NEW] dell
Public bug reported: grafica ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-48.51~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 15 22:56:04 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca] InstallationDate: Installed on 2017-04-14 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Latitude E7240 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=449c6e1f-0c61-4de4-833e-756ee75d16bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.asset.tag: NKTcables dmi.board.name: 060GR9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NKTcables dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn060GR9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7240 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1683072 Title: dell Status in xorg package in Ubuntu: New Bug description: grafica ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-48.51~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 15 22:56:04 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca] InstallationDate: Installed on 2017-04-14 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Latitude E7240 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=449c6e1f-0c61-4de4-833e-756ee75d16bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.asset.tag: NKTcables dmi.board.name: 060GR9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NKTcables dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn060GR9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7240 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
It looks like there was some activity with a kernel patch from someone at canonical at some point: https://patchwork.kernel.org/patch/9128611/ -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1683066] [NEW] Broken DNS when using Three UK mobile internet (17.04 zesty)
Public bug reported: When connected via 4G to Three/3 (UK), DNS lookups fail (though the internet is otherwise working). The connection receives the correct DNS servers, but as far as I can work out systemd-resolve is unaware of them. Connection info screenshot is attached. DNS lookups time out: $ nslookup www.bbc.co.uk ;; connection timed out; no servers could be reached However they work when manually specifying the DNS server: $ nslookup www.bbc.co.uk 217.171.132.0 Server: 217.171.132.0 Address:217.171.132.0#53 Non-authoritative answer: www.bbc.co.uk canonical name = www.bbc.net.uk. Name: www.bbc.net.uk Address: 212.58.246.54 Name: www.bbc.net.uk Address: 212.58.244.26 Connections to IP addresses work (though redirect to a Three page at present): $ curl http://212.58.246.54 -v * Rebuilt URL to: http://212.58.246.54/ * Trying 212.58.246.54... * TCP_NODELAY set * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0) > GET / HTTP/1.1 > Host: 212.58.246.54 > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 302 Moved Temporarily < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html < Content-Type: text/plain; charset=UTF-8 < Content-Length: 0 < * Curl_http_done: called premature == 0 * Connection #0 to host 212.58.246.54 left intact Below is the output of systemd-resolve --status: $ systemd-resolve --status Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 3 (wwp0s20f0u6i12) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Note: Everything works fine on Wi-Fi, this problem is only happening on 4G. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu2 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 CurrentDesktop: Unity:Unity7 Date: Sat Apr 15 20:54:33 2017 InstallationDate: Installed on 2017-04-08 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) MachineType: LENOVO 20HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET53W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HDCTO1WW 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:bvrN1QET53W(1.28):bd03/29/2017:svnLENOVO:pn20HDCTO1WW:pvrThinkPadT470:rvnLENOVO:rn20HDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HDCTO1WW dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Connection information screenshot" https://bugs.launchpad.net/bugs/1683066/+attachment/4862764/+files/three-conn-info.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1683066 Title: Broken DNS when using Three UK mobile internet (17.04 zesty) Status in systemd package in Ubuntu: New Bug description: When connected via 4G to Three/3 (UK), DNS
[Touch-packages] [Bug 403911] Re: bluez-simple-agent missing
still an issue as of 16.10 root@tony-Satellite-S55t-C:~/ixxat# grep . /etc/issue Ubuntu 16.10 \n \l what's the problem here? why is it dropped? -- 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/403911 Title: bluez-simple-agent missing Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez What else is there to say? Relevant to at least Intrepid and Jaunty, possibly many more. bluez-simple-agent is 3 kB in size, and a very important tool for binding (inserting PIN), when not using bluez-gnome (maybe one is limited to console only), or when bluez-gnome decides to use a random PIN (https://bugs.launchpad.net/ubuntu/+source/bluez- gnome/+bug/284994) It's a part of bluez package, so... was there a GOOD reason to drop it in the first place? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/403911/+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 1683062] [NEW] package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3
Public bug reported: It does not upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 16 00:03:52 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2016-01-23 (448 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1683062 Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 Status in python3-defaults package in Ubuntu: New Bug description: It does not upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 16 00:03:52 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2016-01-23 (448 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1683062/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1658921 *** https://bugs.launchpad.net/bugs/1658921 On 2017-04-15 I upgraded from 16.04 to 16.10 on the way to 17.04. This issue was the one and only problem I encountered. In my case I started the wired interface manually (sudo ifconfig enp3s0 up && sudo dhclient epn3s0), got on-line and found this page. Message 6 above worked perfectly, and it's an easy fix once one knows what to do - but not until then. It would be a very good idea to fix this, because as observed above it's a disproportionate nuisance as it prevents web access, hindering the the search for a fix and for neophytes - exactly the people we want to get using Linux - that could drive them away. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1658921] Re: NetworkManager does not manage wired connection
On 2017-04-15 I upgraded from 16.04 to 16.10 on the way to 17.04. This issue was the one and only problem I encountered. In my case I started the wired interface manually (sudo ifconfig enp3s0 up && sudo dhclient epn3s0), got on-line and found this page. Message 6 above worked perfectly, and it's an easy fix once one knows what to do - but not until then. It would be a very good idea to fix this, because as observed above it's a disproportionate nuisance as it prevents web access, hindering the the search for a fix and for neophytes - exactly the people we want to get using Linux - that could drive them away. -- 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/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1683054] [NEW] package unattended-upgrades 0.90ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: plz slove it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Sat Apr 15 23:03:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-07-18 (1366 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-04-15 (0 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2013-07-22T09:33:54.666057 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1683054 Title: package unattended-upgrades 0.90ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: plz slove it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Sat Apr 15 23:03:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-07-18 (1366 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-04-15 (0 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2013-07-22T09:33:54.666057 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1683054/+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 1384394] Re: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" comman
*Ubuntu 16.04* The workaround by deleting /run/resolvconf/interface/NetworkManager did not work for me. Removing dns=dnsmasq from /etc/NetworkManager/NetworkManager.conf did work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1384394 Title: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" command Status in dnsmasq package in Ubuntu: Triaged Bug description: lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy resolvconf resolvconf: Installed: 1.69ubuntu1.1 Candidate: 1.69ubuntu1.1 Version table: *** 1.69ubuntu1.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.69ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages DESCRIPTION: network-manager: My "eth0" and "wlan0" cards are managed by the network-manager and this works fine. /etc/network/interfaces: My 2 bridges "br0" and "br1" are managed in "/etc/network/interfaces" as follows: ... iface br0 inet static address 192.168.10.1 netmask 255.255.255.0 dns-nameservers 192.168.10.2 bridge_ports none bridge_stp off bridge_fd 0 bridge_maxwait 0 iface br1 inet static address 192.168.0.1 netmask 255.255.255.0 dns-nameservers 192.168.0.2 bridge_ports none bridge_stp off bridge_fd 0 bridge_maxwait 0 ... When I now bring up the bridge interfaces using: sudo ifup br0 br1 Then they show up fine in "ifconfig". BUT "dns-nameservers 192.168.10.2" and "dns-nameservers 192.168.0.2" DO NOT show up in "/etc/resolv.conf" WORKAROUND: Until this has been fixed the following workaround works fine for me: sudo vi /etc/resolvconf/interface-order #Add the following entry (this entry can be put on any line BUT it has to come before the last entry "*"): ... br* ... * PS: Based on the workaround in "/etc/resolvconf/interface-order" I think the issue is in package "resolvconf" otherwise I would have reported the error against the "ifupdown scripts". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1384394/+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 1680811] Re: Request to add wireguard interface to interface-order
It might make more sense to simply switch to using openresolv, which is a proper resolvconf implementation, which doesn't rely on this silly hard-coded list. Alternatively, you could just backport features one by one from openresolv, such as '-m 0 and '-x'. But really, since openresolv has no downsides and only upsides, and Debian's homebaked resolvconf is rotting and has issues, you'd really be better off just removing Debian's resolvconf from Ubuntu and relying instead on openresolv. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1680811 Title: Request to add wireguard interface to interface-order Status in resolvconf package in Ubuntu: Triaged Bug description: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
Here the same. I upgraded from 16.10 to 17.04. Network is not active. I cannot surf in internet. -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 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 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 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 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1683044] [NEW] TouchPad not working, despite correctly detected
Public bug reported: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse1 event7 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 TrackPad correctly detected, when running evtest on it, no event appearing. Working correctly with a USB mouse ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 15 12:17:56 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb01] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GF108M [GeForce GT 630M] [1179:fb01] InstallationDate: Installed on 2017-04-15 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: TOSHIBA Satellite P850 ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic.efi.signed root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 6.60 dmi.board.asset.tag: * dmi.board.name: QFKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr6.60:bd12/07/2012:svnTOSHIBA:pnSatelliteP850:pvrPSPKFC-00E004:rvnTOSHIBA:rnQFKAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.name: Satellite P850 dmi.product.version: PSPKFC-00E004 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Apr 15 12:06:36 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu yakkety ** Attachment added: "evtest" https://bugs.launchpad.net/bugs/1683044/+attachment/4862615/+files/evtest -- 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/1683044 Title: TouchPad not working, despite correctly detected Status in xorg package in Ubuntu: New Bug description: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse1 event7 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 TrackPad correctly detected, when running evtest on it, no event appearing. Working correctly with a USB mouse ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 15 12:17:56 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb01] NVIDIA
[Touch-packages] [Bug 1564252] Re: [HDA-Intel - HDA Intel PCH, recording] No sound from external microphone on headset
Fix proposed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539843 -- 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/1564252 Title: [HDA-Intel - HDA Intel PCH, recording] No sound from external microphone on headset Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound from external microphone on headset. Work well in windows. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2273 F pulseaudio /dev/snd/pcmC1D0p: ubuntu 2273 F...m pulseaudio /dev/snd/controlC1: ubuntu 2273 F pulseaudio CasperVersion: 1.368 CurrentDesktop: Unity Date: Thu Mar 31 06:18:30 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) 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_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2273 F pulseaudio /dev/snd/controlC1: ubuntu 2273 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JM.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1564252/+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 1682978] Re: Random Screen Rotation
For me, it's counterclockwise. I tried setting the "lock rotation" option referenced in https://askubuntu.com/questions/874487/ubuntu- gnome-16-10-screen-orientation-spontaneously-changes (had to switch to Unity 8 to find it), but it didn't make a difference when I logged back in under Cinnamon, the windowing environment I usually use. -- 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/1682978 Title: Random Screen Rotation Status in xorg package in Ubuntu: Confirmed Bug description: My screen randomly rotates 90 degrees clockwise without warning. It has happened twice so far, once was yesterday after I installed UG 17.04, and once today. The first time was when I was still getting my system setup for myself after install, and the second time was while I had left the system unattended for an extended period of time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 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 CurrentDesktop: GNOME Date: Fri Apr 14 20:35:02 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-13 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+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 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary
Setting /etc/systemd/resolv.conf entry DNSSEC=no and enacting a sudo service systemd-resolved restart works around the problem for me. However, DNSSEC with the default (i.e. fallback) should still work. Starting Firefox does not "fix" the problem for me, though. -- 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/1650877 Title: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary Status in systemd package in Ubuntu: Confirmed Bug description: After I boot Ubuntu 17.04 "Zesty Zapus" (dev) $ systemd-resolve www.facebook.com www.facebook.com: resolve call failed: DNSSEC validation failed: failed-auxiliary But after I have started Mozilla Firefox, and I try again it correctly resolves. $ systemd-resolve www.facebook.com www.facebook.com: 31.13.72.36 (star-mini.c10r.facebook.com) -- Information acquired via protocol DNS in 3.6ms. -- Data is authenticated: no This does not only apply to the above mentioned www.facebook.com domain. This seems to be related to a GitHub issue: https://github.com/systemd/systemd/issues/4003 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650877/+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 1682978] Re: Random Screen Rotation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1682978 Title: Random Screen Rotation Status in xorg package in Ubuntu: Confirmed Bug description: My screen randomly rotates 90 degrees clockwise without warning. It has happened twice so far, once was yesterday after I installed UG 17.04, and once today. The first time was when I was still getting my system setup for myself after install, and the second time was while I had left the system unattended for an extended period of time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 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 CurrentDesktop: GNOME Date: Fri Apr 14 20:35:02 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-13 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+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 1658921] Re: NetworkManager does not manage wired connection
Got the same issue upgrading from 16.04 to 16.10 and again from 16.10 to 17.04. Deleting the file worked. Sad that this is not fixed. -- 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/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1682192] Re: My printers are not recognized by Ubuntu 16.10
I'm not sure why you would report your issue against xorg but https://wiki.ubuntu.com/Bugs/FindRightPackage#Printing suggests that *cups* is the package to report such issues against. You might also take a look at https://wiki.ubuntu.com/DebuggingPrintingProblems Also, reporting any issues that you come across in the English language, if that is possible, would be of great help to bug triagers. ** Package changed: xorg (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1682192 Title: My printers are not recognized by Ubuntu 16.10 Status in cups package in Ubuntu: New Bug description: Mes imprimantes sont : Epson WF-3520 et Brother DCP-7030 J'ai chargé un pilote généric esc/p-r pour l'Epson WF-3520 qui a d'abord bien fonctionné et puis sans raison apparente, le système a dysfonctionné. Depuis aucune de mes imprimantes n'est reconnue par Ubuntu 16.10. Ubuntu 16.10 est installé en dual boot avec Windows 7 depuis une semaine. Juste une précison : je suis nul en programmation informatique et comprends avec difficulté la langue anglaise ! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 BootLog: [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d5-1\x2d5.1). See 'systemctl status "udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\\x2d5-1\\x2d5.1.service"' for details. [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d4). See 'systemctl status "udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\\x2d4.service"' for details. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 12 19:12:27 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GF108 [GeForce GT 730] [1462:8a9f] InstallationDate: Installed on 2017-04-01 (11 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. H110M-DS2 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=fbe8f99a-28b6-422e-b4fc-52de97bfa3d1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20 dmi.board.asset.tag: Default string dmi.board.name: H110M-DS2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-DS2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-DS2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: H110M-DS2 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Apr 12 20:55:24 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1682192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account
Confirmed on Ubuntu 16.04, Evolution 3.20.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Evolution appears unable to create EWS or Exchange MAPI account Status in evolution-ews: Expired Status in evolution package in Ubuntu: Triaged Status in evolution-data-server package in Ubuntu: Triaged Status in evolution-ews package in Ubuntu: Triaged Status in evolution-mapi package in Ubuntu: Won't Fix Bug description: Evolution appears unable to create an EW or MAPI account. All the steps proceed normally, including fetching the URL (for EWS) or authenticating (for MAPI). However, at the conclusion of account creation process, no actual account appears in the list. I've tried starting Evolution from the command line using various DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm not exactly sure what to do next. I am fairly certain the problem doesn't lie with my corporate Exchange server, as web mail works fine and any other EWS-capable client (like the mail app in Android). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evolution 3.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 12:40:28 2012 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 (20120925) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1061195/+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 1681513] Re: Ubuntu 17.04: wi-fi not working — mac address keeps changing?
Thanks Jesse for the workaround ! -- 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/1681513 Title: Ubuntu 17.04: wi-fi not working — mac address keeps changing? Status in network-manager package in Ubuntu: Confirmed Bug description: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1573715] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de o
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1573715 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 Status in One Hundred Papercuts: Confirmed Status in perl package in Ubuntu: Confirmed Bug description: problem with update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 19:03:32 2016 DpkgTerminalLog: Preparando para desempaquetar .../libperl5.22_5.22.1-9_i386.deb ... Desempaquetando libperl5.22:i386 (5.22.1-9) ... dpkg: error al procesar el archivo /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573715/+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 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
Based on duplicates, the same issue affects 16.10. ** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Bug description: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+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 1575110] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de o
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1575110 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Just that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 26 12:11:04 2016 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2016-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1575110/+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 1577163] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres i
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1577163 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Une solution??? Free ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 1 14:34:49 2016 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 InstallationDate: Installed on 2016-05-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1577163/+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 1611516] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.22/changelog.Debian.gz' partilhado, que é diferente de outras
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1611516 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.22/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: erro na atualização de 15.04 para 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 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 Date: Tue Aug 9 18:14:08 2016 DpkgTerminalLog: A preparar para desempacotar .../libperl5.22_5.22.1-9_i386.deb ... A descompactar libperl5.22:i386 (5.22.1-9) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): a tentar sobreescrever '/usr/share/doc/libperl5.22/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libperl5.22:i386 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libperl5.22/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libperl5.22:i386 InstallationDate: Installed on 2016-08-09 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.22/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1611516/+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 1640734] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1640734 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Bug description: Wanted to install scanner ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Nov 10 10:56:59 2016 DuplicateSignature: package:libperl5.22:5.22.2-3 Unpacking libperl5.22:i386 (5.22.2-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-Il1Esk/23-libperl5.22_5.22.2-3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-07-29 (103 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1640734/+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 1659114] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz' as a fix for failed installation
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1659114 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz' as a fix for failed installation of irssi , which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Installation that triggered problem was installation of irssi on HP Probook 450G1. lsb_release -a LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety uname -a Linux curiosity 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy irssi irssi: Installed: 0.8.19-1ubuntu2 Candidate: 0.8.19-1ubuntu2 Version table: *** 0.8.19-1ubuntu2 500 500 http://ug.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy libperl5.22: Installed: 5.22.2-3 Candidate: 5.22.2-3 Version table: *** 5.22.2-3 500 500 http://ug.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 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 Date: Tue Jan 24 16:29:34 2017 DuplicateSignature: package:libperl5.22:5.22.2-3 Unpacking libperl5.22:i386 (5.22.2-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-38X7QD/28-libperl5.22_5.22.2-3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-12-06 (49 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1659114/+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 1640863] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de o
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1640863 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: ultimamente me salen muchos avisos de errores ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Nov 10 13:37:00 2016 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2016-11-09 (0 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1640863/+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 1637865] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres i
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1637865 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: installing ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 30 15:37:44 2016 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 InstallationDate: Installed on 2016-10-30 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1637865/+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 1668015] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres i
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1668015 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: This bug occurs on start of my computer ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Feb 23 20:57:13 2017 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 InstallationDate: Installed on 2017-01-21 (36 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.22/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1668015/+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 1659487] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1659487 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Bug description: Ubuntu Crash ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 Uname: Linux 4.8.3-040803-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri Jan 20 13:31:45 2017 DuplicateSignature: package:libperl5.22:5.22.2-3 Unpacking libperl5.22:i386 (5.22.2-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-NdLby7/29-libperl5.22_5.22.2-3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-10-18 (99 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1659487/+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 1677117] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches versc
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1677117 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist Status in perl package in Ubuntu: New Bug description: attempted to instal hP scanner ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 21:34:35 2017 ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist InstallationDate: Installed on 2017-03-19 (9 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1677117/+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 1617608] Re: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf',
*** This bug is a duplicate of bug 1622499 *** https://bugs.launchpad.net/bugs/1622499 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1622499, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1622499 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 -- 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/1617608 Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Status in One Hundred Papercuts: Confirmed Status in account-plugins package in Ubuntu: Confirmed Bug description: no crash, just a failed update message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 27 19:06:15 2016 DuplicateSignature: package:account-plugin-google:0.12+16.04.20160126-0ubuntu1 Unpacking account-plugin-google (0.13+16.04.20160719-0ubuntu1) over (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2015-04-26 (489 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: account-plugins Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: Upgraded to xenial on 2016-05-02 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1617608/+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 1633762] Re: ubuntu log out me
*** This bug is a duplicate of bug 1622499 *** https://bugs.launchpad.net/bugs/1622499 ** This bug is no longer a duplicate of bug 1617608 package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ** This bug has been marked a duplicate of bug 1622499 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 -- 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/1633762 Title: ubuntu log out me Status in account-plugins package in Ubuntu: New Bug description: every time log in to ubuntu after few second log out me and ask for user name and password agian and agian ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google 0.12+15.10.20150723-0ubuntu1 [modified: usr/share/accounts/providers/google.provider] ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 14 12:29:39 2016 DuplicateSignature: package:account-plugin-google:0.12+15.10.20150723-0ubuntu1 [modified: usr/share/accounts/providers/google.provider] Unpacking account-plugin-google (0.13+16.04.20160719-0ubuntu1) over (0.12+15.10.20150723-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-04-22 (176 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: account-plugins Title: package account-plugin-google 0.12+15.10.20150723-0ubuntu1 [modified: usr/share/accounts/providers/google.provider] failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2015-04-21T15:11:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1633762/+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 1681513] Re: Ubuntu 17.04: wi-fi not working — mac address keeps changing?
Hey friends, make sure you click "this bug affects me too" so that anyone who reads this report will know it's affecting a lot of users. I can reproduce the bug on Ubuntu 17.04, Ubuntu Mate 17.04 and Ubuntu GNOME 17.04. The workaround in the first comment here does fix the issue for me as well so it appears to just be a poor default configuration. I'm using a Panda Wireless USB adapter, which has an Ralink RT5372 chipset in it. -- 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/1681513 Title: Ubuntu 17.04: wi-fi not working — mac address keeps changing? Status in network-manager package in Ubuntu: Confirmed Bug description: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1681513] Re: Ubuntu 17.04: wi-fi not working — mac address keeps changing?
** Summary changed: - Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps changing? + Ubuntu 17.04: wi-fi not working — mac address keeps changing? -- 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/1681513 Title: Ubuntu 17.04: wi-fi not working — mac address keeps changing? Status in network-manager package in Ubuntu: Confirmed Bug description: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1683004] [NEW] launching unity bug, screen stop from the launching system
Public bug reported: graphics performance, my real question is why X didn't use hardware acceleration for my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: * Setting up X socket directories... [210G [204G[ OK ] Running 0dns-down to make sure resolv.conf is ok...done. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 15 10:10:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-67-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:3010] InstallationDate: Installed on 2014-05-26 (1054 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Compaq dc7600 Convertible Minitower ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=565ea83a-34a8-4891-b36a-2a18c0af3973 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786D1 v01.03 dmi.board.name: 09F0h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC64824P2 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786D1v01.03:bd05/18/2005:svnHewlett-Packard:pnHPCompaqdc7600ConvertibleMinitower:pvr:rvnHewlett-Packard:rn09F0h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc7600 Convertible Minitower dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80+git1704150630.f02719~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1704150730.9f0dd8~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1704150730.9f0dd8~gd~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.99+git1704111933.d6c292~gd~x version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1704101933.b57abe~gd~x version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14+git1704031933.e9418e~gd~x xserver.bootTime: Sat Apr 15 09:31:06 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- 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/1683004 Title: launching unity bug, screen stop from the launching system Status in xorg package in Ubuntu: New Bug description: graphics performance, my real question is why X didn't use hardware acceleration for my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: * Setting up X socket directories... [210G [204G[ OK ] Running 0dns-down to make sure resolv.conf is ok...done. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 15 10:10:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-67-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:3010] InstallationDate: Installed on
[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection
I just upgraded 16.10 -> 17.04 and this defect still is present. The bad /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf was recreated and I had to delete it to get my wired LAN back. -- 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/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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
