[Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

2024-04-24 Thread Anderson Soares Ferreira
Hello Kleber,

I've installed the last kernel update (5.15.0-106.116) and it's solved the 
problem.
Now FCoE interfaces are correctly detected and the system got storage disks 
access back.

Regards,

Anderson

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

Title:
  Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

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


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

Re: [Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

2024-04-04 Thread Anderson Soares Ferreira
Hello, Kleber.

Thank you for the instructions for installing the proposed kernel
packages.  Unfortunately, booting the system with the kernel 5.15.0-102.112
resulted in the same behavior, fcoe interfaces offline and reporting the
FC-IDs as 0x.
If you need further information, please let me know.

Best regards,


Anderson Soares Ferreira - anderson.soa...@embrapa.br
Núcleo de Tecnologia da Informação - NTI
Embrapa Territorial
Tel.: (19) 3211-6200


Em qua., 3 de abr. de 2024 às 09:49, Kleber Sacilotto de Souza <
2057...@bugs.launchpad.net> escreveu:

> Hello Anderson,
>
> Thank you for reporting the issue. We have a new kernel for 22.04
> (version 5.15.0-102.112) that is about to be released in the next few
> days. Could you please test it again with this kernel and report the
> results? You can either enable -proposed in your system and update the
> kernel, or wait until it gets promoted to -updates and a simple dist-
> upgrate will update the kernel.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2057960
>
> Title:
>   Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   Since I've upgraded my server's to Ubuntu 22.04.4  I'm facing problems
> to make my fcoe setup to work correctly.
>   Firstly, some context. We have a HPE Synergy appliance with a bunch of
> Synergy 480 Gen10 servers still running Ubuntu 20.04.
>   Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi
> Function network adapters with two of them dedicated to storage
> communication through FCoE.
>
>   Recently, I've upgraded one of them to Ubuntu 22.04 and realized that
> after the upgrade, all the Fibre Channel LUNs have disappeared. During the
> diagnostic process I noticed that both network (bnx2x) and fcoe (fcoe,
> bnx2fc) kernel drivers have been loaded properly, FCoE vlans were correctly
> detected by fcoe-utils, but there was no connection between the server and
> the storage and the server could not detect any LUN.
>   I also noticed that fcoeadm was reporting the following status:
>
>   # fcoeadm -i
>   Description:  BCM57840 NetXtreme II Ethernet Multi Function
>   Revision: 11
>   Manufacturer: Broadcom Inc. and subsidiaries
>   Serial Number:9440C953B7F0
>
>   Driver:   bnx2x Unknown
>   Number of Ports:  1
>
>   Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over
> ens3f2.4093-fco
>   OS Device Name:host2
>   Node Name: 0x1a3d2725
>   Port Name: 0x1a3d2724
>   Fabric Name:   0x0
>   Speed: 20 Gbit
>   Supported Speed:   1 Gbit, 10 Gbit
>   MaxFrameSize:  2048 bytes
>   FC-ID (Port ID):   0x
>   State: Offline
>   Description:  BCM57840 NetXtreme II Ethernet Multi Function
>   Revision: 11
>   Manufacturer: Broadcom Inc. and subsidiaries
>   Serial Number:9440C953B7F0
>
>   Driver:   bnx2x Unknown
>   Number of Ports:  1
>
>   Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over
> ens3f3.4094-fco
>   OS Device Name:host3
>   Node Name: 0x1a3d2727
>   Port Name: 0x1a3d2726
>   Fabric Name:   0x0
>   Speed: 20 Gbit
>   Supported Speed:   1 Gbit, 10 Gbit
>   MaxFrameSize:  2048 bytes
>   FC-ID (Port ID):   0x
>   State: Offline
>
>   Although most of information displayed was correct, the port state was
>   always offline (what explains no storage connectivity) and the FC-ID
>   reported was 0x for both interfaces.
>
>   Supposing that something went wrong during the upgrade process, I
> decided to make a fresh install of the server and, for my surprise, the
> fcoe ports went online and all luns were detected correctly.
>   Unfortunately, the ports went offline again after a dist-upgrade.
>   Trying to understand what was happening I performed another fresh
> install of the Ubuntu 22.04, but this time collecting some information
> about kernel and packages versions from before and after dist-upgrade.
>   What I discovered was that all packages related (fcoe-utils, lldpad) had
> the same versions before and after, the only exception was the kernel
> itself. Before the dist-upgrade the kernel in use was 5.15.0-25-generic and
> after dist-upgrade the kernel was 5.15.0-100-generic.
>   Suspecting a kernel problem I installed and booted diff

[Bug 2057960] [NEW] Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

2024-03-14 Thread Anderson Soares Ferreira
Public bug reported:

Since I've upgraded my server's to Ubuntu 22.04.4  I'm facing problems to make 
my fcoe setup to work correctly.
Firstly, some context. We have a HPE Synergy appliance with a bunch of Synergy 
480 Gen10 servers still running Ubuntu 20.04. 
Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi Function 
network adapters with two of them dedicated to storage communication through 
FCoE.

Recently, I've upgraded one of them to Ubuntu 22.04 and realized that after the 
upgrade, all the Fibre Channel LUNs have disappeared. During the diagnostic 
process I noticed that both network (bnx2x) and fcoe (fcoe, bnx2fc) kernel 
drivers have been loaded properly, FCoE vlans were correctly detected by 
fcoe-utils, but there was no connection between the server and the storage and 
the server could not detect any LUN.
I also noticed that fcoeadm was reporting the following status:

# fcoeadm -i
Description:  BCM57840 NetXtreme II Ethernet Multi Function
Revision: 11
Manufacturer: Broadcom Inc. and subsidiaries
Serial Number:9440C953B7F0

Driver:   bnx2x Unknown
Number of Ports:  1

Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f2.4093-fco
OS Device Name:host2
Node Name: 0x1a3d2725
Port Name: 0x1a3d2724
Fabric Name:   0x0
Speed: 20 Gbit
Supported Speed:   1 Gbit, 10 Gbit
MaxFrameSize:  2048 bytes
FC-ID (Port ID):   0x
State: Offline
Description:  BCM57840 NetXtreme II Ethernet Multi Function
Revision: 11
Manufacturer: Broadcom Inc. and subsidiaries
Serial Number:9440C953B7F0

Driver:   bnx2x Unknown
Number of Ports:  1

Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f3.4094-fco
OS Device Name:host3
Node Name: 0x1a3d2727
Port Name: 0x1a3d2726
Fabric Name:   0x0
Speed: 20 Gbit
Supported Speed:   1 Gbit, 10 Gbit
MaxFrameSize:  2048 bytes
FC-ID (Port ID):   0x
State: Offline

Although most of information displayed was correct, the port state was
always offline (what explains no storage connectivity) and the FC-ID
reported was 0x for both interfaces.

Supposing that something went wrong during the upgrade process, I decided to 
make a fresh install of the server and, for my surprise, the fcoe ports went 
online and all luns were detected correctly.
Unfortunately, the ports went offline again after a dist-upgrade.
Trying to understand what was happening I performed another fresh install of 
the Ubuntu 22.04, but this time collecting some information about kernel and 
packages versions from before and after dist-upgrade.
What I discovered was that all packages related (fcoe-utils, lldpad) had the 
same versions before and after, the only exception was the kernel itself. 
Before the dist-upgrade the kernel in use was 5.15.0-25-generic and after 
dist-upgrade the kernel was 5.15.0-100-generic.
Suspecting a kernel problem I installed and booted different kernel versions 
from 5.15.0-25 and 5.15.0-100 and discovered that the problem probably was 
introduced with kernel 5.15.0-94, since it is the first version showing the 
describe behavior.
Looking at the changelog of linux-modules package, I noticed some changes on 
fcoe and other scsi modules, right after the 5.15.0-91 version. 
Could those changes be the cause of the behavior observed on my server or just 
a coincidence? Is there any fix to it?

Thanks in advance.

Anderson

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-94-generic 5.15.0-94.104
ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136
Uname: Linux 5.15.0-94-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 14 11:03 seq
 crw-rw 1 root audio 116, 33 Mar 14 11:03 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
Date: Thu Mar 14 14:57:14 2024
HibernationDevice: RESUME=UUID=c4f1e832-fa46-4c58-913e-2093e8a4a4f0
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 002: ID 0424:2660 Microchip Technology, Inc. (formerly SMSC) Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M

[Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2024-03-05 Thread james anderson
one of the best information be like the  https://rugnroll.com.au

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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


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

[Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2024-03-05 Thread james anderson
thanks for sharing you can visit to the https://advancewithai.net/ai-
image-generators/leonardo-ai.html

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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


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

[Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

2022-05-02 Thread Anderson Luiz Alves
Bluetooth worked with linux-firmware 20220329.git681281e4-0ubuntu3.

** Tags added: verification-done-jammy

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

Title:
  No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

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


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

[Bug 1970916] [NEW] bluetooth not working in 22.04

2022-04-29 Thread Anderson Luiz Alves
Public bug reported:

Bluetooth is not working in Ubuntu 22.04 jammy.
It works on 20.04.

dmesg says:
Bluetooth: Patch file not found ar3k/AthrBT_0x3101.dfu

version:
linux-firmware 20220329.git681281e4-0ubuntu1
linux-image-5.15.0-27-generic
linux-modules-5.15.0-27-generic
linux-modules-extra-5.15.0-27-generic

hardware:
Dell Inspiron 5437
06:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)

** Affects: linux-firmware (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/1970916

Title:
  bluetooth not working in 22.04

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


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

[Bug 1965843] [NEW] Alto consumo de processamento ao executar chrome + youtube

2022-03-21 Thread Anderson Simplício
Public bug reported:

Desde o kernel 5.4.0-77 sempre que o chrome está em excução existe um excesso 
de cosumo de processamento.
Presumo que seja por causa do kernel pois ao utilizar a versão 5.4.0-77 a taxa 
de processamento fica em níveis baixos.

Meu sistema:
Linux Mint 20.2 Cinnamon
versão do Cinamon 5.0.7
kernel linux : 5.4.0-105-generic (Testando para verificar se houve melhora)
Processador: Intel© Core™ i7-2620M CPU @ 2.70GHz × 2
RAM: 7.7 GiB
HD_SSD:481.2 GB
Placa de Video: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller
Placa de video: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] (prog-if 00 [VGA controller])

** 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/1965843

Title:
  Alto consumo de processamento ao executar chrome + youtube

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


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

[Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds

2021-12-07 Thread Craig Anderson
I have the same issue. It's preventing me from doing some fairly
important things, without an obvious workaround at the moment.

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

Title:
  OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds

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


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

[Bug 1948481] Re: sustem locks up when trying to move icon (Firefox) up list on left update 2021-10

2021-10-24 Thread Frank Anderson
frank@frank-desktop:/proc$ cat version
Linux version 5.13.0-1008-raspi (buildd@bos02-arm64-018) (gcc (Ubuntu 
11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #9-Ubuntu SMP 
PREEMPT Wed Sep 29 08:27:44 UTC 2021
frank@frank-desktop:/proc$ 


** Package changed: ubuntu => desktop

** Changed in: desktop
   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/1948481

Title:
  sustem locks up when trying to move icon (Firefox) up list on left
  update 2021-10

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


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

[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)

2021-10-22 Thread Ryan Anderson
This is still broken on impish when running i3 under X11.

Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]: 
/etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not 
found
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]: 
/etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5658]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

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

Title:
  ssh-agent fails to start (has_option: command not found)

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


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

[Bug 1948481] [NEW] sustem locks up when tryiny to move icon (Firefox) up list on left update 2021-10

2021-10-22 Thread Frank Anderson
Public bug reported:

System constantly locks up when trying to move icons on the bar at the
left. Just updated to 2021-10 on Raspberry Pi 400. Even running system
monitor, it just halts! This is a MAJOR PROBLEM! Only way out it to
disconnect power! Instantly locks up when icon get to the top of the
list and the list does NOT scroll higher! thanks!

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: locks system up

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

Title:
  sustem locks up when tryiny to move icon (Firefox) up list on left
  update 2021-10

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


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

[Bug 1944481] Re: Distrust "DST Root CA X3"

2021-09-24 Thread Collin Anderson
Yes, I'm running into the issue above, where a windows server is not
correctly serving the new certificate chain (which means it's going to
fail for everyone else on Sept 30th.) Windows server might need an
update or might need to be rebooted.
https://community.certifytheweb.com/t/upcoming-expiry-of-dst-root-
ca-x3-and-r3-intermediate-for-lets-encrypt/1480

In the meantime, from the ubuntu point of view, how do I roll this
update back? The cert is still valid for another week. `sudo apt install
ca-certificates=20210119~20.04.1` says `E: Version '20210119~20.04.1'
for 'ca-certificates' was not found`.

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

Title:
  Distrust "DST Root CA X3"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1944481/+subscriptions


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

[Bug 49613] Re: [MASTER] Adobe Flash does not support WMODE (Flash content always rendered on top of web pages)

2021-09-01 Thread Anderson Cavalcante
Muito interessante, eu fiz o teste no site abaixo e me parece normal.

https://manutencaoemcelular.com.br/

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

Title:
  [MASTER] Adobe Flash does not support WMODE (Flash content always
  rendered on top of web pages)

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


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

[Bug 1938810] [NEW] Reverse lookup of 127.0.0.1 does not work

2021-08-03 Thread Nick Anderson
Public bug reported:

I expected a reverse lookup of 127.0.0.1 to return localhost, instead it
returned nothing.

```
root:~# dig -x 127.0.0.1

; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60017
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Aug 03 09:25:20 CDT 2021
;; MSG SIZE  rcvd: 51

```

If I explicitly lookup using 127.0.0.1 instead of the default
127.0.0.53, I do get a record as expected.

```
root:~# dig -x 127.0.0.1 @127.0.0.1

; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1 @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51602
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa. 10800   IN  PTR localhost.

;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Aug 03 09:25:15 CDT 2021
;; MSG SIZE  rcvd: 74

```

I have an entry in /etc/hosts.

```
root:~# grep 127.0.0.1 /etc/hosts
127.0.0.1   localhost
```

Looks like unbound which seems to work as expected is running on
127.0.0.1:53, and systemd-resolv which is not working is on
127.0.0.53:53.

```
tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN  
1839/unbound
tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN  
1511/systemd-resolv 

```

I am running 20.04.2:

```
root:~# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
```

With systemd version 245.4-4ubuntu3.7

```
root@:~# apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3.7
  Candidate: 245.4-4ubuntu3.11
  Version table:
 245.4-4ubuntu3.11 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 *** 245.4-4ubuntu3.7 100
100 /var/lib/dpkg/status
 245.4-4ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
 237-3ubuntu10.50 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages

```

** Affects: systemd (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/1938810

Title:
  Reverse lookup of 127.0.0.1 does not work

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


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

[Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM

2021-07-30 Thread Dean Anderson
I have a Dell Precision 7560, with this issue.  I just installed the
proposed 5.10.0-1041 oem kernel package for testing.

While it did fix the boot issue, the e1000e driver is failing and I
cannot use the wired network interface.

Here is the dmesg output of `modprobe e1000e`:

[  293.106059] e1000e: Intel(R) PRO/1000 Network Driver
[  293.106059] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[  293.106442] e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[  293.194836] e1000e :00:1f.6: The NVM Checksum Is Not Valid
[  293.240151] e1000e: probe of :00:1f.6 failed with error -5

Previously I was working around the e1000e NVM issues by building the
e1000e module from the 3.8.7 source package from sourceforge.  Applying
the patches from https://bugzilla.kernel.org/show_bug.cgi?id=213667 to
the 5.10.1038-oem kernel source and re-building the e1000e module also
solved the issue.

** Bug watch added: Linux Kernel Bug Tracker #213667
   https://bugzilla.kernel.org/show_bug.cgi?id=213667

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

Title:
  e1000e blocks the boot process when it tried to write checksum to its
  NVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions


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

[Bug 1800836] Re: systemd-networkd doesn't process IPv6 RA properly

2021-07-27 Thread Tore Anderson
This bug is still present on Ubuntu 18.04.5 LTS with systemd
237-3ubuntu10.50. Please reopen.

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

Title:
  systemd-networkd doesn't process IPv6 RA properly

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


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

[Bug 1931455] Re: open-iscsi fails to create nodes directory

2021-06-11 Thread Logan M Anderson
I'm having issues recreating the problem (i.e. it's working like it
should), so take this with a grain of salt.

On a fresh Ubuntu 20.04.2 install, fully updated:

> sudo apt update -y && sudo apt full-upgrade -y && sudo apt auto-remove
-y

I would send the discovery command:

> sudo iscsiadm -m discovery -t sendtargets -p 192.168.35.99

And because the open-iscsi service wasn't running, this command would
not discover anything.  As soon as I populated the folder and restart
the service:

> sudo mkdir -p /etc/iscsi/nodes/something/
> sudo systemctl restart open-iscsi.service iscsid.service

I would get SOMETHING out of the discovery command:

>sudo iscsiadm -m discovery -t sendtargets -p 192.168.35.99
192.168.35.99:3260,1 iqn.2014-04.com.junos:tlv-13691u-rp:iscsi.initserver.387862


But like I said I am having trouble recreating this and it seems to be working 
as intended now.  I don't know if there was an update between June 4th and June 
10th but mostly I'm just happy it's working.

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

Title:
  open-iscsi fails to create nodes directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1931455/+subscriptions

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

[Bug 1931455] Re: open-iscsi fails to create nodes directory

2021-06-10 Thread Logan M Anderson
Hi Simon,

I would expect that, but the service cannot start or be invoked as
written without that directory.  And that service is what should
generate that directory.  Like I said: chicken/egg.

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

Title:
  open-iscsi fails to create nodes directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1931455/+subscriptions

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

[Bug 1931455] [NEW] open-iscsi fails to create nodes directory

2021-06-09 Thread Logan M Anderson
Public bug reported:

open-iscsi will not run without the nodes directory, but the nodes
directory is created and populated by the open-iscsi service.
Chicken/Egg.

Mitigated by creating and populating the nodes with junk directories to
be deleted later:

linuxsudoer@banana01ubu:/etc/iscsi$ sudo systemctl status open-iscsi.service
● open-iscsi.service - Login to default iSCSI targets
 Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2021-06-08 19:05:21 UTC; 25min ago
>├─ ConditionDirectoryNotEmpty=|/etc/iscsi/nodes was not met
 └─ ConditionDirectoryNotEmpty=|/sys/class/iscsi_session was not met
   Docs: man:iscsiadm(8)
 man:iscsid(8)

** Affects: open-iscsi (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/1931455

Title:
  open-iscsi fails to create nodes directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1931455/+subscriptions

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

[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-06-03 Thread Thomas Anderson
Same issue with the latest stable kernel published today:

linux-headers-5.12.9-051209-generic : Depends: libc6 (>= 2.33) but
2.31-0ubuntu9.2 is installed

Ubuntu Server 20.04.2 LTS machine.

Please fix it. I don't feel comfortable installing 3rd party Kernels and I need 
to use mainline kernel to be able to use the iGPU on my 11gen Intel CPU for 
rendering. 
Thanks in advance!!

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

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

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

[Bug 1926775] [NEW] package linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.8.0-50-generic, o script pre-removal retornou e

2021-04-30 Thread Anderson Mendes de Almeida
Public bug reported:

Error when run "sudo apt-get purge linux*5.8*".

Command given by AMD to fix some bugs.

https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-
linux-20-45

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
edac_mce_amd snd_hda_intel snd_intel_dspcfg btusb snd_hda_codec btrtl btbcm 
snd_hda_core snd_usb_audio btintel snd_usbmidi_lib bluetooth rapl wmi_bmof 
k10temp mac_hid it87 hwmon_vid videodev mc i2c_piix4 r8169 realtek wmi 
gpio_amdpt gpio_generic
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 30 11:30:12 2021
ErrorMessage: o subprocesso instalado, do pacote linux-image-5.8.0-50-generic, 
o script pre-removal retornou erro do status de saída 1
InstallationDate: Installed on 2020-08-30 (242 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: linux-signed-hwe-5.8
Title: package linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 failed to 
install/upgrade: o subprocesso instalado, do pacote 
linux-image-5.8.0-50-generic, o script pre-removal retornou erro do status de 
saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 failed to
  install/upgrade: o subprocesso instalado, do pacote linux-
  image-5.8.0-50-generic, o script pre-removal retornou erro do status
  de saída 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926775/+subscriptions

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

[Bug 1918081] [NEW] gtk showswarning from soffice about clearlooks css

2021-03-07 Thread David Anderson
Public bug reported:

This shows the message and I made the fix below and the warning went
away.

(soffice:1199957): Gtk-WARNING **: 16:01:27.425: Theme parsing error:
gtk-widgets.css:1214:18: Not using units is deprecated. Assuming 'px'.

/usr/share/themes/Clearlooks-Phenix/gtk-3.0/gtk-widgets.css

 1211 combobox > .linked > button.combo:disabled:last-child {
   1212 border-image-width: 3px 3px 4px 0;
   1213 border-radius: 0 3px 3px 0;
-  1214 border-width: 0 1;
+  1214 border-width: 0 1px;
   1215 }

clearlooks-phenix-theme 7.0.1-3

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: clearlooks-phenix-theme 7.0.1-3 [modified: 
usr/share/themes/Clearlooks-Phenix/gtk-3.0/gtk-widgets.css]
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Mar  7 16:22:37 2021
InstallationDate: Installed on 2015-11-19 (1935 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: clearlooks-phenix-theme
UpgradeStatus: Upgraded to focal on 2020-10-02 (156 days ago)

** Affects: clearlooks-phenix-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  gtk showswarning from soffice about clearlooks css

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clearlooks-phenix-theme/+bug/1918081/+subscriptions

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

[Bug 1870189] Re: initramfs does not get loaded

2021-01-26 Thread Richard Anderson
Is there any update on this?

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

Title:
  initramfs does not get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions

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

[Bug 1885571] Re: Can't set boot kernel in GRUB on focal image

2021-01-25 Thread Richard Anderson
I noticed this happens when simply rebooting.

1. Import Focal ova image into ESXi/vSphere
2. Setup new virtual machine with little or no changes
3. Reboot via command line (shutdown -r now) or ctrl-alt-del
4. First boot after the initiated reboot results in a kernel panic (similar to 
above)
5. System reboots and boots into Ubuntu

I have this occurring on Focal OVA images with ESXI 6.5 and Fusion
11.5.7. This does not occur with Bionic or Groovy.

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

Title:
  Can't set boot kernel in GRUB on focal image

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1885571/+subscriptions

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

[Bug 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded

2020-12-14 Thread Tore Anderson
Probably. My (fully updated) 20.04.1 LTS box is still at version
1.18.0-2build1, though.

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+subscriptions

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

[Bug 1906986] [NEW] defective ir-keytable udev rule → custom keytable does not get loaded

2020-12-06 Thread Tore Anderson
Public bug reported:

ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-keytable.rules
containing the following rule:

ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
/etc/rc_maps.cfg -s $name"

After upgrading to Focal, this does not get triggered at boot, nor if I
(re)insert my receiver when the system is running. Therefore, the custom
keytable does not get loaded.

This is the udev events that occur when I insert the receiver:

$ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1195.829011] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
KERNEL[1195.834989] add  /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 
(usb)
KERNEL[1195.874055] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
KERNEL[1195.875019] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
KERNEL[1195.875183] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
KERNEL[1196.134164] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
KERNEL[1196.134448] bind /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 
(usb)
KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
UDEV  [1196.158923] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
UDEV  [1196.174559] add  /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 
(usb)
UDEV  [1196.194750] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
UDEV  [1196.196268] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
UDEV  [1196.197180] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
UDEV  [1196.224577] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
UDEV  [1196.231346] bind /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 
(usb)
UDEV  [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)

Note how there's no «(rc)» displayed on any of the lines, which means
that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
the above events.

I found a rule that works at https://www.mail-archive.com/linux-
me...@vger.kernel.org/msg117165.html:

ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s
$env{.rc_sysdev}"

Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file containing
this rule solves the problem; now my custom keymap is loaded at boot, as
it did before (when I was running Bionic).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec  6 18:05:06 2020
SourcePackage: v4l-utils
UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)

** Affects: v4l-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+subscriptions

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

[Bug 1903894] Re: failure to display videos at major websites using FF 82 after upgrade to 20.04

2020-11-12 Thread Eric Anderson
Olivier, yes this worked. FIXED! thank you so much for this help.
...Eric, Melbourne, FL, USA

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

Title:
  failure to display videos at major websites using FF 82 after upgrade
  to 20.04

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

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

[Bug 1903894] [NEW] failure to display videos at major websites using FF 82 after upgrade to 20.04

2020-11-11 Thread Eric Anderson
Public bug reported:

my FF will not properly display videos at facebook website, vimeo
website, twitter videos and animated gifs. several separate websites
exhibit problem. is it Ubuntu drivers? is it FF codecs?

I just upgraded to Ubuntu 20.04.01LTS.  when I first installed Unbuntu
18, I had similar problem with FF. I don't remember what I had to do to
resolve problem then, but now I have problem again with this upgrade
install. I tend to believe that Ubuntu is culprit because FF
automatically upgrades itself.

is this OS or the FF application? 
I have not tried loading other browsers to see if they exhibit same problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 82.0.3+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eric   1425 F pulseaudio
 /dev/snd/pcmC0D0p:   eric   1425 F...m pulseaudio
BuildID: 20201108180448
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 11 12:14:20 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:361
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-11-07 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.2.1 dev enp3s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp3s0 scope link metric 1000 
 192.168.2.0/24 dev enp3s0 proto kernel scope link src 192.168.2.3 metric 100
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:361
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=82.0.3/20201108180448 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.11
dmi.board.name: 8441
dmi.board.vendor: HP
dmi.board.version: 00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd06/19/2018:svnHP:pnHPSlimDesktop290-a0xxx:pvr:rvnHP:rn8441:rvr00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Desktop
dmi.product.name: HP Slim Desktop 290-a0xxx
dmi.product.sku: X6C00AA#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  failure to display videos at major websites using FF 82 after upgrade
  to 20.04

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

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

[Bug 1896904] Re: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown

2020-10-01 Thread Nathanael Anderson
I can confirm this issue with a 9260 on on Kernel .48, booting back into
.47 works.


** Attachment added: "Dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896904/+attachment/5416228/+files/9260.log

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

Title:
  Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi
  breakdown

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

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

[Bug 1889968] Re: [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes I/O errors

2020-08-01 Thread Tore Anderson
** Attachment added: "Output from 'lshw'"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+attachment/5397631/+files/lshw.txt

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

Title:
  [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes
  I/O errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+subscriptions

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

[Bug 1889968] [NEW] [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes I/O errors

2020-08-01 Thread Tore Anderson
Public bug reported:

Somewhere between 4.15.0-112-generic and 5.3.0-62-generic the kernel
config option SATA_MOBILE_LPM_POLICY was changed from 0 (the upstream
default) to 3. This is causing frequent SATA link resets, resulting in
I/O stalls and errors. For example:

ata1.00: exception Emask 0x0 SAct 0xdc SErr 0x5 action 0x6 frozen
ata1: SError: { PHYRdyChg CommWake }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/20:90:d8:62:c6/00:00:24:00:00/40 tag 18 ncq dma 16384 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/20:98:60:26:1e/00:00:00:00:00/40 tag 19 ncq dma 16384 in
 res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/08:a0:78:85:11/00:00:03:00:00/40 tag 20 ncq dma 4096 out
 res 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/10:b0:80:60:c6/00:00:24:00:00/40 tag 22 ncq dma 8192 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:b8:d0:13:ac/00:00:02:00:00/40 tag 23 ncq dma 4096 in
 res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1.00: device reported invalid CHS sector 0
ata1.00: device reported invalid CHS sector 0
sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] tag#23 Sense Key : Illegal Request [current] 
sd 0:0:0:0: [sda] tag#23 Add. Sense: Unaligned write command
sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 02 ac 13 d0 00 00 08 00
blk_update_request: I/O error, dev sda, sector 44831696 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 0
ata1: EH complete

Available workarounds:

1) downgrading to 4.15.0-*-generic
2) appending 'ahci.mobile_lpm_policy=n' to the kernel command line, where 'n' 
is either 0, 1 or 2.

The meanings of policy numbers can be found at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/ata/Kconfig?h=v5.8-rc7#n118:

0 => Keep firmware settings
1 => Maximum performance
2 => Medium power
3 => Medium power with Device Initiated PM enabled
4 => Minimum power

The computer in question is an Intel NUC DN2820FYK (running the latest
system firmware version), containing an embedded Intel Corporation Atom
Processor E3800 Series SATA AHCI Controller (rev 0e) controller. The
hard drive is a HITACHI HTS723232L9SA60.

I have confirmed that the issue persists in the latest mainline kernel
build (5.8.0-050800rc7-generic).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Sat Aug  1 10:51:29 2020
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: Upgraded to bionic on 2020-06-28 (33 days ago)

** Affects: linux-signed-hwe-5.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Kernel messages (contains further examples of the errors)"
   https://bugs.launchpad.net/bugs/1889968/+attachment/5397627/+files/dmesg.txt

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

Title:
  [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes
  I/O errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+subscriptions

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

[Bug 1889968] Re: [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes I/O errors

2020-08-01 Thread Tore Anderson
** Attachment added: "Output from 'smartctl -a /dev/sda'"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+attachment/5397632/+files/smartctl_-a__dev_sda.txt

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

Title:
  [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes
  I/O errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+subscriptions

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

[Bug 1887862] [NEW] package speedtest-cli (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/speedtest', which is also in package speedtest 1.0.0.2-1.5ae238b

2020-07-16 Thread Jay Anderson
Public bug reported:

Occurred after upgrading release to 20.04 from 18.04. Removed
'speedtest' and then was able to install 'speedtest-cli'.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: speedtest-cli (not installed)
Uname: Linux 4.9.230-89 aarch64
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
 speedtest-cli:arm64: Install
 NULL: ConfigurePending
Architecture: arm64
CasperMD5CheckResult: skip
Date: Thu Jul 16 17:06:38 2020
DpkgTerminalLog:
 Preparing to unpack .../speedtest-cli_2.1.2-2_all.deb ...
 Unpacking speedtest-cli (2.1.2-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/speedtest-cli_2.1.2-2_all.deb (--unpack):
  trying to overwrite '/usr/bin/speedtest', which is also in package speedtest 
1.0.0.2-1.5ae238b
ErrorMessage: trying to overwrite '/usr/bin/speedtest', which is also in 
package speedtest 1.0.0.2-1.5ae238b
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: speedtest-cli
Title: package speedtest-cli (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/speedtest', which is also in package speedtest 
1.0.0.2-1.5ae238b
UpgradeStatus: Upgraded to focal on 2020-07-16 (0 days ago)

** Affects: speedtest-cli (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 focal

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

Title:
  package speedtest-cli (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/speedtest', which is also in package
  speedtest 1.0.0.2-1.5ae238b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1887862/+subscriptions

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

[Bug 1886697] [NEW] Xorg crash

2020-07-07 Thread Jacob R Anderson
Public bug reported:

Reproducible on my system. Whenever my computer "sleeps" while running a
specific program (Phenix), when I return to check on the job, the
Desktop screen does not load. Alt-F2 and other routes have not been
successful in recovery the Desktop GUI or log-in. However, if I stay at
my computer and prevent the computer from sleeping, the job completes
without GUI death.  I don't know how to search the syslog, but I expect
to find something funky around something like "GUI going to sleep".

The reason I think it is a true "crash" is, despite being away from my
the PC for 1 hr, the job directory is empty. This makes me think the
computer processes were halted during the events that lead to the GUI
death.

I have played with my GPU settings. As per this NVIDIA thread
https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock-
up/79731/252, I have set my minumum clock speed to 1050mHz. This had
been successful up until this point at preventing a different issue not
related to this bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  7 13:26:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
 nvidia, 440.100, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:13a2]
InstallationDate: Installed on 2020-05-26 (41 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5a52a344-c840-428b-89b5-b3c2e86fbc43 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS PRO WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash

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

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

[Bug 1879209] Re: Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson
** Description changed:

  I have two displays side-by-side: one that is 2560x1440 in landscape and
  a second that is 1280x1024 in portrait. In earlier versions of Ubuntu
- (definitely in 19.04 and 19.10) I was able to configure this using
+ (definitely in 18.04 and 19.10) I was able to configure this using
  Display Settings in the default windowing environment.
  
  After upgrading to Ubuntu 20.04 it seems Display Settings is computing
  an incorrect horizontal resolution for the combined display. This
  results in a display that is too wide for the monitors that pans when I
  mouse toward the edges.
  
  xrandr is reporting that it's trying to make a display that is 3840x1440
  (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is
  doing the math before considering the smaller display is in portrait
  instead of landscape.
  
  here is the output from xrandr:
  
  $ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
-1280x1024 60.02*+  75.02  
-1280x960  60.00  
-1152x864  75.00  
-1024x768  75.0370.0760.00  
-800x600   75.0072.1960.3256.25  
-640x480   75.0072.8159.94  
+    1280x1024 60.02*+  75.02
+    1280x960  60.00
+    1152x864  75.00
+    1024x768  75.0370.0760.00
+    800x600   75.0072.1960.3256.25
+    640x480   75.0072.8159.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
-2560x1440 59.95*+
-2048x1152 60.00  
-1920x1200 59.88  
-1920x1080 60.0059.9450.0029.9725.0023.98  
-1680x1050 59.95  
-1600x1200 60.00  
-1280x1024 75.0260.02  
-1280x720  60.0059.9450.00  
-1200x960  59.90  
-1152x864  75.00  
-1024x768  75.0360.00  
-800x600   75.0060.32  
-720x576   50.00  
-720x480   59.94  
-640x480   75.0059.9459.93  
+    2560x1440 59.95*+
+    2048x1152 60.00
+    1920x1200 59.88
+    1920x1080 60.0059.9450.0029.9725.0023.98
+    1680x1050 59.95
+    1600x1200 60.00
+    1280x1024 75.0260.02
+    1280x720  60.0059.9450.00
+    1200x960  59.90
+    1152x864  75.00
+    1024x768  75.0360.00
+    800x600   75.0060.32
+    720x576   50.00
+    720x480   59.94
+    640x480   75.0059.9459.93
  DP-5 disconnected (normal left inverted right x axis y axis)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
-  GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
+  GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 20:35:03 2020
  DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
+  NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
  InstallationDate: Installed on 2018-09-17 (608 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUS All Series
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  

[Bug 1879209] Re: Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson
** Attachment added: "Display Settings 2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879209/+attachment/5373107/+files/Screenshot%20from%202020-05-17%2020-44-29.png

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

Title:
  Display settings configures dual display resolution incorrectly

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

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

[Bug 1879209] [NEW] Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson
Public bug reported:

I have two displays side-by-side: one that is 2560x1440 in landscape and
a second that is 1280x1024 in portrait. In earlier versions of Ubuntu
(definitely in 19.04 and 19.10) I was able to configure this using
Display Settings in the default windowing environment.

After upgrading to Ubuntu 20.04 it seems Display Settings is computing
an incorrect horizontal resolution for the combined display. This
results in a display that is too wide for the monitors that pans when I
mouse toward the edges.

xrandr is reporting that it's trying to make a display that is 3840x1440
(2560+1280) instead of 3584x1440 (2560+1024), so I assume something is
doing the math before considering the smaller display is in portrait
instead of landscape.

here is the output from xrandr:

$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
   1280x1024 60.02*+  75.02  
   1280x960  60.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.3256.25  
   640x480   75.0072.8159.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
   2560x1440 59.95*+
   2048x1152 60.00  
   1920x1200 59.88  
   1920x1080 60.0059.9450.0029.9725.0023.98  
   1680x1050 59.95  
   1600x1200 60.00  
   1280x1024 75.0260.02  
   1280x720  60.0059.9450.00  
   1200x960  59.90  
   1152x864  75.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0059.9459.93  
DP-5 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 20:35:03 2020
DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
InstallationDate: Installed on 2018-09-17 (608 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago)
dmi.bios.date: 04/18/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO(Wi-Fi ac)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

2020-05-03 Thread Blake Anderson
Confirmed, I get the message in #1 every boot. 20.04

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

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

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

[Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

2020-04-24 Thread Richard Anderson
* It is also there is a setting here that I overlooked.

should have been:

It is possible also there is a setting here that I overlooked.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions

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

[Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

2020-04-24 Thread Richard Anderson
This may or may not be an issue, but here are my observations. The order
of operations seems to be the cause of my issue with the additional
factor that the /boot partition size is unusually small compared to
recent Ubuntu installations.

Order of operations as follows:

1. unattended-install script is run
2. removes packages found in /etc/kernel/postinst.d/apt-auto-removal
3. Installs new kernel
4. creates new /etc/kernel/postinst.d/apt-auto-removal

At this point it does not remove any old packages after the new kernel
is installed. However, when unattended-install is run a second time it
will remove those packages. This seems like an awkward approach.
Ideally, the old kernel packages would get removed the first run of
unattended-install. I considered safety concerns in removing older
kernels after an update but then it still gets removed on a second run.
It is also there is a setting here that I overlooked.

I applied a work around in kernel/postinst.d/zzz_autoremove to simply
run apt-get autoremove -y a few seconds after unattended-install is
completed. This approach is not ideal but functional for this
potentially unique issue.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions

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

[Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

2020-04-21 Thread Richard Anderson
Is this still an issue?

I have Xenial installs where this occurs occasionally. I don't have much
information other than /boot partition fills where we will get alerts.
After logging in and running apt-get autoremove the space is cleared.

apt-mark showauto 'linux-image-.*'
Show 3 kernels, which I believe is normal. (currently 
linux-image-4.4.0-176-generic,linux-image-4.4.0-177-generic, 
linux-image-generic)

apt-mark showmanual 'linux-image-.*'
Does not show any results.

/etc/apt/apt.conf.d/50unattended-upgrades has the following uncommented:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}ESM:${distro_codename}";
};
Unattended-Upgrade::Remove-Unused-Dependencies "true";

unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions

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

[Bug 1863810] Re: Focal Fossa (20.04) feature request - Enable CONFIG_X86_UV

2020-03-13 Thread Russ Anderson
This looks good.  The UV message show up as expected.

Attached is boot output.

** Attachment added: "ubuntu-5.4.0-15.UV.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863810/+attachment/5336628/+files/ubuntu-5.4.0-15.UV.txt

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

Title:
  Focal Fossa (20.04) feature request - Enable CONFIG_X86_UV

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

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

[Bug 1864153] Re: tracker-extract crashed with signal 5 in start_thread()

2020-02-25 Thread derrill wayne anderson
crashed on boot

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

Title:
  tracker-extract crashed with signal 5 in start_thread()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1864153/+subscriptions

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

[Bug 1859031] [NEW] Cursor freezes with synergy software kvm

2020-01-09 Thread Dean Anderson
Public bug reported:

I'm using the synergy software KVM to share a mouse and keyboard between
two machines, with my Ubuntu workstation as the client.  When attempting
to drag-and-drop within Qt apps, the mouse cursor will freeze for
several seconds.  Cursor freezes also occur intermittently as well.  I
have an issue report for synergy as well: https://github.com/symless
/synergy-core/issues/6487

This issue seems to be a regression related to update 1.6.4-3ubuntu0.2.
The current workaround is to pin all libx11 packages to the previous
(0.1) versions.

Release Version: Ubuntu 18.04.3 LTS
Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libx11-6 2:1.6.4-3ubuntu0.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.33.01  Wed Nov 13 00:00:22 
UTC 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jan  9 09:13:29 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP104GLM [Quadro P5200 Mobile] [1028:1832]
InstallationDate: Installed on 2018-07-30 (527 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Precision 7730
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=6599bc95-d2cf-4bb0-b32d-653b78ae0fe9 ro quiet splash acpi=force 
vt.handoff=1
SourcePackage: libx11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0MG0JR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7730:pvr:rvnDellInc.:rn0MG0JR:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7730
dmi.product.sku: 0832
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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: libx11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  Cursor freezes with synergy software kvm

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

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

[Bug 1413665] Re: Bad Request - Bad bot, go away! Request aborted.

2019-11-07 Thread Dale C. Anderson
It seems any password auto filler gets fooled by the honeypot on the
page and results in the error.

The irony is that in order to comment or mark "it affects me", you have
to get past the very form that's causing the problem. I suspect this
affects a lot more people than is indicated.

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

Title:
  Bad Request - Bad bot, go away!  Request aborted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1413665/+subscriptions

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

[Bug 1841364] Re: AppArmor breaks the default Unbound installation in a live session

2019-08-30 Thread Tore Anderson
I can confirm that the following commands fixes the problem so Ubound
can start again:

 echo 'alias / -> /upper/,' >> /etc/apparmor.d/tunables/alias
 apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.unbound

I noticed that when it starts, another AppArmor-related error message is
logged:

[  257.707923] audit: type=1107 audit(1567174888.349:247): pid=976 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=6735 label="/usr/sbin/unbound" 
peer_pid=1 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'

However, it does not appear to cause any problems as far as I could
tell.

Tore

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

Title:
  AppArmor breaks the default Unbound installation in a live session

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

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

[Bug 1841364] Re: AppArmor breaks the default Unbound installation in a live session

2019-08-28 Thread Tore Anderson
That does not work, same error message when attempting to restart
unbound.

The apparmor_parser command results in the following being logged to the
system journal:

aug. 28 16:08:02 ubuntu audit[6536]: AVC apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/usr/sbin/unbound" pid=6536 comm="apparmor_parser"
aug. 28 16:08:02 ubuntu kernel: audit: type=1400 audit(1567008482.755:240): 
apparmor="STATUS" operation="profile_replace" info="same as current profile, 
skipping" profile="unconfined" name="/usr/sbin/unbound" pid=6536 
comm="apparmor_parser"

Also, the /etc/apparmor.d/force-complain/usr.sbin.unbound does not
exist, so the rm -f command is a no-op.

Tore

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

Title:
  AppArmor breaks the default Unbound installation in a live session

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

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

[Bug 1841364] Re: AppArmor breaks the default Unbound installation in a live session

2019-08-27 Thread Tore Anderson
Sure, I can test if you tell me how, ideally spoon-fed. Like I said, I
have no experience with AppArmor so I don't know how to install alias
rules.

By the way, I finished the my blog post, of the six DNSSEC validators I
tested it was only Unbound that didn't work in the live environment (but
of course it might be that none of the others are using AppArmor):
https://www.redpill-linpro.com/techblog/2019/08/27/evaluating-local-
dnssec-validators.html

Tore

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

Title:
  AppArmor breaks the default Unbound installation in a live session

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

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

[Bug 1841364] Re: AppArmor breaks the default Unbound installation

2019-08-25 Thread Tore Anderson
I don't know anything about AppArmor, so I am afraid I can't help you
with that.

I was just researching DNSSEC validators for a blog post I'm working on,
testing them on both Fedora and Ubuntu (using a live VM). Since Unbound
didn't seem to work (unless I did 'aa-complain /usr/sbin/unbound') I
thought I'd submit a bug. I didn't realise the problem was caused by my
use of the live media, as I was under the impression that the live media
was expected to work the same as a regular installation.

In any case, I'll be able to finish my blog post so it's not important
for me that this issue is fixed.

Tore

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

Title:
  AppArmor breaks the default Unbound installation

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

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

[Bug 1841364] Re: AppArmor breaks the default Unbound installation

2019-08-25 Thread Tore Anderson
Correct, as mentioned under «Steps to reproduce» I did my testing using
live media in a virtual machine.

Tore

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

Title:
  AppArmor breaks the default Unbound installation

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

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

[Bug 1841364] [NEW] AppArmor breaks the default Unbound installation

2019-08-25 Thread Tore Anderson
Public bug reported:

Immediately after installing Unbound, it starts up normally. However, if
you try to restart it afterwards (without changing anything), it fails
with the following error message:

Aug 25 10:41:26 ubuntu unbound[6650]: /etc/unbound/unbound.conf:10: error: 
cannot open include file '/etc/unbound/unbound.conf.d/*.conf': No such file or 
directory
Aug 25 10:41:26 ubuntu unbound[6650]: read /etc/unbound/unbound.conf failed: 1 
errors in configuration file
Aug 25 10:41:26 ubuntu unbound[6650]: [1566729686] unbound[6650:0] fatal error: 
Could not read config file: /etc/unbound/unbound.conf. Maybe try unbound -dd, 
it stays on the commandline to see more errors, or unbound-checkconf

There *are* files matching the above glob pattern, however:

root@ubuntu:~# echo /etc/unbound/unbound.conf.d/*.conf
/etc/unbound/unbound.conf.d/qname-minimisation.conf 
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf

unbound-checkconf, on the other hand, determines the configuration to be
fine:

root@ubuntu:~# unbound-checkconf 
unbound-checkconf: no errors in /etc/unbound/unbound.conf

In the kernel log I can see that AppArmor is the probable culprit:

Aug 25 10:41:26 ubuntu kernel: audit: type=1400
audit(1566729686.377:239): apparmor="DENIED" operation="open"
profile="/usr/sbin/unbound" name="/upper/etc/unbound/unbound.conf.d/"
pid=6650 comm="unbound" requested_mask="r" denied_mask="r" fsuid=0
ouid=0

Steps to reproduce:

1. Download ubuntu-19.04-desktop-amd64.iso from 
https://ubuntu.com/download/desktop
2. Boot the downloaded ISO file in a virtual machine
3. Start gnome-terminal
4. sudo -i
5. apt-add-repository universe
6. apt -y install unbound
7. systemctl status unbound # verify that it is runnning
8. systemctl restart unbound
9. systemctl status unbound # verify that it failed to start
10. journalctl -kn1 # display AppArmor error message

** Affects: unbound (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/1841364

Title:
  AppArmor breaks the default Unbound installation

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

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

[Bug 1828345] Re: [4.4.0-144 regression] kernel BUG at [...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

2019-06-11 Thread Tore Anderson
We had another server running 4.4.0-148-generic crash just now. It has a
different role then the firewalls that we originally saw the crash with.
After an automatic reboot, it got back up with 4.4.0-150-generic (which
had been installed at an earlier stage but not rebooted into), and
crashed twice in rapid succession. I'm including the traces printed to
the serial console below:

Crash #1:

[760425.631142] [ cut here ]
[760425.68] kernel BUG at 
/build/linux-JhELCR/linux-4.4.0/net/core/skbuff.c:1207!
[760425.698342] invalid opcode:  [#1] SMP 
[760425.722139] Modules linked in: cpuid xt_CHECKSUM iptable_mangle ipt_REJECT 
nf_reject_ipv4 bridge stp llc ebtable_filter ebtables hpwdt nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp xt_multiport xt_conntrack 
iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 ip_tables x_tables bonding 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
gpio_ich ghash_clmulni_intel aesni_intel ftdi_sio aes_x86_64 lrw cdc_ether 
gf128mul usbserial usbnet mii glue_helper input_leds hpilo joydev ablk_helper 
i7core_edac cryptd edac_core shpchp serio_raw 8250_fintek acpi_power_meter 
lpc_ich ipmi_ssif mac_hid ipmi_devintf ipmi_si ipmi_msghandler nf_nat_h323 
nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_nat nf_conntrack lp parport 
autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ixgbe dca amdkfd 
amd_iommu_v2 radeon i2c_algo_bit hid_generic ttm drm_kms_helper syscopyarea 
sysfillrect vxlan ip6_udp_tunnel sysimgblt fb_sys_fops udp_tunnel usbhid uas 
ptp hpsa pps_core psmouse drm usb_storage hid bnx2 mdio scsi_transport_sas fjes
[760426.325859] CPU: 9 PID: 0 Comm: swapper/9 Tainted: G  I 
4.4.0-148-generic #174-Ubuntu
[760426.377154] Hardware name: HP ProLiant DL360 G7, BIOS P68 05/21/2018
[760426.413661] task: 880c0461d940 ti: 880c04634000 task.ti: 
880c04634000
[760426.456870] RIP: 0010:[]  [] 
pskb_expand_head+0x243/0x250
[760426.504553] RSP: 0018:880c1f903b80  EFLAGS: 00010202
[760426.535588] RAX: 0002 RBX: 880c0007ed00 RCX: 
02080020
[760426.577271] RDX: 0140 RSI:  RDI: 
880c0007ed00
[760426.618845] RBP: 880c1f903bb8 R08: 0001 R09: 
000a
[760426.660361] R10: 880bffcf6a00 R11:  R12: 
880c0007ed00
[760426.702862] R13: 0001 R14: 0011 R15: 
880c0007ed00
[760426.743881] FS:  () GS:880c1f90() 
knlGS:
[760426.789899] CS:  0010 DS:  ES:  CR0: 80050033
[760426.822597] CR2: 7ffccac51ff8 CR3: 01e0a000 CR4: 
00020670
[760426.863053] Stack:
[760426.874826]  81efb140 880c1f903db0 880c0007ed00 
880c0007ed00
[760426.917091]  0001 0011 0001 
880c1f903c00
[760426.960119]  81740e10 880c002d29c0 00010001 
880c0007ed00
[760427.003239] Call Trace:
[760427.017831]   
[760427.029143]  [] __pskb_pull_tail+0x50/0x350
[760427.064432]  [] _decode_session6+0x26a/0x400
[760427.097198]  [] __xfrm_decode_session+0x39/0x50
[760427.132864]  [] icmpv6_route_lookup+0xf0/0x1c0
[760427.168344]  [] icmp6_send+0x5e1/0x940
[760427.198021]  [] ? check_preempt_curr+0x54/0x90
[760427.232489]  [] ? ttwu_do_activate.constprop.87+0x5d/0x70
[760427.272075]  [] ? try_to_wake_up+0x49/0x400
[760427.304593]  [] ? nf_ct_net_exit+0x50/0x50 
[nf_defrag_ipv6]
[760427.345205]  [] icmpv6_send+0x21/0x30
[760427.375673]  [] ip6_expire_frag_queue+0xe0/0x120
[760427.411187]  [] nf_ct_frag6_expire+0x1f/0x30 
[nf_defrag_ipv6]
[760427.452645]  [] call_timer_fn+0x37/0x140
[760427.48]  [] ? nf_ct_net_exit+0x50/0x50 
[nf_defrag_ipv6]
[760427.532271]  [] run_timer_softirq+0x234/0x330
[760427.570814]  [] __do_softirq+0x109/0x2b0
[760427.608307]  [] irq_exit+0xa5/0xb0
[760427.641799]  [] smp_apic_timer_interrupt+0x50/0x70
[760427.682907]  [] apic_timer_interrupt+0xcc/0xe0
[760427.721035]   
[760427.732319]  [] ? cpuidle_enter_state+0x11b/0x2d0
[760427.777027]  [] cpuidle_enter+0x17/0x20
[760427.812803]  [] call_cpuidle+0x32/0x60
[760427.847096]  [] ? cpuidle_select+0x19/0x20
[760427.883583]  [] cpu_startup_entry+0x296/0x360
[760427.921417]  [] start_secondary+0x177/0x1b0
[760427.958469] Code: 75 1a 41 8b 87 cc 00 00 00 49 03 87 d0 00 00 00 e9 e2 fe 
ff ff b8 f4 ff ff ff eb bc 4c 89 ef e8 84 9c ab ff b8 f4 ff ff ff eb ad <0f> 0b 
90 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 
[760428.073481] RIP  [] pskb_expand_head+0x243/0x250
[760428.112534]  RSP 
[760428.151392] ---[ end trace ae05fc32238b1676 ]---
[760428.182175] Kernel panic - not syncing: Fatal exception in interrupt
[760428.224421] Kernel Offset: disabled
[760428.248096] Rebooting in 120 seconds..

Crash #2:


[Bug 1828345] Re: [4.4.0-144 regression] kernel BUG at [...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

2019-05-13 Thread Tore Anderson
** Summary changed:

- [possible regression] kernel BUG at 
[...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207
+ [4.4.0-144 regression] kernel BUG at 
[...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

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

Title:
  [4.4.0-144 regression] kernel BUG at [...]/linux-lts-
  xenial-4.4.0/net/core/skbuff.c:1207

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1828345/+subscriptions

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

[Bug 1828345] Re: [possible regression] kernel BUG at [...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

2019-05-10 Thread Tore Anderson
Hi Peter, and thanks for confirming the bug.

We first experienced this issue in 4.4.0-144 so if you're saying
4.4.0-143 is stable that would mean the bug was introduced in 4.4.0-144.

Tore

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

Title:
  [possible regression] kernel BUG at [...]/linux-lts-
  xenial-4.4.0/net/core/skbuff.c:1207

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1828345/+subscriptions

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

[Bug 1828345] Re: [possible regression] kernel BUG at [...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

2019-05-10 Thread Tore Anderson
And a third crash, this time after upgrading to 4.4.0-146-generic.
Uptime just 21h41m. Backtrace looks the same.

I've now reverted back to 4.4.0-116-generic. I'll let you know if we
experience similar crashes with this version.

[78056.952451] [ cut here ]
[78056.975336] kernel BUG at 
/build/linux-lts-xenial-Y8MnSS/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207!
[78057.024383] invalid opcode:  [#1] SMP 
[78057.046515] Modules linked in: ip6table_raw ip6table_mangle ip6t_REJECT 
nf_reject_ipv6 iptable_raw xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_mark 
iptable_mangle xt_comment ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_limit xt_tcpudp 
xt_iprange ip_set_hash_net hpwdt nfnetlink_log ip6table_filter ip6_tables 
xt_set ip_set nfnetlink xt_multiport xt_conntrack iptable_filter ip_tables 
x_tables dm_crypt nf_conntrack_irc nf_conntrack_tftp nf_conntrack_ftp 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
intel_powerclamp nf_conntrack coretemp kvm_intel kvm ipmi_ssif ipmi_devintf 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 hpilo lrw gpio_ich gf128mul ipip glue_helper shpchp tunnel4 ipmi_si 
ip_tunnel ablk_helper serio_raw ipmi_msghandler cryptd i7core_edac 8250_fintek 
edac_core 8021q lpc_ich acpi_power_meter garp mrp stp llc mac_hid bonding 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear amdkfd amd_iommu_v2 radeon 
i2c_algo_bit ttm drm_kms_helper ixgbe syscopyarea dca sysfillrect sysimgblt 
vxlan fb_sys_fops ip6_udp_tunnel udp_tunnel ptp hpsa drm pps_core psmouse bnx2 
mdio scsi_transport_sas fjes
[78057.630237] CPU: 14 PID: 0 Comm: swapper/14 Not tainted 4.4.0-146-generic 
#172~14.04.1-Ubuntu
[78057.676457] Hardware name: HP ProLiant DL360 G7, BIOS P68 07/02/2013
[78057.710242] task: 88011a90cc80 ti: 88011a928000 task.ti: 
88011a928000
[78057.751071] RIP: 0010:[]  [] 
pskb_expand_head+0x227/0x260
[78057.797573] RSP: 0018:88011bbc3b90  EFLAGS: 00010202
[78057.825843] RAX: 0002 RBX: 8800b8641000 RCX: 02080020
[78057.864650] RDX: 0140 RSI:  RDI: 8800b8641000
[78057.902584] RBP: 88011bbc3bc8 R08: 0001 R09: 88011a5f6e80
[78057.940809] R10:  R11: 0040 R12: 
[78057.979197] R13: 8800b8641000 R14: 0001 R15: 8800b2f5c6ce
[78058.018261] FS:  () GS:88011bbc() 
knlGS:
[78058.061413] CS:  0010 DS:  ES:  CR0: 80050033
[78058.090850] CR2: 7f6086a9afb8 CR3: 01e0c000 CR4: 00020670
[78058.128810] Stack:
[78058.140078]  88011bbc3de0 88011bbc3de0 8800b8641000 
88011bbc3ca0
[78058.179734]  0001 0001 8800b2f5c6ce 
88011bbc3c10
[78058.219346]  81713a70 880218455f28 00010005 
8800b8641000
[78058.258709] Call Trace:
[78058.272106]   
[78058.282744]  [] __pskb_pull_tail+0x50/0x350
[78058.314577]  [] _decode_session6+0x2e6/0x490
[78058.346575]  [] __xfrm_decode_session+0x33/0x50
[78058.378788]  [] icmpv6_route_lookup+0xf4/0x1d0
[78058.411200]  [] icmp6_send+0x5f1/0x920
[78058.440073]  [] ? kmem_cache_free+0x1dd/0x200
[78058.471604]  [] ? destroy_conntrack+0xb0/0x100 
[nf_conntrack]
[78058.512149]  [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6]
[78058.550814]  [] icmpv6_send+0x21/0x30
[78058.578855]  [] ip6_expire_frag_queue+0xe0/0x120
[78058.612372]  [] nf_ct_frag6_expire+0x1f/0x30 
[nf_defrag_ipv6]
[78058.651923]  [] call_timer_fn+0x37/0x140
[78058.681306]  [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6]
[78058.724450]  [] run_timer_softirq+0x213/0x320
[78058.761756]  [] __do_softirq+0xe5/0x2b0
[78058.795657]  [] irq_exit+0x96/0xa0
[78058.828108]  [] smp_apic_timer_interrupt+0x50/0x70
[78058.867152]  [] apic_timer_interrupt+0xcc/0xe0
[78058.903881]   
[78058.914272]  [] ? poll_idle+0x40/0x80
[78058.952138]  [] cpuidle_enter_state+0x9f/0x280
[78058.987977]  [] cpuidle_enter+0x17/0x20
[78059.021555]  [] call_cpuidle+0x32/0x60
[78059.056082]  [] ? cpuidle_select+0x19/0x20
[78059.091593]  [] cpu_startup_entry+0x290/0x350
[78059.128795]  [] start_secondary+0x16c/0x190
[78059.164726] Code: ff ff ff 90 e9 54 ff ff ff 48 89 d7 48 89 55 c8 e8 bf b2 
a8 ff 84 c0 48 8b 55 c8 75 97 eb 91 41 81 cf 00 20 00 00 e9 2a fe ff ff <0f> 0b 
0f 0b 44 89 fe 4c 89 ef e8 7a ec ff ff 85 c0 74 12 48 89 
[78059.277870] RIP  [] pskb_expand_head+0x227/0x260
[78059.314117]  RSP 
[78059.353516] ---[ end trace e2f55d38532b6f9c ]---
[78059.381878] Kernel panic - not syncing: Fatal exception in interrupt
[78059.420570] Kernel Offset: disabled
[78059.442784] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
[78059.483700] [ cut here ]
[78059.512129] WARNING: CPU: 14 PID: 0 at 
/build/linux-lts-xenial-Y8MnSS/linux-lts-xenial-4.4.0/arch/x86/kernel/smp.c:125 

[Bug 1828345] [NEW] [possible regression] kernel BUG at [...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207

2019-05-09 Thread Tore Anderson
Public bug reported:

Following a kernel upgrade from linux-image-4.4.0-116-generic to linux-
image-4.4.0-144-generic, our IPTables-based firewall have become
unstable and have crashed twice with identical-looking backtraces after
a short uptime.

When running linux-image-4.4.0-116-generic the firewall had been up and
running stable with an uptime of well over a year. Therefore, I highly
suspect that this is a bug that has been introduced between the two
versions mentioned.

These are the backtraces printed to the serial console when it crashed.

Crash #1 (after approx. 3 days of uptime):

[258363.286572] [ cut here ]
[258363.311248] kernel BUG at 
/build/linux-lts-xenial-YWfqtJ/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207!
[258363.362309] invalid opcode:  [#1] SMP 
[258363.385411] Modules linked in: ip6table_raw ip6table_mangle ip6t_REJECT 
nf_reject_ipv6 iptable_raw xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_mark 
iptable_mangle xt_comment ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_limit xt_tcpudp 
xt_iprange ip_set_hash_net hpwdt nfnetlink_log ip6table_filter ip6_tables 
xt_set ip_set nfnetlink xt_multiport xt_conntrack iptable_filter ip_tables 
x_tables dm_crypt intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul nf_conntrack_irc nf_conntrack_tftp nf_conntrack_ftp 
crc32_pclmul ghash_clmulni_intel hpilo aesni_intel aes_x86_64 nf_conntrack_ipv6 
acpi_power_meter mac_hid lrw 8250_fintek nf_defrag_ipv6 shpchp gpio_ich 
gf128mul serio_raw nf_conntrack_ipv4 i7core_edac glue_helper nf_defrag_ipv4 
edac_core nf_conntrack ablk_helper cryptd lpc_ich ipmi_ssif ipmi_devintf 
ipmi_si ipmi_msghandler ipip tunnel4 ip_tunnel 8021q garp mrp stp llc bonding 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear amdkfd amd_iommu_v2 radeon 
ixgbe i2c_algo_bit ttm dca drm_kms_helper vxlan syscopyarea ip6_udp_tunnel 
sysfillrect udp_tunnel sysimgblt ptp fb_sys_fops hpsa pps_core psmouse drm mdio 
bnx2 scsi_transport_sas fjes
[258363.967279] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-144-generic 
#170~14.04.1-Ubuntu
[258364.011349] Hardware name: HP ProLiant DL360 G7, BIOS P68 07/02/2013
[258364.045068] task: 81e15500 ti: 81e0 task.ti: 
81e0
[258364.085793] RIP: 0010:[]  [] 
pskb_expand_head+0x227/0x260
[258364.132139] RSP: 0018:88011ba03b90  EFLAGS: 00010202
[258364.162253] RAX: 0002 RBX: 8800bff20e00 RCX: 
02080020
[258364.201311] RDX: 0140 RSI:  RDI: 
8800bff20e00
[258364.240352] RBP: 88011ba03bc8 R08: 0001 R09: 
8800d872
[258364.279499] R10:  R11: 0040 R12: 

[258364.319220] R13: 8800bff20e00 R14: 0001 R15: 
8800d327fdce
[258364.358038] FS:  () GS:88011ba0() 
knlGS:
[258364.401198] CS:  0010 DS:  ES:  CR0: 80050033
[258364.432486] CR2: 7fcdc0672543 CR3: 01e0c000 CR4: 
00020670
[258364.470918] Stack:
[258364.481920]  88011ba03de0 88011ba03de0 8800bff20e00 
88011ba03ca0
[258364.521426]  0001 0001 8800d327fdce 
88011ba03c10
[258364.561323]  81713aa0 8802195c3b28 00010005 
8800bff20e00
[258364.601724] Call Trace:
[258364.615234]   
[258364.626239]  [] __pskb_pull_tail+0x50/0x350
[258364.658220]  [] _decode_session6+0x2e6/0x490
[258364.690802]  [] __xfrm_decode_session+0x33/0x50
[258364.724086]  [] icmpv6_route_lookup+0xf4/0x1d0
[258364.756501]  [] icmp6_send+0x5f1/0x920
[258364.786304]  [] ? handle_edge_irq+0xba/0x180
[258364.818506]  [] ? nf_ct_net_exit+0x50/0x50 
[nf_defrag_ipv6]
[258364.856875]  [] icmpv6_send+0x21/0x30
[258364.884947]  [] ip6_expire_frag_queue+0xe0/0x120
[258364.918555]  [] nf_ct_frag6_expire+0x1f/0x30 
[nf_defrag_ipv6]
[258364.957884]  [] call_timer_fn+0x37/0x140
[258364.988097]  [] ? nf_ct_net_exit+0x50/0x50 
[nf_defrag_ipv6]
[258365.027226]  [] run_timer_softirq+0x213/0x320
[258365.065587]  [] __do_softirq+0xe5/0x2b0
[258365.100276]  [] irq_exit+0x96/0xa0
[258365.132826]  [] smp_apic_timer_interrupt+0x50/0x70
[258365.172450]  [] apic_timer_interrupt+0xcc/0xe0
[258365.210589]   
[258365.221544]  [] ? cpuidle_enter_state+0xc9/0x280
[258365.266485]  [] ? cpuidle_enter_state+0xbb/0x280
[258365.305657]  [] cpuidle_enter+0x17/0x20
[258365.339899]  [] call_cpuidle+0x32/0x60
[258365.372832]  [] ? cpuidle_select+0x19/0x20
[258365.407697]  [] cpu_startup_entry+0x290/0x350
[258365.443997]  [] rest_init+0x7c/0x80
[258365.476503]  [] start_kernel+0x4a7/0x4b4
[258365.511376]  [] ? set_init_arg+0x55/0x55
[258365.546509]  [] ? early_idt_handler_array+0x120/0x120
[258365.585481]  [] x86_64_start_reservations+0x2a/0x2c
[258365.623803]  [] x86_64_start_kernel+0x12d/0x13a
[258365.660778] Code: ff ff ff 90 e9 54 ff ff ff 48 89 d7 48 89 55 c8 e8 0f b1 
a8 ff 84 c0 48 8b 55 c8 

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-05-02 Thread Anderson Luiz Alves
unattended-upgrades=1.5ubuntu3.18.10.4 works on cosmic

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic

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

Title:
  NoAllowedOrigin cause package removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+subscriptions

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

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-05-02 Thread Anderson Luiz Alves
unattended-upgrades=1.1ubuntu1.18.04.7~16.04.3 works on xenial

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  NoAllowedOrigin cause package removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+subscriptions

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

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-05-02 Thread Anderson Luiz Alves
unattended-upgrades=1.1ubuntu1.18.04.11 works on bionic.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  NoAllowedOrigin cause package removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+subscriptions

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

[Bug 1826624] [NEW] package apt-utils 1.2.31 failed to install/upgrade: package apt-utils is already installed and configured

2019-04-26 Thread Tommy Anderson
Public bug reported:

Just installed Ubuntu 16 on an old Dell previously running Windows XP
Home Edition.  Deleted Windows and proceeded to become your newest Linux
user.  Runs okay except after shut down.  Tried using Ubuntu Software
for updates and had to end up using terminal to update.  Had system
error codes evey since.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt-utils 1.2.31
ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: i386
Date: Fri Apr 26 19:36:41 2019
DuplicateSignature:
 package:apt-utils:1.2.31
 Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
 dpkg: error processing package udev (--configure):
  package udev is already installed and configured
ErrorMessage: package apt-utils is already installed and configured
InstallationDate: Installed on 2019-04-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: dpkg
Title: package apt-utils 1.2.31 failed to install/upgrade: package apt-utils 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 xenial

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

Title:
  package apt-utils 1.2.31 failed to install/upgrade: package apt-utils
  is already installed and configured

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

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

[Bug 1803993] Re: Password appears on the VT1 screen

2019-04-16 Thread Robert Anderson
I'm pretty sure I just encountered this bug, although all I did was
issue a shutdown, and very briefly I was able to see several plaintext
passwords that had been used to log in across several user accounts.  I
am on Ubuntu 18.04.2 LTS.

This was a shock for reasons which should be obvious.

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

Title:
  Password appears on the VT1 screen

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

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

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-04-16 Thread Anderson Luiz Alves
The package unattended-upgrades=1.10ubuntu5 fixes the problem on Ubuntu
18.04 LTS bionic.

** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco

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

Title:
  NoAllowedOrigin cause package removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+subscriptions

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

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-04-11 Thread Anderson Luiz Alves
full log that removed packages that shouldn't

** Description changed:

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.
  
  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS
  
  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.
  
- Log of dry-run with the problem:
- $ sudo unattended-upgrade -d --dry-run
+ Log that happens package removal:
+ $ sudo unattended-upgrade -d
  [...]
- Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
- self.allowed_origins)
-   File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
- raise NoAllowedOriginError()
+   File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
+ self.allowed_origins)
+   File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
+ raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
- Exception:
+ Exception: 
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
+ marking cliente-ldap for removal
+ (Reading database ... 213413 files and directories currently installed.)
+ Removing cliente-ldap (1:2.17.15) ...
+ marking libcephfs2 for removal
+ (Reading database ... 213392 files and directories currently installed.)
+ Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ marking ldap-auth-config for removal
+ (Reading database ... 213386 files and directories currently installed.)
+ Removing libpam-ldap:amd64 (186-4ubuntu1) ...
+ Removing ldap-auth-config (0.5.3) ...
+ Removing ldap-auth-client (0.5.3) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking python-samba for removal
+ (Reading database ... 213332 files and directories currently installed.)
+ Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
+ Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
+ Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking nss-updatedb for removal
+ (Reading database ... 212865 files and directories currently installed.)
+ Removing nss-updatedb (10-3build1) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking samba-vfs-modules for removal
+ (Reading database ... 212859 files and directories currently installed.)
+ Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking librados2 for removal
+ (Reading database ... 212770 files and directories currently installed.)
+ Removing librados2 (12.2.11-0ubuntu0.18.04.1) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ marking libibverbs1 for removal
+ (Reading database ... 212761 files and directories currently installed.)
+ Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ...
+ Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ marking libpam-mount for removal
+ (Reading database ... 212731 files and directories currently installed.)
+ Removing libpam-mount (2.16-3ubuntu0.1) ...
+ Processing triggers for sgml-base (1.29) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking ibverbs-providers for removal
  marking tdb-tools for removal
- Keeping auto-removable tdb-tools package(s) because it would also remove the 
following packages which should be kept in this step: samba-common
- marking ibverbs-providers for removal
+ (Reading database ... 212691 files and directories currently installed.)
+ Removing tdb-tools (1.3.15-2) ...
+ Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ marking samba-dsdb-modules for removal
+ (Reading database ... 212680 files and directories currently installed.)
+ Removing samba-dsdb-modules 

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-04-11 Thread Anderson Luiz Alves
** Description changed:

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.
  
  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS
  
  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.
  
  Log of dry-run with the problem:
  $ sudo unattended-upgrade -d --dry-run
  [...]
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 259, in call_adjusted
- self.allowed_origins)
-   File "/usr/bin/unattended-upgrade", line 777, in ver_in_allowed_origin
- raise NoAllowedOriginError()
+   File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
+ self.allowed_origins)
+   File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
+ raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
- Exception: 
+ Exception:
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking tdb-tools for removal
  Keeping auto-removable tdb-tools package(s) because it would also remove the 
following packages which should be kept in this step: samba-common
  marking ibverbs-providers for removal
  marking python-dnspython for removal
  marking librados2 for removal
  marking ldap-auth-client for removal
  marking ldap-auth-config for removal
  marking python-tdb for removal
  marking libhx28 for removal
  marking libcephfs2 for removal
  marking nscd for removal
  marking smbclient for removal
  marking cliente-ldap for removal
  marking libnss-db for removal
  marking samba-vfs-modules for removal
  marking samba-dsdb-modules for removal
  marking libpam-mount for removal
  marking libpam-ldap for removal
  marking nss-updatedb for removal
  marking python-samba for removal
  marking auth-client-config for removal
  marking python-ldb for removal
  marking libnss-ldap for removal
  marking python-crypto for removal
  marking samba for removal
  marking libibverbs1 for removal
  marking attr for removal
  marking libpam-ccreds for removal
- Packages that were successfully auto-removed: 
+ Packages that were successfully auto-removed:
  Packages that are kept back: samba-common-bin tdb-tools
  InstCount=0 DelCount=0 BrokenCount=0
  
  Log of what should happen:
  $ sudo unattended-upgrade -d --dry-run
  [...]
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
- debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False
+ debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=False
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 259, in call_adjusted
+   File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
-   File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin
+   File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  debug: call_adjusted libsmbclient
  debug: marked_pkg: python-samba: install=False, upgrade=True, delete=False
  debug: marked_pkg: libwbclient0: install=False, upgrade=True, delete=False
  debug: marked_pkg: samba: install=False, upgrade=True, delete=False
  debug: marked_pkg: samba-dsdb-modules: install=False, upgrade=True, 
delete=False
  debug: marked_pkg: samba-libs: install=False, upgrade=True, delete=False
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
 

[Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-04-11 Thread Anderson Luiz Alves
The proposed fix is clear cache on NoAllowedOriginError exception.

** Patch added: "fix clear cache on exception"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+attachment/5254915/+files/uu_origin.patch

** Description changed:

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.
  
  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS
  
  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.
  
  Log of dry-run with the problem:
  $ sudo unattended-upgrade -d --dry-run
  [...]
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
- debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False
+ debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 259, in call_adjusted
  self.allowed_origins)
-   File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin
+   File "/usr/bin/unattended-upgrade", line 777, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception: 
+ marking samba-common-bin for removal
+ Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
+ marking tdb-tools for removal
+ Keeping auto-removable tdb-tools package(s) because it would also remove the 
following packages which should be kept in this step: samba-common
  marking ibverbs-providers for removal
- Keeping auto-removable ibverbs-providers package(s) because it would also 
remove the following packages which should be kept in this step: cliente-ldap 
samba-common
- marking samba-common-bin for removal
- Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: cliente-ldap 
samba-common
+ marking python-dnspython for removal
+ marking librados2 for removal
+ marking ldap-auth-client for removal
+ marking ldap-auth-config for removal
+ marking python-tdb for removal
+ marking libhx28 for removal
+ marking libcephfs2 for removal
+ marking nscd for removal
+ marking smbclient for removal
+ marking cliente-ldap for removal
+ marking libnss-db for removal
  marking samba-vfs-modules for removal
+ marking samba-dsdb-modules for removal
+ marking libpam-mount for removal
+ marking libpam-ldap for removal
+ marking nss-updatedb for removal
+ marking python-samba for removal
+ marking auth-client-config for removal
+ marking python-ldb for removal
+ marking libnss-ldap for removal
  marking python-crypto for removal
- Keeping auto-removable python-crypto package(s) because it would also remove 
the following packages which should be kept in this step: cliente-ldap
+ marking samba for removal
+ marking libibverbs1 for removal
  marking attr for removal
- marking smbclient for removal
- Keeping auto-removable smbclient package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
- marking python-ldb for removal
- Keeping auto-removable python-ldb package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
- marking python-tdb for removal
- Keeping auto-removable python-tdb package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
- marking samba-dsdb-modules for removal
- marking librados2 for removal
- marking libibverbs1 for removal
- marking samba for removal
- Keeping auto-removable samba package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
- marking python-samba for removal
- Keeping auto-removable python-samba package(s) because it would also remove 
the following packages which should be kept in this step: cliente-ldap
- marking libcephfs2 for removal
- marking tdb-tools for removal
- Keeping auto-removable tdb-tools package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap samba-common
- marking python-dnspython for removal
- Keeping auto-removable python-dnspython 

[Bug 1824341] [NEW] NoAllowedOrigin cause package removal

2019-04-11 Thread Anderson Luiz Alves
Public bug reported:

unattended-upgrades remove packages that shouldn't when there is a
NoAllowedOrigin exception.

Version:
unattended-upgrades=1.1ubuntu1.18.04.10
Ubuntu 18.04.2 LTS

Description of problem:
We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

Log of dry-run with the problem:
$ sudo unattended-upgrade -d --dry-run
[...]
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
debug: call_adjusted samba-common
debug: marked_pkg: samba: install=False, upgrade=False, delete=True
debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 259, in call_adjusted
self.allowed_origins)
  File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin
raise NoAllowedOriginError()
NoAllowedOriginError
debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
Exception: 
marking ibverbs-providers for removal
Keeping auto-removable ibverbs-providers package(s) because it would also 
remove the following packages which should be kept in this step: cliente-ldap 
samba-common
marking samba-common-bin for removal
Keeping auto-removable samba-common-bin package(s) because it would also remove 
the following packages which should be kept in this step: cliente-ldap 
samba-common
marking samba-vfs-modules for removal
marking python-crypto for removal
Keeping auto-removable python-crypto package(s) because it would also remove 
the following packages which should be kept in this step: cliente-ldap
marking attr for removal
marking smbclient for removal
Keeping auto-removable smbclient package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
marking python-ldb for removal
Keeping auto-removable python-ldb package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
marking python-tdb for removal
Keeping auto-removable python-tdb package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
marking samba-dsdb-modules for removal
marking librados2 for removal
marking libibverbs1 for removal
marking samba for removal
Keeping auto-removable samba package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
marking python-samba for removal
Keeping auto-removable python-samba package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap
marking libcephfs2 for removal
marking tdb-tools for removal
Keeping auto-removable tdb-tools package(s) because it would also remove the 
following packages which should be kept in this step: cliente-ldap samba-common
marking python-dnspython for removal
Keeping auto-removable python-dnspython package(s) because it would also remove 
the following packages which should be kept in this step: cliente-ldap
Packages that were successfully auto-removed: 
Packages that are kept back: ibverbs-providers python-crypto python-dnspython 
python-ldb python-samba python-tdb samba samba-common-bin smbclient tdb-tools
InstCount=0 DelCount=0 BrokenCount=0


Log of what should happen:
$ sudo unattended-upgrade -d --dry-run
[...]
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
debug: call_adjusted samba-common
debug: marked_pkg: samba: install=False, upgrade=False, delete=True
debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 259, in call_adjusted
self.allowed_origins)
  File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin
raise NoAllowedOriginError()
NoAllowedOriginError
debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
debug: call_adjusted libsmbclient
debug: marked_pkg: python-samba: install=False, upgrade=True, delete=False
debug: marked_pkg: libwbclient0: install=False, upgrade=True, delete=False
debug: marked_pkg: samba: 

[Bug 1791196] Re: [USB-Audio - US122 MKII, recording] Recording problem

2019-01-13 Thread Alfredo Anderson
Hi guys, I managed to have this working (on lubuntu) following
https://linuxmusicians.com/viewtopic.php?t=16711

In short, blacklist snd_usb_audio (and get the board listed as US-122L
instead of US-122mkII)

lfredo@alfredo-pc:~$ cat /proc/asound/cards 
 0 [NVidia ]: HDA-Intel - HDA NVidia
  HDA NVidia at 0xdbff8000 irq 23
 1 [US122L ]: USB US-122L - TASCAM US-122L
  TASCAM US-122L (644:8021 if 0 at 001/002)

Then create .asoundrc file.

And finally run jackd with the following presets

jackd -RP60 -dalsa -dusb_stream:1  -r48000 -p256 -n2

Hope someone find this useful.

Regards, Alfredo

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

Title:
  [USB-Audio - US122 MKII, recording] Recording problem

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

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

[Bug 1796779] Re: isync does not provide SNI when using SSL

2018-10-29 Thread Nick Anderson
As a workaround, I just grabbed and installed the 1.3.0-2 package from
sid https://packages.debian.org/sid/amd64/isync/download

and it works for me.

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

Title:
  isync does not provide SNI when using SSL

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

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

[Bug 1800505] Re: Settings in /etc/mediawiki/LocalSettings.php are ignored

2018-10-29 Thread Nathanael Anderson
why does the main page display: MediaWiki has been installed. instead of
please go to HOSTname/mediawiki to configure media wiki?

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

Title:
  Settings in /etc/mediawiki/LocalSettings.php are ignored

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

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

[Bug 1800505] [NEW] Settings in /etc/mediawiki/LocalSettings.php are ignored

2018-10-29 Thread Nathanael Anderson
Public bug reported:

Description:Ubuntu 18.04 LTS
Release:18.04

mediawiki:
  Installed: 1:1.27.4-3
  Candidate: 1:1.27.4-3
  Version table:
 *** 1:1.27.4-3 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/universe 
amd64 Packages
100 /var/lib/dpkg/status


Based on where the symlinks included in the package point, settings
placed in: /etc/mediawiki/LocalSettings.php should over ride default
settings.

So Creating /etc/mediawiki/LocalSettings.php with mode 640 that has only
this line in it: $wgLogo =
"https://cdn.dribbble.com/users/904380/screenshots/2233565/revised-
google-logo.gif"

and saving it. Should, after clearing the browser cache, show a new
image for the wiki, instead of the default.

This is not the current behaviour, hence the bug.

As a side note, after installing the package on ubuntu no documentation
is displayed to the user, based on my googling today, it looks like
LocalSettings.php used to have a generator, as part of the install
process, and that has gone away. The new install process with out that
feels like it isn't documented well, and this may just be a
documentation issue.

** Affects: mediawiki (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/1800505

Title:
  Settings in /etc/mediawiki/LocalSettings.php are ignored

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

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

[Bug 1796779] Re: isync does not provide SNI when using SSL

2018-10-25 Thread Nick Anderson
This looks to have been patched upstream:
https://sourceforge.net/p/isync/isync/merge-requests/2/

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

Title:
  isync does not provide SNI when using SSL

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

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

[Bug 1796770] [NEW] package grub-efi-amd64-signed 1.108+2.02+dfsg1-5ubuntu6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit s

2018-10-08 Thread Eric Anderson
Public bug reported:

system was executing a system update and failed to do so.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: grub-efi-amd64-signed 1.108+2.02+dfsg1-5ubuntu6
ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
Uname: Linux 4.18.0-9-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Mon Oct  8 16:27:21 2018
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.108+2.02+dfsg1-5ubuntu6 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic package-from-proposed

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

Title:
  package grub-efi-amd64-signed 1.108+2.02+dfsg1-5ubuntu6 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1796770/+subscriptions

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

[Bug 1786195] Re: broken audio/muffled, no system audio

2018-09-10 Thread Dominic Anderson
The bug was not gone when using kernel 4.4

there was also an additional kernel between 4.4 and 4.15 that was
available. I tried that as well. same result.no fix.

Since then I backed up my system and did a completely fresh install of
18.04LTS and the issue is still not fixed.

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1786195] Re: broken audio/muffled, no system audio

2018-09-10 Thread Dominic Anderson
The bug was not gone when using kernel 4.4

there was also an additional kernel between 4.4 and 4.15 that was
available. I tried that as well. same result.no fix.

Since then I backed up my system and did a completely fresh install of
18.04LTS and the issue is still not fixed.

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1791196] [NEW] [USB-Audio - US122 MKII, recording] Recording problem

2018-09-06 Thread Alfredo Anderson
Public bug reported:

Can't get the US122 MKII listed as an input device.

Not in pavucontrol, nor in sound settings nor in jackd.

May be this helps,

alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII
jackdmp 1.9.12
...
Acquire audio card Audio1
creating alsa driver ... hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to 
playback-only mode
...

Please let me know if you need further information.

Regards, Alfredo

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alfredo7890 F pulseaudio
 /dev/snd/controlC1:  alfredo7890 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  6 22:02:55 2018
InstallationDate: Installed on 2018-03-03 (187 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e   
o r   d i r e c t o r y
Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 8 8 :   a u d i 
o   o p e n   e r r o r :   N o   s u c h   f i l e   o r   d i r e c t o r y
Symptom_Card: TASCAM US-122mkII - US122 MKII
Symptom_Type: None of the above
Title: [USB-Audio - US122 MKII, recording] Recording problem
UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago)
dmi.bios.date: 03/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N-MX SE Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [USB-Audio - US122 MKII, recording] Recording problem

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

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

[Bug 1773859] Re: upgrades to 18.04 fail

2018-08-24 Thread David Anderson
I thought one aspect of the bug that nobody specifically highlighted was
interesting:

dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed

Notice the replacement has an extra .systemd on the end of the name.

The fix instructions reported above worked for me.

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

Title:
  upgrades to 18.04 fail

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

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

[Bug 1788472] [NEW] installling Bungie , the grub failed to install onto the EFI partition

2018-08-22 Thread Eric Anderson
Public bug reported:

I always get this error on numerous attempts to install Ubuntu 18.4 of
any flavor.  Even though i get this error, when restarting I have no
problem boot into Ubuntu after removing installer USB. But not always.

INFO:

Ubuntu 18.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Wed Aug 22 12:03:19 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-budgie.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu-budgie

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

Title:
  installling Bungie  , the grub failed to install onto the EFI
  partition

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

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

[Bug 1787127] Re: java Corrupted page table

2018-08-16 Thread Dale C. Anderson
@ggrandes: I experienced that reboot loop on one my aws machines (with
3.13.0-155-generic) today too. Stopping the machine from the web UI and
bringing it back up stopped the loop, and the machine stayed up, if that
helps at all.

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

Title:
  java Corrupted page table

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

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

[Bug 1786195] Re: broken audio/muffled, no system audio

2018-08-09 Thread Dominic Anderson
"16.04 used kernel 4.4 and you are presently using kernel 4.15"

Have been running 18.04 for a week. Until earlier today issue was not
present, each day until now however, had been just fine. Is "4.15" the
same kernel used at install of "18.04"?

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1786195] Re: broken audio/muffled, no system audio

2018-08-09 Thread Dominic Anderson
uname -a
Linux novgorod-LinuxBook 4.4.146-0404146-generic #201808061143 SMP Mon Aug 6 
15:51:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1786195] Re: broken audio/muffled, no system audio

2018-08-09 Thread Dominic Anderson
Over-Amplification is set to "OFF"

Test Speakers returned no sound from either left or right speaker.

Previous version of Ubuntu "16.04 LTS"

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1786195] [NEW] broken audio/muffled, no system audio

2018-08-09 Thread Dominic Anderson
Public bug reported:

Ubuntu 18.04.1 LTS
pulseaudio:
  Installed: 1:11.1-1ubuntu7.1
  Candidate: 1:11.1-1ubuntu7.1
  Version table:
 *** 1:11.1-1ubuntu7.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:11.1-1ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages


expected sound to return to normal/crisp throughout system and media 
applications.

sound became muffled/distorted throughout all media applications, while
other system sounds failed altogether. volume up/down failed. Chime on
reboot also distorted. system and application sounds appear normal when
used via bluetooth.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  novgorod   1787 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  9 01:40:50 2018
InstallationDate: Installed on 2018-08-01 (7 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/18
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB61.88Z.00CC.B00.1802021826
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22C8AC8
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22C8AC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8:
dmi.product.family: MacBook
dmi.product.name: MacBook6,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic

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

Title:
  broken audio/muffled, no system audio

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

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

[Bug 1784669] [NEW] package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias d

2018-07-31 Thread Anderson Porto
Public bug reported:

I was trying to install nautilus-image-converter-0-3-1-en-ubu.deb and
then crashed!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libunity9 7.1.4+18.04.20180209.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 31 13:03:49 2018
ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, 
que é diferente de outras instâncias do pacote libunity9:i386
InstallationDate: Installed on 2018-05-15 (76 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: libunity
Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to
  install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader'
  partilhado, que é diferente de outras instâncias do pacote
  libunity9:i386

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

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

[Bug 1774890] [NEW] Stopping typing every second when prompted for a password.

2018-06-03 Thread Anderson Fratuci
Public bug reported:

Stopping typing every second when prompted for a password.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompositorRunning: None
Date: Sun Jun  3 16:57:33 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2018-05-14 (20 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20B7A0S4BR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=120c671a-235c-462b-966e-ba1fe93b341f ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET77WW (2.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B7A0S4BR
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20B7A0S4BR:pvrThinkPadT440:rvnLENOVO:rn20B7A0S4BR:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440
dmi.product.name: 20B7A0S4BR
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Stopping typing every second when prompted for a password.

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

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

[Bug 1769410] [NEW] Some GNOME apps are not appearing on store.

2018-05-05 Thread Anderson de Araujo
Public bug reported:

Hi,
I m using Ubuntu Budgie 18.04 32-bits LTS.

A lot snap apps are not appearing on my Store, likes Spotify, Brave... When I 
try install Spotify from the Spotify website, I have a message: “dont know how 
to handle snap//spotify”.
Its happening with "repository apps" too, that I try install on Tilix: I have 
installed Opera Browser (opera-stable), but after the instalation, it does not 
appear in mine programs.

Someone can help me? (PS: I’m new to Ubuntu, and I know almost nothing.)

My PC: 
Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4
RAM 4 GB
Graphics Intel® G33 x86/MMX/SSE2
GNOME 3.28.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
CurrentDesktop: Budgie:GNOME
Date: Sat May  5 20:26:59 2018
InstallationDate: Installed on 2018-05-05 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

** Attachment added: "Print screen: i search Spotify, but have no results"
   
https://bugs.launchpad.net/bugs/1769410/+attachment/5134593/+files/Captura%20de%20tela%20de%202018-05-05%2020-59-15.png

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

Title:
  Some GNOME apps are not appearing on store.

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

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

[Bug 1769299] [NEW] universal access zoom unusable

2018-05-04 Thread Ken Anderson
Public bug reported:


Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 point 
type without magnification at normal reading distance and can barely read the 
universal access "large text" from a distance of about 2.5 inches from a 26inch 
monitor at 1360x768.   So he really needs magnification and a lot more than the 
2x default I used here for testing.   We do not live in the same town so 
providing additional details would be slow.

Turned on zoom from the universal access button on top panel.
Default settings were used including Zoom = 2.0, screen part = full

Several areas are corrupted.  These zoom and scroll separately from the
rest of the screen and in a way that severely impairs use as portions
may not ever be visible.   Portions of these subwindows cannot be used
because you have to move the mouse off them to be able see them so you
can either see or click but not both.

These areas are:
  - The top panel
  - The left panel (launcher)  (intermittently)
  - pull down menus, particularly the universal access pull down from the top 
panel


Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

These problems persisted with all the other zoom modes.   One mode,
however, created new bugs.  With "magnifier extends outside of screen",
you lose the ability to see the top and left panels at all; you can pan
over where they would be but they are not drawn.   Can't open the
pulldown menu since there is no icon, so who knows how it would be
rendered.

These bugs made it very difficult to get screenshots, especially with
the defective screenshot program gnome-screenshot which ships with
system.   Also, the bug-reporting program did not permitted attaching
additional screenshots once spectacle was installed.

Ubuntu 18.04, fresh install, only a few added packages (ham radio
related, chrome).  Not using wayland, though a wayland session runs
concurrently with X11 even though no one has logged in with wayland.

Another problem in making the bug report is the irresponsible practice
of failing to identify the software being used.   The accessability man
in circle menu does not have a heading to tell you what program is run
for the accessability menu or any of the functions thus invoked.Nor
does the settings.  And there is no tooltip, popup, or about menu item
to convey this information to the user.   And running a diff on ps
doesn't show any new processes started when zoom is turned on.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 00:04:35 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1163]
InstallationDate: Installed on 2018-05-05 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. OptiPlex 760
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0M858N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "bug_screenshot_0004.png"
   

[Bug 1769299] Re: universal access zoom unusable

2018-05-04 Thread Ken Anderson
added screenshot

** Attachment added: "Screenshot_20180505_005303.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769299/+attachment/5134203/+files/Screenshot_20180505_005303.png

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

Title:
  universal access zoom unusable

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

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

[Bug 1769299] Re: universal access zoom unusable

2018-05-04 Thread Ken Anderson
added screenshot

** Attachment added: "Screenshot_20180505_005450.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769299/+attachment/5134204/+files/Screenshot_20180505_005450.png

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

Title:
  universal access zoom unusable

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

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

[Bug 1765726] Re: libgoo-canvas-perl [needs-packaging]

2018-04-28 Thread Nick Anderson
I have been using shutter for years and this got me today as well after
upgrading to 18.04. I found flameshot
https://github.com/lupoDharkael/flameshot and it seems to have the
fundamentals. Still I prefer shutter, but I thought I would suggest an
alternative.

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

Title:
  libgoo-canvas-perl [needs-packaging]

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

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

[Bug 1767463] [NEW] VM Creation under VMware failed horrifically

2018-04-27 Thread Malcolm Anderson
Public bug reported:

No idea, this is an auto generated issue

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CasperVersion: 1.376.2
Date: Fri Apr 27 11:06:59 2018
InstallCmdLine: initrd=initrd.lz file=/cdrom/preseed/ubuntu.seed boot=casper 
quiet splash --- debian-installer/custom-installation=/custom 
find_preseed=/preseed.cfg auto preseed/file=/floppy/preseed.cfg 
automatic-ubiquity noprompt priority=critical locale=en_US 
console-setup/modelcode=evdev BOOT_IMAGE=vmlinuz
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 ubiquity-2.21.63.4 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/1767463

Title:
  VM Creation under VMware failed horrifically

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

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

[Bug 1766747] [NEW] package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

2018-04-24 Thread Anderson Santiago
Public bug reported:

doesnt work

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apt-config-icons (not installed)
ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
Uname: Linux 4.15.0-19-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Tue Apr 24 20:50:23 2018
DuplicateSignature:
 package:apt-config-icons:(not installed)
 Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ...
 dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
 dpkg: error processing archive 
/tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack):
  dpkg-deb --control subprocess returned error exit status 127
ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6~beta1
SourcePackage: appstream
Title: package apt-config-icons (not installed) failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package apt-config-icons (not installed) failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 127

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

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

[Bug 1766743] [NEW] package shim-signed 1.34.6+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

2018-04-24 Thread Anderson Santiago
Public bug reported:

trying to install anything gives me this error. tried to install the
steam program lots of times, every possible way, but it always fail.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.6+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
Uname: Linux 4.15.0-19-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Arquivo ou diretório 
inexistente: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
BootEFIContents:
 fw
 fwupx64.efi
Date: Tue Apr 24 20:37:38 2018
DpkgTerminalLog:
 Configurando shim-signed (1.34.6+13-0ubuntu2) ...
 Instalando para a plataforma x86_64-efi.
 grub-install: erro: cannot find EFI directory.
 dpkg: erro ao processar o pacote shim-signed (--configure):
  installed shim-signed package post-installation script subprocess returned 
error exit status 1
EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI 
variables are not supported on this system.
EFITables:
 
ErrorMessage: installed shim-signed package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6~beta1
SourcePackage: shim-signed
Title: package shim-signed 1.34.6+13-0ubuntu2 failed to install/upgrade: 
installed shim-signed package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package shim-signed 1.34.6+13-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1766743/+subscriptions

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

[Bug 1765901] [NEW] while installing I got the fatil error boot loader install failed

2018-04-20 Thread Bill Anderson
Public bug reported:

There are no logs to attach as the installation failed. I attempted the
install twice and both times I got the same error. "boot loader failed
to install".

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.387
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 23:49:07 2018
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 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 artful

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

Title:
  while installing I got the fatil error boot loader install failed

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

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

[Bug 1763371] Re: rtl8188ee wifi doesn't work in bionic

2018-04-13 Thread Anderson Luiz Alves
doesn't work on v4.16

doesn't work with:
linux-image-4.16.2-041602-generic_4.16.2-041602.201804121130_amd64.deb
linux-image-4.16.1-041601-generic_4.16.1-041601.201804081334_amd64.deb
linux-image-4.16.0-041600-generic_4.16.0-041600.201804012230_amd64.deb
linux-image-4.15.17-041517-generic_4.15.17-041517.201804120730_amd64.deb
linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb
linux-image-4.15.0-041500rc1-generic_4.15.0-041500rc1.201711262030_amd64.deb

works with:
linux-image-4.14.34-041434-generic_4.14.34-041434.201804120731_amd64.deb
linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb


** Tags added: kernel-bug-exists-upstream

** 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/1763371

Title:
  rtl8188ee wifi doesn't work in bionic

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

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

[Bug 1758398] Re: nautilus doesn't show mounts from pam_mount or cmdline on bionic

2018-04-13 Thread Anderson Luiz Alves
x-gvfs-show doesn't work either
https://gitlab.gnome.org/GNOME/nautilus/issues/362

** Summary changed:

- nautilus doesn't show network shares on 18.04
+ nautilus doesn't show mounts from pam_mount or cmdline on bionic

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

Title:
  nautilus doesn't show mounts from pam_mount or cmdline on bionic

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

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

[Bug 1763371] [NEW] rtl8188ee wifi doesn't work in bionic

2018-04-12 Thread Anderson Luiz Alves
Public bug reported:

In Bionic with kernel 4.15 when connecting rtl8188ee wifi to WPA2
Enterprise it doesn't get ip address.

It worked with kernel 4.13 from Artful.

Also works with: https://github.com/lwfinger/rtlwifi_new

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


** Tags: bionic

** Attachment added: "ubuntu-bug linux"
   https://bugs.launchpad.net/bugs/1763371/+attachment/5112133/+files/rtlwifi

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

Title:
  rtl8188ee wifi doesn't work in bionic

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

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

[Bug 1760452] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

2018-04-01 Thread LaToya Anderson via ubuntu-bugs
*** This bug is a duplicate of bug 1760451 ***
https://bugs.launchpad.net/bugs/1760451

Public bug reported:

Every time I start up my OS it has an internal error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.11
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sun Apr  1 11:48:30 2018
DuplicateSignature:
 package:initramfs-tools:0.122ubuntu8.11
 Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
 awk: fatal error: internal error
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script returned error exit status 134
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2016-09-22 (555 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 134
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 134

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

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

[Bug 1760451] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

2018-04-01 Thread LaToya Anderson via ubuntu-bugs
Public bug reported:

Every time I start up my OS it has an internal error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.11
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sun Apr  1 11:48:30 2018
DuplicateSignature:
 package:initramfs-tools:0.122ubuntu8.11
 Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
 awk: fatal error: internal error
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script returned error exit status 134
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2016-09-22 (555 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 134
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 134

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

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

[Bug 1758398] Re: nautilus doesn't show network shares on 18.04

2018-03-27 Thread Anderson Luiz Alves
Someone reported it.
https://gitlab.gnome.org/GNOME/nautilus/issues/312

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

Title:
  nautilus doesn't show network shares on 18.04

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

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

  1   2   3   4   5   6   7   8   9   10   >