date:20170415

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650395

Title:
  Strange large grey border around gnome-terminal when transparency is
  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650395

Title:
  Strange large grey border around gnome-terminal when transparency is
  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683109] [NEW] icon/statusmap images don't work after upgrading to Zesty

2017-04-15 Thread Ben Coleman

Public bug reported:

I just upgraded my Nagios3 server from Yakkety to Zesty, and the icon
and status map images no longer display.  Icons come up as broken
images, and status map images show as question marks.  I can see the
images  under both /usr/share/nagios/htdocs/images/logos/ and
/usr/share/nagios3/htdocs/images/logos/.  Evidently, the images are for
some reason not being found in either place.

** Affects: nagios3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683109

Title:
  icon/statusmap images don't work after upgrading to Zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1683109/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-04-15 Thread Eldar Khayrullin

The same issue as Sudeep Duggal say (Ubuntu 17.04 bug, Ubuntu 16.10
works fine).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 992464] Re: Menu not accessible when run via ssh xforwarding

2017-04-15 Thread TomaszChmielewski

I'm still seeing this issue with Ubuntu 17.04.

To reproduce:


# ssh to localhost (or, any other host)
ssh -X user@localhost

# run a simple command like gedit or gnome-calculator
gedit


They run fine, unfortunately the menu is not available.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992464

Title:
  Menu not accessible when run via ssh xforwarding

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/992464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 992464] Re: Menu not accessible when run via ssh xforwarding

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992464

Title:
  Menu not accessible when run via ssh xforwarding

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/992464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1681652] Re: Laptop screen does not turn off when closing lid from login screen.

2017-04-15 Thread Mathew Tebbens

Your right, it appears to only happen when I'm logged in.

If I boot cold, at the login screen I can close and open the laptop lid
as much as I want and the screen will instantly turn off (no fade),
which is what I expect to happen.

What information can I provide to fix this issue on my system and other
systems it may happen on?

Matthew

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681652

Title:
  Laptop screen does not turn off when closing lid from login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681652/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1180649] Re: sbsigntool prints scary warning about invalid PE-COFF files which should be debug infos (file-aligned section .text extends beyond end of file; checksum areas are greater than im

2017-04-15 Thread Steve Langasek

On Sat, Apr 15, 2017 at 07:21:44PM -, Edoardo Barolo wrote:
> Is it possible that this bug can affect motherboard efi boot/bios ?
> Because when I use windows in my ASUS H97 plus all works fine. 

No.  This is a spurious warning message in a signing utility, it does not
impact the runtime behavior of EFI boot on Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180649

Title:
  sbsigntool prints scary warning about invalid PE-COFF files which
  should be debug infos (file-aligned section .text extends beyond end
  of file; checksum areas are greater than image size. Invalid section
  table?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sbtools/+bug/1180649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (i386) - tests ran: 4, failed: 0

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_05-12-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-15 Thread Danny

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",

[Bug 1683108] [NEW] Annoying Warning: to-Python converter already registered (Zesty)

2017-04-15 Thread Khurshid Alam

Public bug reported:

I get this annoying warning when I try to use libtorrent in my code:

Warning:
--
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: to-Python 
converter for boost::shared_ptr already registered; second 
conversion method ignored.


Test-Case:
---
#!/usr/bin/python3

import libtorrent as lt
info = lt.torrent_info("some-torrent.torrent")
info_hash = info.info_hash()
print (info_hash)


Package-Version:

OS: Ubuntu 17.04
libboost-python1.62.0 (1.62.0+dfsg-4)
libboost-random1.62.0 (1.62.0+dfsg-4)
libtorrent-rasterbar9 (1.1.1-1)
python3-libtorrent (1.1.1-1)

** Affects: libtorrent-rasterbar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: zesty

** Description changed:

  I get this annoying warning when I try to use libtorrent in my code:
  
- to-Python converter for boost::shared_ptr already
+ /usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: to-
+ Python converter for boost::shared_ptr already
  registered; second conversion method ignored.
- 
  
  Test-Case:
  ---
  
  #!/usr/bin/python3
  
  import libtorrent as lt
  info = lt.torrent_info("some-torrent.torrent")
  info_hash = info.info_hash()
  print (info_hash)
  
- 
  Package-Version:
  
  OS: Ubuntu 17.04
  libboost-python1.62.0 (1.62.0+dfsg-4)
  libboost-random1.62.0 (1.62.0+dfsg-4)
  libtorrent-rasterbar9 (1.1.1-1)
  python3-libtorrent (1.1.1-1)

** Description changed:

  I get this annoying warning when I try to use libtorrent in my code:
  
- /usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: to-
- Python converter for boost::shared_ptr already
- registered; second conversion method ignored.
+ 
+ Warning:
+ --
+ /usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: to-Python 
converter for boost::shared_ptr already registered; second 
conversion method ignored.
  
  Test-Case:
  ---
  
  #!/usr/bin/python3
  
  import libtorrent as lt
  info = lt.torrent_info("some-torrent.torrent")
  info_hash = info.info_hash()
  print (info_hash)
  
  Package-Version:
  
  OS: Ubuntu 17.04
  libboost-python1.62.0 (1.62.0+dfsg-4)
  libboost-random1.62.0 (1.62.0+dfsg-4)
  libtorrent-rasterbar9 (1.1.1-1)
  python3-libtorrent (1.1.1-1)

** Description changed:

  I get this annoying warning when I try to use libtorrent in my code:
- 
  
  Warning:
  --
  /usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: to-Python 
converter for boost::shared_ptr already registered; second 
conversion method ignored.
  
+ 
  Test-Case:
  ---
- 
  #!/usr/bin/python3
  
  import libtorrent as lt
  info = lt.torrent_info("some-torrent.torrent")
  info_hash = info.info_hash()
  print (info_hash)
+ 
  
  Package-Version:
  
  OS: Ubuntu 17.04
  libboost-python1.62.0 (1.62.0+dfsg-4)
  libboost-random1.62.0 (1.62.0+dfsg-4)
  libtorrent-rasterbar9 (1.1.1-1)
  python3-libtorrent (1.1.1-1)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683108

Title:
  Annoying Warning: to-Python converter already registered (Zesty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libtorrent-rasterbar/+bug/1683108/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown, D-BUS stops too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-15 Thread Danny

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959

Title:
  systemd-resolved using 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown, D-BUS stops too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683106] [NEW] Grub fails to install on fresh 17.04 installation

2017-04-15 Thread AbuMaia

Public bug reported:

Fresh installation of Ubuntu Gnome 17.04 to a disk with separate /home
partition.

Grub installation fails, prompting the installer to crash and send this
error report.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
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
CasperVersion: 1.380
Date: Sat Apr 15 22:58:11 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu-gnome zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683106

Title:
  Grub fails to install on fresh 17.04 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1683106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683105] [NEW] Installation of DMRaid should automatically add necessary modules to /etc/initramfs-tools/modules

2017-04-15 Thread David Lee

Public bug reported:

This is related to bug 1313169, I have had a sudden bout of clarity on
the cause of the issue.

I propose this modification to the dmraid installation script as it is a
small but necessary enhancement.

When dmraid is installed, it adds all the necessary hooks to initramfs-
tools. However, it has one oversight, that the required raid modules are
not added to /etc/initramfs-tools/modules. Without these modules, dmraid
will inevitably fail to initialize the array when started since the
kernel would not be able to find the required modules in the image.

I propose that when dmraid is installed, during installation the script
would check to see if the following items are already in /etc/initramfs-
tools/modules, and append the required modules into the bottom of the
file if it's not, and then rebuild the initramfs, update grub and if
necessary reinstall grub. On uninstall of package, I propose that we
should just warn the user but leave the lines in just in case they're
using something else that also needs the modules.

The following modules should be appended to the /etc/inmitramfs-
tools/modules file:

raid0
dm_raid
raid1
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_tx
raid6_pq
async_xor
xor
libcrc32c

** Affects: dmraid (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: linux (Ubuntu) => dmraid (Ubuntu)

** Description changed:

  This is related to bug 1313169, I have had a sudden bout of clarity on
  the cause of the issue.
  
  I propose this modification to the dmraid installation script as it is a
  small but necessary enhancement.
  
  When dmraid is installed, it adds all the necessary hooks to initramfs-
  tools. However, it has one oversight, that the required raid modules are
  not added to /etc/initramfs-tools/modules. Without these modules, dmraid
  will inevitably fail to initialize the array when started since the
  kernel would not be able to find the required modules in the image.
  
  I propose that when dmraid is installed, during installation the script
  would check to see if the following items are already in /etc/initramfs-
  tools/modules, and append the required modules into the bottom of the
  file if it's not, and then rebuild the initramfs, update grub and if
  necessary reinstall grub. On uninstall of package, I propose that we
  should just warn the user but leave the lines in just in case they're
  using something else that also needs the modules.
  
  The following modules should be appended to the /etc/inmitramfs-
  tools/modules file:
  
  raid0
  dm_raid
  raid1
  raid10
  raid456
  async_raid6_recov
  async_memcpy
  async_pq
  async_tx
  raid6_pq
+ async_xor
+ xor

** Description changed:

  This is related to bug 1313169, I have had a sudden bout of clarity on
  the cause of the issue.
  
  I propose this modification to the dmraid installation script as it is a
  small but necessary enhancement.
  
  When dmraid is installed, it adds all the necessary hooks to initramfs-
  tools. However, it has one oversight, that the required raid modules are
  not added to /etc/initramfs-tools/modules. Without these modules, dmraid
  will inevitably fail to initialize the array when started since the
  kernel would not be able to find the required modules in the image.
  
  I propose that when dmraid is installed, during installation the script
  would check to see if the following items are already in /etc/initramfs-
  tools/modules, and append the required modules into the bottom of the
  file if it's not, and then rebuild the initramfs, update grub and if
  necessary reinstall grub. On uninstall of package, I propose that we
  should just warn the user but leave the lines in just in case they're
  using something else that also needs the modules.
  
  The following modules should be appended to the /etc/inmitramfs-
  tools/modules file:
  
  raid0
  dm_raid
  raid1
  raid10
  raid456
  async_raid6_recov
  async_memcpy
  async_pq
  async_tx
  raid6_pq
  async_xor
  xor
+ libcrc32c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683105

Title:
  Installation of DMRaid should automatically add necessary modules to
  /etc/initramfs-tools/modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1683105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683103] Re: Use final Firefox 38 ESR tarball to build mozjs38

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2805

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1952

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2807

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2808

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-4513

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683103

Title:
  Use final Firefox 38 ESR tarball to build mozjs38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array

2017-04-15 Thread David Lee

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313169

Title:
  Ubuntu Trusty Tahr cannot boot on RAID5 array

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (amd64) - tests ran: 34, failed: 4

tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_04-11-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1505409] Re: gnome-shell crashed with signal 5 in _XIOError()

2017-04-15 Thread Roman Zabaluev

Happens in 17.04 for me, after logging in and randomly during the work.
Topicons installed, will try disabling it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505409

Title:
  gnome-shell crashed with signal 5 in _XIOError()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1683064] Re: package digikam 4:5.4.0-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/metainfo/org.kde.digikam.appdata.xml', which is also in package digikam5-data 4:5.5.0-

2017-04-15 Thread yves

It's ok by now.  After I did remove everything and reinstall it worked.
Thanks for your help

On Sat, Apr 15, 2017 at 10:38 PM, Rik Mills 
wrote:

> Removing the ppa digikam5-data 4:5.5.0-yakkety~ppa1 package and any
> other digikam package from that ppa should allow installation of the
> ubuntu package. Changed to a question, as this seems a support or
> configuration issue, and not a bug.
>
> ** Changed in: digikam (Ubuntu)
>Status: New => Invalid
>
> ** Converted to question:
>https://answers.launchpad.net/ubuntu/+source/digikam/+question/620821
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683064
>
> Title:
>   package digikam 4:5.4.0-0ubuntu3 failed to install/upgrade: trying to
>   overwrite '/usr/share/metainfo/org.kde.digikam.appdata.xml', which is
>   also in package digikam5-data 4:5.5.0-yakkety~ppa1
>
> Status in digikam package in Ubuntu:
>   Invalid
>
> Bug description:
>   previous installation was working fine under 16.10.  After
>   installation of 17.04 digikam was removed at time of installation and
>   I cannot reinstall it..  system error..
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.04
>   Package: digikam 4:5.4.0-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
>   Uname: Linux 4.10.0-19-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   Date: Sat Apr 15 21:54:45 2017
>   ErrorMessage: trying to overwrite 
> '/usr/share/metainfo/org.kde.digikam.appdata.xml',
> which is also in package digikam5-data 4:5.5.0-yakkety~ppa1
>   RelatedPackageVersions:
>dpkg 1.18.10ubuntu2
>apt  1.4
>   SourcePackage: digikam
>   Title: package digikam 4:5.4.0-0ubuntu3 failed to install/upgrade:
> trying to overwrite '/usr/share/metainfo/org.kde.digikam.appdata.xml',
> which is also in package digikam5-data 4:5.5.0-yakkety~ppa1
>   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/digikam/+bug/
> 1683064/+subscriptions
>


--





*Après demain, aujourd'hui sera hier..."..Donne un cheval à celui qui dit
la vérité : il en aura besoin pour s’enfuir...""Mamihlapinatapai, du yagan,
langue amérindienne parlée par le peuple du même nom au Chili
 et en Terre de Feu, est réputé être l’un des
mots les plus difficiles à traduire
. Il
signifie « un regard partagé entre deux personnes dont chacune espère que
l’autre va prendre

l’initiative de quelque chose que les deux désirent mais qu’aucun ne veut
commencer ».""Fight Club: “On a long enough timeline the survival rate for
everyone drops to zero.”""How much can we actually know about the economy?
When does data signify, and when is it merely noisy and uncertain?"*


*“Maybe it is time to do better things rather than just doing things
better.”"Do not do today what you can do better tomorrow."*

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683064

Title:
  package digikam 4:5.4.0-0ubuntu3 failed to install/upgrade: trying to
  overwrite '/usr/share/metainfo/org.kde.digikam.appdata.xml', which is
  also in package digikam5-data 4:5.5.0-yakkety~ppa1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1683064/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1022929] Re: package mpd 0.16.5-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022929

Title:
  package mpd 0.16.5-1ubuntu4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1022929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1432617] Re: package mpd (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432617

Title:
  package mpd (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1432617/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1457385] Re: package mpd 0.18.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457385

Title:
  package mpd 0.18.7-1 failed to install/upgrade: package is in a very
  bad inconsistent state; you should  reinstall it before attempting
  configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1457385/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked

[Expired for deja-dup (Ubuntu) because there has been no activity for 60
days.]

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989750

Title:
  repeatedly asks for encryption password when backing up, even though
  "remember password" is ticked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/989750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1522942] Re: package mpd 0.18.7-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522942

Title:
  package mpd 0.18.7-1 failed to install/upgrade: el subproceso
  instalado el script post-installation devolvió el código de salida de
  error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1522942/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506141] Re: package mpd 0.18.7-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506141

Title:
  package mpd 0.18.7-1 failed to install/upgrade: subprocess installed
  post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1506141/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656113] Re: MPD gets stuck

[Expired for mpd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mpd (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656113

Title:
  MPD gets stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1656113/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1657462] Re: I cannot install ubuntu alongside windows. Grub is not installed

[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: grub-installer (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657462

Title:
  I cannot install ubuntu alongside windows. Grub is not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1657462/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1664646] Re: installation Lubuntu 32 bit error, Ubi Partman ( partitioning ) error

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664646

Title:
  installation Lubuntu 32 bit error, Ubi Partman ( partitioning ) error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1664646/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683103] [NEW] Use final Firefox 38 ESR tarball to build mozjs38

*** This bug is a security vulnerability ***

Public security bug reported:

Impact
--
SpiderMonkey (or mozjs) is Firefox's JavaScript engine. It is not
well-supported by Mozilla. Generally, someone at Mozilla makes only one tarball
release per Firefox ESR. For 38, this was done around 38.2. Fedora and Arch
Linux build their mozjs38 using the final Firefox ESR tarball (38.8) which has
7 more months of high-priority bugfixes included.

https://developer.mozilla.org/en-
US/docs/Mozilla/Projects/SpiderMonkey/Releases/38

A quick review of the git log showed that there are multiple high-
priority security fixes in this update.

Test Case
-
Install the update.
Reboot
Log into GNOME Shell. Does it seem to work ok?

Regression Potential

The gjs maintainer has so far only tested with the original release tarball,
but the risk is mitigated by being used by Fedora. Mozilla does tend to be
cautious about updating its ESR branch.

Other Info
--
The Firefox tarball is very slow and difficult to work with since it has so
many files. It was too big for the new debian/copyright Files-Excluded repack (
https://bugs.debian.org/855464 ). I used the older debian/repack scripts to cut
the extra files.

With the repack, I lost the INSTALL, LICENSE and README files which are
not included in the Firefox tarball since I didn't know how to use the
repack script to inject a copy of those files. It did not seem important
enough to use a quilt patch to restore them since they aren't shipped in
the resulting binary packages.

js/src/ctypes/libffi/doc/libffi.info and js/src/jit-test/tests/sunspider
/check-string-unpack-code.jswere removed because
debian/README.source says to remove them.

Here's a visual diff of the new tarball:
https://anonscm.debian.org/git/pkg-gnome/mozjs38.git/commit/?h=debian/unstable&id=ae6f925b6

And here's a git log (the original mozjs38 tarball is from mid-September 2015)
https://github.com/mozilla/gecko-dev/commits/esr38/js/src

** Affects: mozjs38 (Ubuntu)
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683103

Title:
Use final Firefox 38 ESR tarball to build mozjs38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683103/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown, D-BUS stops too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (i386) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_02-39-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown, D-BUS stops too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

2017-04-15 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/388553

Title:
  Wi-Fi Protected Setup (WPS) not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683100] [NEW] package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.6 failed to install/upgrade: package samba-common is already installed and configured

2017-04-15 Thread Sudarshan Kakoty

Public bug reported:

Automated dpkg bug report

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.6
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: i386
BothFailedConnect: Yes
CrashReports:
 600:0:115:157534:2017-04-16 08:45:07.527202367 +0530:2017-04-16 
08:45:08.527202367 +0530:/var/crash/samba-common.0.crash
 600:0:115:157544:2017-04-16 08:45:08.511210043 +0530:2017-04-16 
08:45:08.499215880 +0530:/var/crash/libwbclient0:i386.0.crash
 600:0:115:157525:2017-04-16 08:45:08.499215880 +0530:2017-04-16 
08:45:08.363282042 +0530:/var/crash/libglade2-0:i386.0.crash
Date: Sun Apr 16 08:45:08 2017
DuplicateSignature:
 package:samba-common:2:4.3.11+dfsg-0ubuntu0.16.04.6
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libglade2-0:i386 (--configure):
  package libglade2-0:i386 is already installed and configured
ErrorMessage: package samba-common is already installed and configured
InstallationDate: Installed on 2017-04-15 (0 days ago)
InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216)
NmbdLog:
 
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: dpkg
Title: package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.6 failed to 
install/upgrade: package samba-common is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dpkg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed apport-package i386 need-duplicate-check xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683100

Title:
  package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.6 failed to
  install/upgrade: package samba-common is already installed and
  configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1683100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1659593] Re: package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: virtualbox-ext-pack (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659593

Title:
  package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1659593/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1681970] Re: gnome-calendar with google account only can start from terminal, no launchers works

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681970

Title:
  gnome-calendar with google account only can start  from terminal, no
  launchers works

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1681970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1681970] Re: gnome-calendar with google account only can start from terminal, no launchers works

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1681970

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: gnome-calendar (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681970

Title:
  gnome-calendar with google account only can start  from terminal, no
  launchers works

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1681970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683096] [NEW] [37722QP, Realtek ALC269VC, Black Headphone Out, Left] audio balance slider problem

2017-04-15 Thread Gabriel Longo

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683096

Title:
  [37722QP, Realtek ALC269VC, Black Headphone Out, Left] audio balance
  slider problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

I have already mentioned that I'm not gonna share the output of `sudo
lspci -vnvn` unless absolutely necessary to resolve this issue, so I'm
changing the bug status to 'Confirmed', as instructed by brad-figg.

If you believe that the output of `sudo lspci -vnvn` is absolutely
necessary to resolve this issue, please explain why.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

I also had a similar, but maybe not identical issue today.

First, several application windows grayed out, one after another. Then
my system slowed down and after a few seconds became completely
unresponsive. Of course, I couldn't switch to VT1 too. I waited for more
than 10 minutes, but nothing changed, so I restarted the laptop.

What is unusual about the situation is that during the freeze there was
no HDD activity (the blinkenlight didn't blink even once and I didn't
hear my HDD) and the CPU apparently did almost nothing too (my laptop's
fan was completely silent).

Unfortunately, there was nothing interesting in syslog when I checked it
after the restart, and checking out dmesg after a restart wouldn't help
much too.

I never experienced anything like this when I was on xenial. On xenial,
usually, when I was running out of memory and swap, my system would
become very, but not completely unresponsive, the fan would spin like
crazy, the blinkenlight responsible for HDD activity would blink like
crazy, and of course I would be able to hear the HDD too. I would
usually switch to VT1, patiently wait until the switch actually
happened, then type a command to kill the offending process. The 2
incidents that happened to me today (after I had upgraded to zesty) were
nothing like this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683095] [NEW] rsync has -C / --cvs-exclude enabled permanently

2017-04-15 Thread jimlovell777

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683095

Title:
  rsync has -C / --cvs-exclude enabled permanently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1683095/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683094] [NEW] Upgrade conflict DNS broken between Network Manager and systemd-resolved

2017-04-15 Thread Brian Burch

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683094

Title:
  Upgrade conflict DNS broken between Network Manager and systemd-
  resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683094/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (amd64) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_01-06-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683093] [NEW] server not found on facebook, morningstar.com, and noobslab.com even on usb stick.

2017-04-15 Thread John-bjergen

Public bug reported:

no problem on 16.04 problem with all browsers used.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: evince 3.24.0-0ubuntu1
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:50:46 2017
InstallationDate: Installed on 2015-04-24 (722 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to zesty on 2017-04-13 (2 days ago)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683093

Title:
  server not found on facebook,morningstar.com,and noobslab.com even on
  usb stick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1683093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

2017-04-15 Thread themusicgod1

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683092] [NEW] uBuntu 17 instalation failed

2017-04-15 Thread biMp

Public bug reported:

Failed to install clean install ubuntu 17

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9 [modified: 
lib/partman/automatically_partition/question]
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
CasperVersion: 1.380
Date: Sun Apr 16 09:46:43 2017
InstallCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity  quiet splash --- persistent 
BOOT_IMAGE=/casper/vmlinuz.efi
LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683092

Title:
  uBuntu 17 instalation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1683092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window

2017-04-15 Thread Eugenio Perea

I have the same issue: the tablet works but is not detected by System Settings. 
Is there a workaround, should I wait until the bug is fixed, or do something 
else? 
I've updated the kernel driver and the X driver, but I'm holding off installing 
libwacom until I understand what is the best course of action.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575887

Title:
  Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties
  window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1298272] Re: gnome-photos doesnt show albums

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-photos (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298272

Title:
  gnome-photos doesnt show albums

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-photos/+bug/1298272/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1683091

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

** Description changed:

  Upgraded from xenial to zesty recently.
  
  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole system
  froze for something like 30 seconds (I tried to switch to VT1 to no
  avail), then the process got killed.
  
  Well, not exactly killed.
  
  The grayed-out window is still there, `xprop | grep PID` and clicking on
  it gives:
  
  ```
  _NET_WM_PID(CARDINAL) = 13
  ```
  
  PID 13 is a child of kthreadd:
  
  ```
  $ ps -A | awk '$1 == "13" { print }'
-13 ?00:00:00 cpuhp/1
+    13 ?00:00:00 cpuhp/1
  ```
  
  And this is how the relevant part of `ps -AH` with the "killed" process
  looks like:
  
  ```
-  5709 pts/11   00:00:00   firejail
-  5710 pts/11   00:00:00 firejail
-  5725 pts/11   00:00:00   bash
-  5736 pts/11   00:56:49 firefox 
-  5769 pts/11   00:00:24   tor
+  5709 pts/11   00:00:00   firejail
+  5710 pts/11   00:00:00 firejail
+  5725 pts/11   00:00:00   bash
+  5736 pts/11   00:56:49 firefox 
+  5769 pts/11   00:00:24   tor
  ```
+ 
+ EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
+ the output above as ps.log.
  
  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.
  
  I also add the output of `cat /proc/version_signature` as version.log.
  
  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.
  
  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

** Attachment added: "ps.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862905/+files/ps.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862904/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] [NEW] The whole system froze for something like 30 seconds, then a process got killed

Public bug reported:

Upgraded from xenial to zesty recently.

I was using a Firefox instance, one which is a part of Tor Browser
Bundled. First, the application window grayed out, then the whole system
froze for something like 30 seconds (I tried to switch to VT1 to no
avail), then the process got killed.

Well, not exactly killed.

The grayed-out window is still there, `xprop | grep PID` and clicking on
it gives:

```
_NET_WM_PID(CARDINAL) = 13
```

PID 13 is a child of kthreadd:

```
$ ps -A | awk '$1 == "13" { print }'
   13 ?00:00:00 cpuhp/1
```

And this is how the relevant part of `ps -AH` with the "killed" process
looks like:

```
 5709 pts/11   00:00:00   firejail
 5710 pts/11   00:00:00 firejail
 5725 pts/11   00:00:00   bash
 5736 pts/11   00:56:49 firefox 
 5769 pts/11   00:00:24   tor
```

I checked syslog and dmesg. Both of them have an interesting and
identical message, which I add as dmesg.log.

I also add the output of `cat /proc/version_signature` as version.log.

I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
share it unless absolutely necessary.

The crashed process will be there for something like 2 or 3 days at
least (I don't restart my laptop often), so feel free to ask me to
manipulate or query it somehow, if necessary.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862903/+files/dmesg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (i386) - tests ran: 7, failed: 0

tests ran:   7, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_23-50-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2017-04-15 Thread Piotr Dąbrowski

Related: https://bugzilla.kernel.org/show_bug.cgi?id=195299

** Bug watch added: Linux Kernel Bug Tracker #195299
   http://bugzilla.kernel.org/195299

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682744

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683087] Re: when i started to name my computer it gives me mistake

2017-04-15 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the instructions at
https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry
your installation with new media.  In the event that is is not in fact
an error with your installation media please set the bug's status back
to New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

** Tags added: ident-mismatch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683087

Title:
  when i started to name my computer it gives me mistake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1683087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683088] [NEW] first ubuntu installer on a brand new laptop shows failure message

2017-04-15 Thread Japan Patel

Public bug reported:

grub loader may not load the boot image

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Sun Apr 16 05:41:12 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcEnviron:
 LANGUAGE=en_IN
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683088

Title:
  first ubuntu installer on a brand new laptop  shows failure message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1683088/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683087] [NEW] when i started to name my computer it gives me mistake

2017-04-15 Thread Neo Salam

Public bug reported:

it says that cannot copy information on my hdd

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Sun Apr 16 03:00:49 2017
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid 
initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcEnviron:
 LANGUAGE=ru_RU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683087

Title:
  when i started to name my computer it gives me mistake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1683087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683086] [NEW] grub fails to install on selected device

2017-04-15 Thread Peter Jansen

Public bug reported:

I originally tried to install the 32-bit version and grub failed to
install.  I booted into another installed linux distribution, mounted
the / partition and found only one directory, @.  Inside of @ was what
is normally in the / directory (all the main directories.)  I used btrfs
for the / and /opt directories.  I moved all the files from /@ to / and
was able to get the grub (from the other distribution) to find the
ubuntu 17.04 install and add it.  The install itself worked fine, just
that grub wouldn't install, so I could only boot into it from another
grub after fixing the root partition.

The bug basically was grub couldn't be installed on the chosen device.
Choose any other device or partition to install grub, it still fails.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9 [modified: 
lib/partman/automatically_partition/question]
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
CasperVersion: 1.380
Date: Sat Apr 15 19:32:58 2017
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683086

Title:
  grub fails to install on selected device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1683086/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

2017-04-15 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633162

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1633162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2017-04-15 Thread Piotr Dąbrowski

Connecting to 5GHz network also causes driver error on Intel(R) Dual
Band Wireless AC 7265, REV=0x210 (on Asus UX305FA). It seems like only
Ubuntu 17.04 is affected. I've tried the same on Ubuntu 16.10, Ubuntu
16.04 and Windows 10 - the problem does not occur on any of these.

I can upload more info if needed (but I could use some help on how to
gather it).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682744

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1297286] Re: Wireless connection keeps disconnecting

2017-04-15 Thread gabybosetti

ALso in Ubuntu 17

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297286

Title:
  Wireless connection keeps disconnecting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (amd64) - tests ran: 20, failed: 0

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_22-30-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683083] [NEW] Sound Blaster Z Card does not work

2017-04-15 Thread di35trat

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683083

Title:
  Sound Blaster Z Card does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683083/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682744

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683082] [NEW] package blueman 2.0.4-1ubuntu2 failed to install/upgrade: package blueman is not ready for configuration cannot configure (current status 'half-installed')

2017-04-15 Thread Allan L McCoy

Public bug reported:

  python3-ptyprocess python3-renderpm python3-reportlab
  python3-reportlab-accel snap-confine ubuntu-core-launcher xsane-common
0 upgraded, 0 newly installed, 173 to remove and 1 not upgraded.
3 not fully installed or removed.
Need to get 0 B/2,782 kB of archives.
After this operation, 5,982 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 1915149 files and directories currently installed.)
Removing gcc-4.8-base:i386 (4.8.5-4ubuntu2) ...
Removing gcc-4.9-base:i386 (4.9.3-13ubuntu2) ...
Removing libgtk-3-0:i386 (3.18.9-1ubuntu3.2) ...
dpkg: unrecoverable fatal error, aborting:
 fork failed: Cannot allocate memory
E: Sub-process /usr/bin/dpkg returned an error code (2)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: blueman 2.0.4-1ubuntu2
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
Date: Sat Apr 15 18:42:51 2017
DuplicateSignature:
 package:blueman:2.0.4-1ubuntu2
 Setting up ntpdate (1:4.2.8p4+dfsg-3ubuntu5.4) ...
 dpkg: error processing package blueman (--configure):
  package blueman is not ready for configuration
ErrorMessage: package blueman is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2014-10-03 (925 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: blueman
Title: package blueman 2.0.4-1ubuntu2 failed to install/upgrade: package 
blueman is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: Upgraded to xenial on 2016-07-29 (260 days ago)

** Affects: blueman (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683082

Title:
  package blueman 2.0.4-1ubuntu2 failed to install/upgrade: package
  blueman is not ready for configuration  cannot configure (current
  status 'half-installed')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1683082/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681884

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681175

Title:
  network-manager don't work normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681175/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683080] [NEW] package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2017-04-15 Thread Edward G Prentice

Public bug reported:

failed during 'sudo aptitude dist-upgrade'

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libcuda1-352 361.45.11-0ubuntu0.16.04.1
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
Date: Sat Apr 15 15:37:45 2017
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2015-03-23 (754 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: nvidia-graphics-drivers-361
Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

** Affects: nvidia-graphics-drivers-361 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check third-party-packages zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683080

Title:
  package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1683080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683081] [NEW] package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2017-04-15 Thread Edward G Prentice

Public bug reported:

failed during 'sudo aptitude dist-upgrade'

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1
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
Date: Sat Apr 15 15:37:50 2017
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2015-03-23 (754 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: nvidia-graphics-drivers-361
Title: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

** Affects: nvidia-graphics-drivers-361 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check third-party-packages zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683081

Title:
  package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1683081/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683074] Re: Backlight change randomly

2017-04-15 Thread Colin Watson

** Project changed: launchpad => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683074

Title:
  Backlight change randomly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1683074/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683074] [NEW] Backlight change randomly

You have been subscribed to a public bug:

Since version 16.10 my acer laptop change its backlight randomly

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
Backlight change randomly
https://bugs.launchpad.net/bugs/1683074
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_22-04-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677198] Re: OpenVPN not Working in 17.04

2017-04-15 Thread Marcin Wojcik

Installed Ubuntu Mate 17.04 today. Tried also Ubuntu 17.04. OpenVPN
created by importing *.ovpn file. Does not work with the same error
reported by others. Did not try on 16.10 or 16.04LTS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677198

Title:
  OpenVPN not Working in 17.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1677198/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

2017-04-15 Thread Petr Dlouhý

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
Bugs, which is subscribed to 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1683077/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683079] [NEW] package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to install/upgrade: v nové verzi balíku není žádný skript - končím

2017-04-15 Thread Petr Dlouhý

Public bug reported:

Problem dialog raised after upgrade to Ubuntu 17.04.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2
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: Fri Apr 14 18:53:35 2017
ErrorMessage: v nové verzi balíku není žádný skript - končím
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: ubuntu-app-launch
Title: package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to 
install/upgrade: v nové verzi balíku není žádný skript - končím
UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago)

** Affects: ubuntu-app-launch (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683079

Title:
  package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to
  install/upgrade: v nové verzi balíku není žádný skript - končím

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1683079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683078] [NEW] package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to install/upgrade: v nové verzi balíku není žádný skript - končím

2017-04-15 Thread Petr Dlouhý

Public bug reported:

Problem dialog raised after upgrade to Ubuntu 17.04.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2
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: Fri Apr 14 18:53:35 2017
ErrorMessage: v nové verzi balíku není žádný skript - končím
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: ubuntu-app-launch
Title: package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to 
install/upgrade: v nové verzi balíku není žádný skript - končím
UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago)

** Affects: ubuntu-app-launch (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683078

Title:
  package ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu2 failed to
  install/upgrade: v nové verzi balíku není žádný skript - končím

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1683078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1641974] Re: xinput setting is reseted after a hibernation

2017-04-15 Thread t4eg

This problem disappeared on later 16.10 and 17.04.

** Changed in: xinput (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641974

Title:
  xinput setting is reseted after a hibernation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1641974/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_21-36-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)

2017-04-15 Thread hrvooje

*** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679535

Title:
  ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup  fails)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1679535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682631] Re: gnome-shell crashes in libmozjs on x86_64

Brian Vincent, thank you for taking the time to help make Ubuntu better!

I've uploaded your change and some related changes to the zesty-proposed
queue where it will need to be manually approved by a member of the
Stable Release Update team before it will be available for testing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682631

Title:
  gnome-shell crashes in libmozjs on x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1682631/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

2017-04-15 Thread Reupen Shah

** 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
+

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509562

Title:
  no icons for menu, folders, directories, files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682631] Re: gnome-shell crashes in libmozjs on x86_64

** Description changed:

  Impact
  --
- This enables build tests to run and pass. This was done by building without 
-fstrict-aliasing and skipping 3 ICU tests. (Those 3 tests don't work right 
with the system ICU that Ubuntu 17.04 is using to build mozjs38.)
+ This enables build tests to run on all architectures. The tests now fail the 
build on all architectures except arm64, ppc64el and s390x. (On arm64 and 
ppc64el, the tests fail and I wasn't able to test s390x before uploading. This 
means that there is a decent chance the gnome-shell does not work on these 
architectures but Ubuntu GNOME only officially supports gnome-shell on i386 and 
amd64.)
+ 
+ This was done by building without -fstrict-aliasing and skipping 3 ICU
+ tests. (Those 3 tests don't work right with the system ICU that Ubuntu
+ 17.04 is using to build mozjs38.)
  
  Test Case
  -
  1. Since the tests will now fail the build if they fail, make sure that 
mozjs38 builds on all architectures
  
  2. Install the new version and make sure GNOME Shell seems to still
  work.
  
  Regression Potential
  
  I don't know much about strict-aliasing, but I believe it's safer to disable 
it on a large old codebase like this. Since it makes the build tests pass now, 
it seems like disabling strict-aliasing may fix some bugs.
  
  Other Info
  --
  mozjs is the SpiderMonkey JavaScript engine from Firefox. This version is 
from Firefox 38.
  
  Original Bug Description
  
  A friend and I are seeing frequent gnome-shell crashes on Ubuntu 17.04 on 3 
different computers.  Here's an example:
  
  Apr 12 22:35:00  kernel: gnome-shell[2592]: segfault at 10 ip
  7f0e3ccc26d7 sp 7ffdd31b4d90 error 4 in
  libmozjs-38.so.0.0.0[7f0e3c93e000+6c7000]
  
  I've analyzed the issue for a while and I actually believe I've found
  the solution.
  
  If I simply download the apt source package and build it using gcc
  6.3.0, and then go to js/src and execute:
  
  $ make check-jstests | grep -c UNEXPECTED-FAIL
  49
  
  Upon examination, those test failures are all because of segfaults.
  
  If I rebuild and retests with gcc 5, all tests pass.
  
  I've discovered that adding the flag -fno-strict-aliasing causes all of
  the tests to pass with gcc 6.

** Changed in: mozjs38 (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682631

Title:
  gnome-shell crashes in libmozjs on x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1682631/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

2017-04-15 Thread Reupen Shah

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683066

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666041] Re: package libsigsegv2:amd64 2.10-4 failed to install/upgrade: package libsigsegv2:amd64 is already installed and configured

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dpkg (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666041

Title:
  package libsigsegv2:amd64 2.10-4 failed to install/upgrade: package
  libsigsegv2:amd64 is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1666041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683072] [NEW] dell

2017-04-15 Thread kassidy

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683072

Title:
  dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1683072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-04-15 Thread bwat47

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682041] onibi (amd64) - tests ran: 64, failed: 0