date:20200427

** No longer affects: bluez (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1366418

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
  [0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 
SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
  [0.261179] pnp 00:0a: Plug and Play ACPI device, IDs ATK3001 PNP030b 
(active)
  [

[Touch-packages] [Bug 1875113] Re: Opengl no detected

Hmm, Nvidia recommends driver version 390 for your GeForce GT 635M and
that's what you have...


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: nvidia

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Opengl no detected
+ OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875113

Title:
  OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The screen presents screen tearing in the browser, on the desktop as
  well and when installing Steam it says that it does not detect Opengl
  or any video card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/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:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:01:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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 N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

2020-04-27 Thread Douglas Silva

Oh, I can finally hear sound through the earphones by changing the
capture source. Too bad the change doesn't persist after I remove and
reinsert the connector. Every time that happens, I must change it to
Headset Mic, otherwise there will be no sound output.

It also works when I do it through the Pulseaudio GUI mixer that comes
with Xubuntu. Now I just wish the default selection could be one that
works out of the box, as it was in previous Ubuntu versions.

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
[Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
sound output from earphones

Status in alsa-driver package in Ubuntu:
New

Bug description:
Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
no sound output when you plug an earphone/headset. The built-in
speakers, on the other hand, are working properly. This is a laptop,
Dell Inspiron 11 3162.

I checked volume levels with alsamixer, I played with the device
selection in the Pulseaudio mixer application, but nothing worked. I
also tested Firefox (playing a YouTube video) and system sounds. None
of them worked. The audio test made by apport-bug played no sound
through the earphone.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Apr 26 18:12:06 2020
InstallationDate: Installed on 2020-04-24 (2 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0NM68T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.sku: 0725
dmi.product.version: 2.4.0
dmi.sys.vendor: Dell Inc.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875073] Re: Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

It appears you are using graphics packages from the 'oibaf' PPA, which
is not supported and is known to be buggy.

Please remove that PPA from your system and if the problem persists then
open a new bug.



** Changed in: xorg (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875073

Title:
  Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I'm experiencing a problem extremely similar to 
https://gitlab.freedesktop.org/drm/intel/-/issues/272
  My screen flickers too on a fresh install of Kubuntu 20.04LTS 
https://imgur.com/a/FoWI1sp

  Results of `inxi -Gx`  
  `
  Graphics:  Device-1: Intel Iris Plus Graphics G7 vendor: Lenovo driver: i915 
v: kernel bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.8 driver: modesetting resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel Iris Plus Graphics (ICL GT2) 
 v: 4.6 Mesa 20.1.0-devel (git-a64d266 2020-04-25 focal-oibaf-ppa) 
direct render: Yes 
  `

  I've tried 915.enable_psr=0 as a boot parameter, didn't work.
  nomodeset does get me into a bootable image, but I'm looking into getting a 
working driver.

  Fedora 31 was having a similar issue, there was barely any flickering up 
untill some recent kernel updates. (about a couple small ones every 10 minutes 
or so)
  Kubuntu 19.10 was quite stable too, untill I installed a lenovo provided 
firmware update (from AUCN45WW to AUCN54WW), which made it slightly worse.
  I also tried a couple of other kernel parameters that haven't had any effect.
  Running kernel 5.6 on Kubuntu did have thesame issue as regular kubuntu 20.04.
  Running kernel 5.7-rc2 did fix the problem, but networking and sound was 
dead, so it's only half a solution.
  I highly suspect it's an issue with i915, but I don't know how I would trace 
it down.
  I don't know why and I don't know how.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr 25 20:49:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3801]
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81Q9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=5d977dfa-1fa5-412b-9d83-644cef18af6e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101+git2004241830.bf63f8~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004250730.a64d26~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875162] Re: Crash when using scummvm with SDL.

** Package changed: xorg (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875162

Title:
  Crash when using scummvm with SDL.

Status in Ubuntu:
  Invalid

Bug description:
  Relevant line from dmesg:

  [   44.809342] scummvm[2866]: segfault at a0 ip 7f203f4a3838 sp 
7ffc2144a5e0 error 4 in iris_dri.so[7f203ea73000+d48000]
  [   44.809349] Code: 44 24 18 48 c7 44 24 10 00 00 00 00 48 c7 44 24 18 00 00 
00 00 50 4c 8d 4c 24 18 e8 d2 0b b6 ff 48 8b 44 24 18 31 d2 48 89 ef <4c> 8b b0 
a0 00 00 00 4c 89 f6 e8 79 91 fd ff 48 8b bd 28 01 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  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 Apr 26 11:58:21 2020
  DistUpgraded: 2020-04-23 22:04:58,240 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-48-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-10-07 (201 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (2 days ago)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875533] [NEW] [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

2020-04-27 Thread ernestrayb...@hotmail.com

Public bug reported:

This problem happens on YouTube videos. It's almost like the sound is
muted where you can hear something  but not make it out.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ernest 1080 F pulseaudio
 /dev/snd/controlC0:  ernest 1080 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 11:21:04 2020
InstallationDate: Installed on 2020-04-25 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ernest 1080 F pulseaudio
 /dev/snd/controlC0:  ernest 1080 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B.10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-VDH MAX (MS-7A38)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 8.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 8.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A38
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 8.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1875533

Title:
  [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem happens on YouTube videos. It's almost like the sound is
  muted where you can hear something  but not make it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ernest 1080 F pulseaudio
   /dev/snd/controlC0:  ernest 1080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 11:21:04 2020
  InstallationDate: Installed on 2020-04-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 
successful
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ernest 1080 F pulseaudio
   /dev/snd/controlC0:  ernest 1080 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-VDH MAX (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 8.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 8.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 8.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go

[Touch-packages] [Bug 1861250] Re: Apparmor error failed to start profiles

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861250

Title:
  Apparmor error failed to start profiles

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  OS Ubuntu focal fossa 20.04
  On boot error message - Apparmor Failed to start profiles.

  Steps attempted to correct

  1.sudo as status

  lee@lee-desktop:~$ sudo aa-status
  apparmor module is loaded.
  53 profiles are loaded.
  51 profiles are in enforce mode.
 /sbin/dhclient
 /snap/core/8268/usr/lib/snapd/snap-confine
 /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/bin/evince
 /usr/bin/evince-previewer
 /usr/bin/evince-previewer//sanitized_helper
 /usr/bin/evince-thumbnailer
 /usr/bin/evince//sanitized_helper
 /usr/bin/man
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/lightdm/lightdm-guest-session
 /usr/lib/lightdm/lightdm-guest-session//chromium
 /usr/lib/snapd/snap-confine
 /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/lib/telepathy/mission-control-5
 /usr/lib/telepathy/telepathy-*
 /usr/lib/telepathy/telepathy-*//pxgsettings
 /usr/lib/telepathy/telepathy-*//sanitized_helper
 /usr/lib/telepathy/telepathy-ofono
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/ippusbxd
 /usr/sbin/tcpdump
 /usr/share/hplip/plugin.py
 /usr/share/hplip/sendfax.py
 /usr/share/hplip/setup.py
 /usr/share/hplip/systray.py
 /usr/share/hplip/toolbox.py
 libreoffice-senddoc
 libreoffice-soffice//gpg
 libreoffice-xpdfimport
 lsb_release
 man_filter
 man_groff
 nvidia_modprobe
 nvidia_modprobe//kmod
 snap-update-ns.core
 snap-update-ns.gnome-calculator
 snap-update-ns.gnome-characters
 snap-update-ns.gnome-logs
 snap-update-ns.gnome-system-monitor
 snap.core.hook.configure
 snap.gnome-calculator.gnome-calculator
 snap.gnome-characters.gnome-characters
 snap.gnome-logs.gnome-logs
 snap.gnome-system-monitor.gnome-system-monitor
 system_tor
  2 profiles are in complain mode.
 libreoffice-oopslash
 libreoffice-soffice
  3 processes have profiles defined.
  3 processes are in enforce mode.
 /usr/lib/telepathy/mission-control-5 (3090) 
 /usr/sbin/cupsd (1646) 
 /usr/bin/tor (1861) system_tor
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.
  lee@lee-desktop:~$ 

  2.sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  3.sudo rm -rf /etc/apparmor.d/cache/*

  4. sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  Thanks,

  Lee

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 23:19:19 2020
  InstallationDate: Installed on 2013-08-08 (2365 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  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-12-generic 
root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Looking at this: https://bugzilla.kernel.org/show_bug.cgi?id=205959 i tried 
editing the 
/etc/modprobe.d/alsa.conf to have the option... restarted... same output

** Attachment added: "alsa.conf_options"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+attachment/5362188/+files/alsa.conf_options

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

hmm... it says that same message here

snd-intel-dspcfg.dsp_driver=1 is set in the command line.  But later on
it says i should pass that option.

** Attachment added: "with_dspcfg.dsp_driver=1"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+attachment/5362187/+files/with_dspcfg.dsp_driver%3D1

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1874717] Re: devices cannot connect to ubuntu hotspot

2020-04-27 Thread Amartya Ghosh

I started my hotspot at 9:18...This is the log file since

On Mon, 27 Apr 2020 at 18:41, Sebastien Bacher 
wrote:

> $ journalctl -b 0 > log
>
> and add the 'log' file to the bug
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874717
>
> Title:
>   devices cannot connect to ubuntu hotspot
>
> Status in network-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
>   based internet connection to my ubuntu system via the hotspot
>   connection to my other devices.I am able to connect to my hospot
>   though. My ethernet connection works fine hotspot too but my devices
>   report:"This device has no connection to internet."Earlier in v18.04
>   it worked fine.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubuntu-release-upgrader-core 1:20.04.18
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashDB: ubuntu
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 24 17:49:30 2020
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: dist-upgrade
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   VarLogDistupgradeTermlog:
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 20.04
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   IpRoute:
>default via 10.20.2.1 dev enp2s0 proto static metric 100
>10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric
> 100
>10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric
> 600
>169.254.0.0/16 dev enp2s0 scope link metric 1000
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: network-manager 1.22.10-1ubuntu1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Tags:  focal
>   Uname: Linux 5.4.0-26-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.22.10  connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874717/+subscriptions
>


** Attachment added: "logfile"
   https://bugs.launchpad.net/bugs/1874717/+attachment/5362186/+files/logfile

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Maybe it's the "HP Wide Vision FHD Camera" which should be treated as a
camera and microphone?  i see it register with uvcvideo in both.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2020-04-27 Thread clickwir

Fixed my problem.

While looking through /var/log/syslog, I noticed this line around the
same time swap mount failed.

BTRFS warning (device sda3): swapfile must not be copy-on-write

Then a few lines later...

systemd[1]: swap.img.swap: Failed with result 'exit-code'.
systemd[1]: Failed to activate swap /swap.img.
systemd[1]: Dependency failed for Swap.
systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.

Yes my root is on btrfs and I did not see this error before. So I
deleted /swap.img and started over.

$ sudo rm -rf /swap.img
$ sudo touch /swap.img
$ sudo chattr +C /swap.img
$ sudo fallocate -l 2G /swap.img
$ sudo chmod 600 /swap.img
$ sudo mkswap /swap.img
$ sudo swapon /swap.img

No error and "swapon --show" gives this:

NAME  TYPE SIZE USED PRIO
/swap.img file   2G   0B   -2

Just what I was expecting. So problem solved for me, maybe a check can
be put in to see if it's on btrfs and apply the 'chattr +C' option.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788321

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

and this is dmesg with the dmic_setting

** Attachment added: "with_dmic_setting"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+attachment/5362180/+files/with_dmic_setting

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

OK, Let's see if this helps you narrow it down.  This file is with
dmic_setting=0 removed from the grub cmdline

** Attachment added: "no_dmic_setting"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+attachment/5362179/+files/no_dmic_setting

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875465] Re: none

** Package changed: xorg (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875465

Title:
  none

Status in Ubuntu:
  Incomplete

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 12:12:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05be]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] 
[1002:6606] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2020-04-11 (16 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude E6540
  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-96-generic 
root=UUID=dfd03262-1b27-47a5-9143-e19ca5a8e933 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0VPH0Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0VPH0Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874505] Re: start key

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1874505

Title:
  start key

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  when i press start key in my laptop it's shown search page and when i
  press start key again it's not gone

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-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.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  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: Thu Apr 23 22:15:25 2020
  DistUpgraded: 2020-04-23 21:07:17,632 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.0.0-37-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d8d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d8d]
  InstallationDate: Installed on 2020-01-07 (107 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: ASUSTeK COMPUTER INC. N552VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=c1ceff9f-cd7b-4287-b846-9a29132765e3 ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN552VW.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  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
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875036] Re: bridge stops working on focal update

2020-04-27 Thread Rafael David Tinoco

Hello Javier,

Actually the release notes for the version you were at:

https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#netplan.io

already deprecated ifupdown in favor of netplan.io.

Upgrade path to 20.04 has likely uninstalled bridge-utils because of
that. You can keep using ifupdown + vlan + bridge-utils + net-tools but
do have in mind that those tools are being deprecated in favor of:
systemd-networkd, netplan.io, iproute2, etc.

Good examples on how to obtain the same result using netplan.io can be
found at:

https://netplan.io/examples

For now I'm marking this as a Invalid bug. If think there is anything
else on this topic I would suggest writing to Ubuntu Users mailing list,
a correct place for community-based technical support.

Best regards,

Rafael D. Tinoco



** Changed in: bridge-utils (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1875036

Title:
  bridge stops working on focal update

Status in bridge-utils package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I don't know if this is the right package to report but: I have
  upgraded to 20.04 from 18.04 and my network stopped working. Problem
  was that bridge-utils package was uninstalled, so network was unable
  to start. Reinstalling the package solved the problem. But I don't
  understand why it was uninstalled. I have reviewed the release note
  for 20.04 and I haven't seen the problem, so I'm reporting in case in
  can help anyone.

  Regards

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-04-27 Thread Sebastian Unger

Ok, this is interesting. I just downgraded to bionic (18.04) and now the
dongle is working! So something went wrong somewhere along the way but
the H/W is definitely good.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1873718

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1859862] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1859862

Title:
  networkd doesn't re-enable ipv6 unless mtu is set

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  if the 'disable_ipv6' procfs setting is disabled, and networkd is
  configured with ipv6 networking, networkd will not enable ipv6 via the
  procfs setting unless the interface mtu is also set to a custom value,
  that doesn't match the current interface mtu.

  [test case]

  create networkd config similar to:

  [Match]
  MACAddress=52:54:00:0c:09:77
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  Note that with the mtu set, it will successfully re-enable ipv6;
  modify the networkd config to set the mtu by adding this:

  [Link]
  MTUBytes=1400

  (be sure to set the MTU config to something other than its current
  mtu)

  verify ipv6 is still disabled and has no addresses, then restart and
  check again:

  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  0
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  2: ens3:  mtu 1400 state UP qlen 1000
  inet6 2001:db8::100/64 scope global
     valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe0c:977/64 scope link
     valid_lft forever preferred_lft forever

  That should be the behavior even if MTUBytes is not set.

  [regression potential]

  as this adjusts when the procfs 'disable_ipv6' setting is changed, the
  regression potential could cause failure to properly set/create ipv6
  addresses, or to leave ipv6 disabled entirely.

  [scope]

  This is needed in Bionic and Eoan.

  the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765
  which is included starting in v243, so it is included already in
  Focal.

  Ignoring Disco, as it is EOL next week.

  This problem was introduced by commit
  44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting
  in v239, but also backported to Bionic in bug 1850704.

  [other info]

  for Eoan, this bug has always existed since release, but for Bionic,
  this is a regression introduced by bug 1850704.  However, manual
  disabling of ipv6 is very unusual, so this bug is unlikely to have an
  impact to many systems.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1858412] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1858412

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit
  c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in
  version 244, so this is already included in Focal.  This is needed for
  Eoan, Bionic, and Xenial.

  [original description]

  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1776654] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776654

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  TEST-21-SYSUSERS autopkgtest fails

  [test case]

  see original description

  [regression potential]

  any regression would be limited to incorrect pass/fail of
  TEST-21-SYSUSERS

  [scope]

  TEST-21-SYSUSERS does not exist in Xenial, it is first contained in
  Bionic.  This is needed for B, E, and F.

  [original description]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2020-04-27 Thread Rustin Schenk

I also still have a crackling sound in the left channel when I plug in a
pair of headphones using an hp laptop.  I had this with 19.04,19.10 and
now still with 20.04. Would be nice if it could be fixed.   The solution
by Robert Joynt does fix the problem, but it is a work around.  Would be
nice if the real problem could be fixed in the distro.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1648183

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1862657] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1862657

Title:
  systemd autopkgtest 'logind' fails when running with linux-kvm

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  the logind autopkgtest tries to access /sys/power/state, but because
  linux-kvm has CONFIG_PM unset, there is no /sys/power/state file

  [test case]

  check autopkgtest, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  autopkgtest [13:48:53]: test logind: ---]
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - results - - - - - - 
- - - -
  logind   FAIL stderr: grep: /sys/power/state: No such file or 
directory
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - stderr - - - - - - 
- - - -
  grep: /sys/power/state: No such file or directory

  [regression potential]

  regressions would likely involve incorrectly skipped logind test.

  [scope]

  this fails for all releases; Xenial, Bionic, Eoan, and Focal.

  [other info]

  it's unclear if linux-kvm should have CONFIG_PM (and other config)
  enabled or not.

  However, it's not the intention of systemd's autopkgtests to look for
  missing config in the kernel; the test already skips if 'mem' isn't in
  /sys/power/state, so it should also skip if /sys/power/state isn't
  present at all.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1837914] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837914

Title:
  restart systemd-jounald fails

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  in some situations, restarting journald causes assertion failure.

  [test case]

  intermittently, when restarting journald.  See upstream bug for repro
  details.

  [regression potential]

  this adjusts the journal file destructor, so any regression would
  likely occur when cleaning up journal files and/or
  stopping/restarting.

  [scope]

  this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which
  is included in Focal.  This is needed for Eoan and earlier.

  [original description]

  While restarting systemd-jounald, the following error message occurs:

  systemd-journald[28007]: Assertion 'f' failed at ../src/journal
  /journal-file.c:143, function journal_file_close(). Aborting.

  release: Ubuntu 16.04.5 LTS
  systemd version: 229-4ubuntu21.22

  This issue is reported at
  https://github.com/systemd/systemd/issues/12400 and solved at
  https://github.com/systemd/systemd/pull/12679

  Please cherry-pick this fix to the ubuntu16.04 package.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-04-27 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849156

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1868892] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1868892

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870811] Autopkgtest regression report (systemd/242-7ubuntu3.8)

All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.8 (ppc64el)
prometheus-postgres-exporter/unknown (armhf)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64)
snapd/2.42.1+19.10 (i386)
udisks2/unknown (armhf)
umockdev/0.13.2-1 (armhf)
sks/unknown (armhf)
network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64)
asterisk/unknown (armhf)
logrotate/unknown (armhf)
lxc/3.0.4-0ubuntu1 (i386)
netplan.io/0.98-0ubuntu1 (amd64)
dbus/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1870811

Title:
  compile auto test failure, and root-unittest failure, is extremely
  noisy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  failure in the compile-time tests (also run from the root-unittest
  autopkgtest) prints out the entire meson testlog.txt, which shows the
  output of all tests, including passed ones, not just the failed test
  output.  This makes it extremely difficult to find the output of the
  failed test(s) and creates a massive log to download.

  [test case]

  see any failed build, e.g.
  
https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz

  [regression potential]

  any regression would likely occur during test failure, likely
  resulting in lack of details of the test failure; or, a regression
  caused by the additional meson parameter could cause build failure.

  [scope]

  Xenial does not use meson, so can not be adjusted.  This is needed in
  Bionic and later.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875407] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1875407

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Received this error when doing do-release-upgrade from ubuntu 18.04.4
  to 20.4

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 09:59:42 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-12 (1567 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  PackageArchitecture: all
  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.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-27 Thread Chris Nichols

Also working for me.

Also of note, configuring the bridge via DHCP worked prior to the patch,
regardless of assigning a dynamic or static IP via the DHCP server.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860926

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service

[Touch-packages] [Bug 1875034] Re: login screen will put a character in the password box when pressing key to reomve lock screen

2020-04-27 Thread Seth Arnold

** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1875034

Title:
  login screen will put a character in the password box when pressing
  key to reomve lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I press a key to dismiss the lock screen, the key I pressed gets
  into the password box

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: login 1:4.8.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 10:39:40 2020
  InstallationDate: Installed on 2020-03-27 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-27 Thread Jane Atkinson

Also working here.

'networkctl status' shows:

●   State: routable
  Address: 192.168.1.65 on br0 
   192.168.122.1 on virbr0 
   fe80::3a2c:4aff:febd:306a on br0
  Gateway: 192.168.1.1 (PC Engines GmbH) on br0
  DNS: 192.168.1.1 

Apr 28 10:45:07 ja-desktop systemd-networkd[339]: rtnl: received neighbor for 
link '4' we don't know about, ignoring.
Apr 28 10:45:07 ja-desktop systemd-networkd[339]: rtnl: received neighbor for 
link '4' we don't know about, ignoring.
Apr 28 10:45:07 ja-desktop systemd-networkd[339]: rtnl: received neighbor for 
link '4' we don't know about, ignoring.
Apr 28 10:45:07 ja-desktop systemd-networkd[339]: rtnl: received neighbor for 
link '4' we don't know about, ignoring.
Apr 28 10:45:07 ja-desktop systemd-networkd[339]: virbr0-nic: Link UP
Apr 28 10:45:07 ja-desktop systemd-networkd[339]: virbr0-nic: Gained carrier
Apr 28 10:45:09 ja-desktop systemd-networkd[339]: virbr0-nic: Gained IPv6LL
Apr 28 10:45:12 ja-desktop systemd-networkd[339]: virbr0: Link UP
Apr 28 10:45:12 ja-desktop systemd-networkd[339]: virbr0-nic: Link DOWN
Apr 28 10:45:12 ja-desktop systemd-networkd[339]: virbr0-nic: Lost carrier
   

Many thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860926

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26

[Touch-packages] [Bug 1849835] Re: add-apt-repository does not work in focal

2020-04-27 Thread Eugene Minov

OK, but can you guide me please as to how to resolve this in case I upgraded 
and not installed anew?
Cause I installed all the updated but this error still persists..
Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1849835

Title:
  add-apt-repository does not work in focal

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  I tested to use a ppa because I wanted to test if mkusb will work in
  focal. But

  add-apt-repository

  does not work.

  ---
  lubuntu@lubuntu:~$ sudo add-apt-repository ppa:mkusb/ppa  # existing ppa
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/focal
  lubuntu@lubuntu:~$ sudo add-apt-repository ppa:qwerty/asdf  # not existing 
ppa: same output
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/focal
  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  lubuntu@lubuntu:~$ 
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-common 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.427
  CurrentDesktop: LXQt
  Date: Fri Oct 25 13:10:33 2019
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191024)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2020-04-27 Thread YannUbuntu

** Changed in: os-uninstaller
   Status: Fix Committed => Fix Released

** Changed in: boot-info
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all

[Touch-packages] [Bug 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

2020-04-27 Thread Jens Elkner

Łukasz Zemczak, yes, upgraded a machine from bionic to focal - same
problem. However, the patch looks not optimal but sufficient.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1868892

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875498] [NEW] smart-notifier installs, but has missing requirments

2020-04-27 Thread Colin Hemming

Public bug reported:

I installed this in a fresh install of Xubuntu 20.04.1 and, while it
installs, the file to which it links:

/usr/bin/smart-notifier -> ../share/smart-notifier/smart-notifier

does not exist, so it does not function at all!

--
Description:Ubuntu 20.04 LTS
Release:20.04

smart-notifier:
  Installed: 0.28-5build1
  Candidate: 0.28-5build1
  Version table:
 *** 0.28-5build1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1875498

Title:
  smart-notifier installs, but has missing requirments

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I installed this in a fresh install of Xubuntu 20.04.1 and, while it
  installs, the file to which it links:

  /usr/bin/smart-notifier -> ../share/smart-notifier/smart-notifier

  does not exist, so it does not function at all!

  --
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  smart-notifier:
Installed: 0.28-5build1
Candidate: 0.28-5build1
Version table:
   *** 0.28-5build1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875044] Re: Host name not resolved

2020-04-27 Thread Dan Streetman

You should check your system configuration, specifically how you have
resolved configured.  Try looking at the output of:

$ systemd-resolve --status


Since you haven't even mentioned what Ubuntu release you're using, that's about 
all I can suggest without more info.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1875044

Title:
  Host name not resolved

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Systemd-resolved fails to resolve a host which has a private IP address, even 
though its DNS entry is public. This happens even when I am connected to a VPN 
where the host resides.
  Interestingly, if I manually issue a `host -a` request, the host gets 
resolved, and further resolution works until its cached entry times out.

  Here's some hopefully helpful output of me running `nslookup` and
  `host`:

  # nslookup
  > presto.lmta.lt
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  *** Can't find presto.lmta.lt: No answer
  > server 8.8.8.8
  Default server: 8.8.8.8
  Address: 8.8.8.8#53
  > presto.lmta.lt
  Server:   8.8.8.8
  Address:  8.8.8.8#53

  Non-authoritative answer:
  Name: presto.lmta.lt
  Address: 10.41.0.118
  > server 127.0.0.53
  Default server: 127.0.0.53
  Address: 127.0.0.53#53
  > presto.lmta.lt
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  *** Can't find presto.lmta.lt: No answer
  [^D pressed]

  # host presto.lmta.lt
  [no output at all. I immediately run the next command]

  # host -a presto.lmta.lt
  Trying "presto.lmta.lt"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20532
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;presto.lmta.lt.  IN  ANY

  ;; ANSWER SECTION:
  presto.lmta.lt.   3599IN  A   10.41.0.118

  Received 48 bytes from 127.0.0.53#53 in 57 ms

  [then immediately afterwards:]
  # host presto.lmta.lt
  presto.lmta.lt has address 10.41.0.118

  # nslookup
  > presto.lmta.lt
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  Name: presto.lmta.lt
  Address: 10.41.0.118

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874501] Re: /dev/mapper/mpath* are not symlinks from udev consistently

2020-04-27 Thread Michael Hudson-Doyle

Actually it seems this was caused by subiquity running vgscan --mknodes
during block probing:

root@ubuntu-server:/# rm -rf /dev/mapper/mpath*
root@ubuntu-server:/# ls -l /dev/mapper/
total 0
crw--- 1 root root 10, 236 Apr 24 05:57 control
root@ubuntu-server:/# vgscan --mknodes
root@ubuntu-server:/# ls -l /dev/mapper/
total 0
crw--- 1 root root  10, 236 Apr 24 05:57 control
brw-rw 1 root disk 253,   0 Apr 27 21:16 mpatha
brw-rw 1 root disk 253,   1 Apr 27 21:16 mpatha-part1

retargeting bug...

** Package changed: multipath-tools (Ubuntu) => lvm2 (Ubuntu)

** Summary changed:

- /dev/mapper/mpath* are not symlinks from udev consistently
+ vgscan --mknodes creates block device multipath nodes in /dev/mapper

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1874501

Title:
  vgscan --mknodes creates block device multipath nodes in /dev/mapper

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  # apt-cache policy multipath-tools
  multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
   *** 0.8.3-1ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
  100 /var/lib/dpkg/status

  
  /dev/mapper/mpatha is symlink which points to ../../dm-X device

  /dev/mapper/mpath is block device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: multipath-tools 0.8.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  Date: Thu Apr 23 17:32:12 2020
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.multipath.conf:
   defaults {
   user_friendly_names yes
   skip_kpartx no
   verbosity 4
   }
  mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874501] [NEW] /dev/mapper/mpath* are not symlinks from udev consistently

You have been subscribed to a public bug:

Description:Ubuntu 20.04 LTS
Release:20.04

# apt-cache policy multipath-tools
multipath-tools:
  Installed: 0.8.3-1ubuntu2
  Candidate: 0.8.3-1ubuntu2
  Version table:
 *** 0.8.3-1ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
100 /var/lib/dpkg/status


/dev/mapper/mpatha is symlink which points to ../../dm-X device

/dev/mapper/mpath is block device

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: multipath-tools 0.8.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: s390x
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Thu Apr 23 17:32:12 2020
LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: multipath-tools
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.multipath.conf:
 defaults {
 user_friendly_names yes
 skip_kpartx no
 verbosity 4
 }
mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

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


** Tags: apport-bug curtin focal rls-gg-incoming s390x subiquity uec-images
-- 
/dev/mapper/mpath* are not symlinks from udev consistently
https://bugs.launchpad.net/bugs/1874501
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lvm2 in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2020-04-27 Thread Fabrício Pereira

I uninstalled the network-manager, and started using the traditional
Linux networking service with wpa_supplicant, but the problem continues.

The wifi connects and ping to my router IP. But seems to don't lookup
over DNS correctly.

$ systemd-resolve --status
Global
 DNS Servers: 8.8.8.8
  181.213.132.2
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 3 (wlp2s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 2 (enp1s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1666432

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2020-04-27 Thread Fabrício Pereira

I uninstalled the network-manager, and started using the traditional
Linux networking model, but the problem continues.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1666432

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage

[Touch-packages] [Bug 1874819] Re: Cannot change display driver in Software & Updates

Thanks

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1874819

Title:
  Cannot change display driver in Software & Updates

Status in software-properties package in Ubuntu:
  New

Bug description:
  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
  to nouveau and restart, the Software & Updates does not allow me to
  change back to the proprietary drivers, as the buttons are now greyed
  out.

  Workaround:
  sudo ubuntu-drivers devices  # shows available drivers
  sudo apt install nvidia-driver-440

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1571506] Re: update-initramfs won't include firmware in /lib/firmware/updates

Thank you for the report and the patch, I've subscribed ubuntu-sponsors
now. Could you maybe explain the practical impact/what problems it
creates?

** Tags added: rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1571506

Title:
  update-initramfs won't include firmware in /lib/firmware/updates

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  according to the kernel doc
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README

  Linux kernel will search firmware from
  "/lib/firmware/updates/" UTS_RELEASE,
  "/lib/firmware/updates",
  "/lib/firmware/" UTS_RELEASE,
  "/lib/firmware"

  But the add module function in initramfs-tools won't search the
  "/lib/firmware/updates".

  This problem applies to all Ubuntu releases.

  Attach patch to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:24:29 2016
  InstallationDate: Installed on 2014-04-23 (725 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875465] Re: none

Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875465

Title:
  none

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 12:12:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05be]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] 
[1002:6606] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2020-04-11 (16 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude E6540
  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-96-generic 
root=UUID=dfd03262-1b27-47a5-9143-e19ca5a8e933 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0VPH0Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0VPH0Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875005] Re: 3D acceleration not working with NVidia driver

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875005

Title:
  3D acceleration not working with NVidia driver

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  I have a laptop with both AMD Raven and Nvidia GTX 1050 video
  adapters. I wanted to test the new game mode in Ubuntu 20.04, and
  noticed that only the AMD Raven actually works. To do the test, I
  tried launching a terminal and running gxgears, both in a normal way,
  and then using the "start using dedicated video adapter" (or whatever
  it really is in English) option in gnome-shell.

  Using the standard video adapter (probably the AMD Raven), it works, but 
slowly.
  Using the dedicated video adapter, I get the following:

  juloliv@juloliv:~$ glxgears 
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  152 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  25
Current serial number in output stream:  26

  NB: in both cases, I tried launching nvidia-settings and got the
  following:

  juloliv@juloliv:~$ nvidia-settings

  ERROR: Unable to load info from any available system

  
  (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  ** Message: 12:33:29.273: PRIME: No offloading required. Abort
  ** Message: 12:33:29.273: PRIME: is it supported? no

  And then a blank window...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 25 12:26:50 2020
  DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1]
  InstallationDate: Installed on 2020-02-07 (77 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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:

[Touch-packages] [Bug 1875457] Re: Window system doesn't support OpenGL

Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875457

Title:
  Window system doesn't support OpenGL

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Failed to load module "canberra-gtk-module"

  (anydesk:13884): GdkGLExt-WARNING **: 12:32:22.222: Window system
  doesn't support OpenGL.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/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:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 12:34:53 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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 N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875000] Re: [HP Pavilion dv2500 Notebook PC, Conexant CX20549 (Venice), Speaker, Internal] fails after a while. The speaker in laptop turns on and off automatically during boot

2020-04-27 Thread Eduardo Barretto

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875000

Title:
  [HP Pavilion dv2500 Notebook PC, Conexant CX20549 (Venice), Speaker,
  Internal] fails after a while.  The speaker in laptop turns on and off
  automatically during boot time when I use Ubuntu and when I turn it
  off. It really troubles me a lot. Please help me as soon as possible
  for this problem and bring a solution.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem has started to occur since the day I installed Ubuntu on
  my laptop. I installed first Ubuntu 18.04 LTS and this problem
  occurred. The problem is that whenever I turn my laptop on then sound
  turns on and off automatically during boot time and the time I use
  this laptop and while turning it off also. I have recently installed
  Ubuntu 20.04 LTS in this laptop in a bid to get my problem solved but
  it went in vain and the problem still exists. Please help me out as it
  really troubles me a lot. Please find a solution to this problem as
  soon as possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kinshuk08   1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 03:13:06 2020
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [HP Pavilion dv2500 Notebook PC, Conexant CX20549 (Venice), Speaker, 
Internal] fails after a while
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
  dmi.bios.date: 05/28/2007
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.0A
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.0A:bd05/28/2007:svnHewlett-Packard:pnHPPaviliondv2500NotebookPC:pvrF.0A:rvnWistron:rn30CD:rvr80.27:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv2500 Notebook PC
  dmi.product.sku: GN395PA#ACJ
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875445] Re: Volume slider doesn't produce sound

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

apport-collect 1875445

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

** Package changed: alsa-driver (Ubuntu) => gnome-settings-daemon
(Ubuntu)

** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low

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

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875445

Title:
Volume slider doesn't produce sound

Status in gnome-settings-daemon package in Ubuntu:
Incomplete

Bug description:
Hello,
In Ubuntu 20.04:
After system boot there is sound and when I adjust volume with the slide (top
right corner of the screen) it produces default sound. About 10 minutes (may be
related to loading of certain s/w) later during the same session the slider
stops producing sound when I adjust volume. System sound is still present. I
also noticed that in Settings->Sound two more entries appear in "Volume
levels": 1. Speech-dispatcher-dummy; 2. Speech-dispatcher-espeak-ng. These two
entries are not present there right after system boot when everything works
fine. I also see these errors in Logs: "sof-audio-pci :00:1f.3: error: no
reply expected, received 0x0".
This bug is reproducible.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875465] Re: none

2020-04-27 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875465

Title:
  none

Status in xorg package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 12:12:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05be]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] 
[1002:6606] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2020-04-11 (16 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude E6540
  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-96-generic 
root=UUID=dfd03262-1b27-47a5-9143-e19ca5a8e933 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0VPH0Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0VPH0Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875483] [NEW] vulkan failed with ERROR_INITIALIZATION_FAILED

2020-04-27 Thread Vova

Public bug reported:

1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About 
Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04

2. The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
apt-cache policy mesa-vulkan-drivers
mesa-vulkan-drivers:
  Установлен: 20.0.4-2ubuntu1
  Кандидат:   20.0.4-2ubuntu1
  Таблица версий:
 *** 20.0.4-2ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3. What you expected to happen

run vulkaninfo
run vkcube

4. What happened instead

$ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

$ vkcube
vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
Аварийный останов (стек памяти сброшен на диск)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon Apr 27 22:47:58 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
 Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] 
[1002:6610] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
InstallationDate: Installed on 2020-04-23 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A58M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1875483

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in mesa package in Ubuntu:
  New

Bug description:
  1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 :

[Touch-packages] [Bug 1875465] [NEW] none