date:20190327

Do you encounter audio stuttering in any other apps?

** Package changed: alsa-driver (Ubuntu) => quodlibet (Ubuntu)

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

** Summary changed:

- [wma codec problem, playback] Playback problem
+ Audio sometimes stutters in Quod Libet in a VM

-- 
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/1821960

Title:
  Audio sometimes stutters in Quod Libet in a VM

Status in quodlibet package in Ubuntu:
  Incomplete

Bug description:
  The song Waterloo of ABBA plays correct with 
  Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
  Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
  I use Quod Libet as audio payer.
  The song plays for one second, halts for one second and than plays again for 
a second.
  I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1987 f pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 27 14:36:21 2019
  InstallationDate: Installed on 2018-11-08 (139 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/1821960/+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 1821936] Re: ALC274 unsupported

If the problem is the kernel version then please try to find the closest
two versions where one works and the other does not, from this list:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1821936

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1821936] Re: ALC274 unsupported

Derek, are you saying kernel 4.18 (or earlier) does not have the bug?

** Changed in: alsa-driver (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/1821936

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1821929] Re: Bluetooth mouse is not able to connect

I think we should work on releasing the gnome-bluetooth fix for bug
1773897 before assessing whether or not this is a different issue.

-- 
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/1821929

Title:
  Bluetooth mouse is not able to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I recently bought not expensive wireless mouse with bluetooth support:
  
https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS

  I works in MacOS X and Windows but doesn't work in Linux. I suppose I
  can debug that mouse under Windows to collect more information if I
  have proper instructions.

  I collected some information about that mouse:
  # uname -a
  Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  
  # lsb_release -a
  Distributor ID:Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:bionic

  
  # lsusb 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb)
  Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam)
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


  
  # usb-devices
  T:  Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#=  6 Spd=12  MxCh= 0
  D:  Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0bda ProdID=8763 Rev=02.00
  S:  Manufacturer=Realtek
  S:  Product=Bluetooth Radio
  S:  SerialNumber=00e04c01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb



  
  # bluetoothctl --version
  bluetoothctl: 5.48

  
  # hciconfig -a
  hci0:Type: Primary  Bus: USB
  BD Address: 94:E9:79:1A:89:1D  ACL MTU: 820:8  SCO MTU: 255:16
  UP RUNNING PSCAN 
  RX bytes:1604 acl:0 sco:0 events:170 errors:0
  TX bytes:28036 acl:0 sco:0 commands:166 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF PARK 
  Link mode: SLAVE ACCEPT 
  Name: 'asus-N752VX'
  Class: 0x1c010c
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Laptop
  HCI Version: 4.0 (0x6)  Revision: 0xe3e
  LMP Version: 4.0 (0x6)  Subversion: 0x4380
  Manufacturer: Realtek Semiconductor Corporation (93)

  
  # bluetoothctl
  [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default]
  [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0

  
  # show
  Controller 94:E9:79:1A:89:1D (public)
  Name: asus-N752VX
  Alias: asus-N752VX
  Class: 0x001c010c
  Powered: yes
  Discoverable: no
  Pairable: yes
  UUID: Headset AG(1112--1000-8000-00805f9b34fb)
  UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
  UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
  UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
  UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (5005--1000-8000-0002ee01)
  UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
  UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
  UUID: Headset   (1108--1000-8000-00805f9b34fb)
  Modalias: usb:v1D6Bp0246d0530
  Discovering: no

  
  # devices
  Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0

  
  # info 5A:4B:3C:0E:07:B2
  Device 5A:4B:3C:0E:07:B2 (public)
  Name: Bluetooth Mouse 4.0
  Alias: Bluetooth Mouse 4.0
  Class: 0x2580
  Icon: input-mouse
  Paired: yes
  Trusted: yes
  Blocked: no
  Connected: no
  LegacyPairing: no
  UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  Modalias: usb:v0A5Cp0001d0129

[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

Please run these commands:

1. apport-collect 1821904

2. dpkg -l > allpackages.txt

and then attach the file 'allpackages.txt' to this bug.

** Tags added: disco

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

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

-- 
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/1821904

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

Xubuntu daily images are still missing the fix for bug 1819943. So
please wait until a newer image is available which includes that fix
before retesting.

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1821609/+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 1821904] [NEW] Gnome Shell always started muted on Disco

You have been subscribed to a public bug:

On Disco, Gnome Shell always starts muted.

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


** Tags: disco
-- 
Gnome Shell always started muted on Disco
https://bugs.launchpad.net/bugs/1821904
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1807856] Re: During do-release-upgrade from 18.04 to 18.10: package lxd 3.0.2-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess retur

2019-03-27 Thread Seth Arnold

I added apport for the python2 -> python3 bug.

Thanks

** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  During do-release-upgrade from 18.04 to 18.10: package lxd
  3.0.2-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-
  installation script subprocess returned error exit status 1

Status in apport package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Upgrading apt version of lxd to snap version during do-release-upgrade
  failed.

  I attempted to update my ubuntu server 18.04 system to 18.10 as root:

  apt update
  apt dist-upgrade -y
  apt autoremove -y
  do-release-upgrade

  I have an existing LXD installed via apt, and running containers.

  It asked me which snap LXD to upgrade to, and I selected "latest".

  Console log:

  ==> Installing the LXD snap from the latest track for ubuntu-18.10
  error: cannot perform the following tasks:
  - Run install hook of "lxd" snap if present (run hook "install": cannot 
perform operation: mount /var/lib/snapd/hostfs/var/lib/lxd /var/lib/lxd -o 
nosuid,nodev,noexec,rbind,rslave: Permission denied)
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gdCSiW/32-lxd_1%3a0.4_all.deb (--unpack):
   new lxd package pre-installation script subprocess returned error exit 
status 1
  Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/apt/cache.py", line 265, in __getitem__
    
  rawpkg = self._cache[key]
    
   KeyError: 
'32-lxd'

  During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 126, in _apt_pkg
    
 return 
self._cache()[package]
    

File "/usr/lib/python3/dist-packages/apt/cache.py", line 267, in 
__getitem__
    raise KeyError('The cache has no 
package named %r' % key)
    
 KeyError: "The cache has no package named '32-lxd'"

  During handling of the above exception, another exception occurred:

   Traceback (most recent call last):
   File "/usr/share/apport/package_hook", 
line 48, in 
    
  pr['SourcePackage'] = 
apport.packaging.get_source(options.package)
    

  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 
159, in get_source
     if 
self._apt_pkg(package).installed:
    
   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 
128, in _apt_pkg
    

raise ValueError('package %s does not exist' % package)
   ValueError: package 32-lxd does not exist
    Preparing to unpack 
.../33-open-iscsi_2.0.874-5ubuntu9.1_amd64.deb ...
  Unpacking open-iscsi (2.0.874-5ubuntu9.1) over (2.0.874-5ubuntu2.4) ...
  Preparing to unpack .../34-poppler-data_0.4.9-2_all.deb ...
  Unpacking poppler-data (0.4.9-2) over (0.4.8-2) ...
  Preparing to unpack .../35-tasksel-data_3.34ubuntu12_all.deb ...
  Unpacking tasksel-data (3.34ubuntu12) over (3.34ubuntu11) ...
  Preparing to unpack .../36-tasksel_3.34ubuntu12_all.deb ...
  Unpacking tasksel (3.34ubuntu12) over (3.34ubuntu11) ...
  Preparing to unpack .../37-libsepol1_2.8-1_amd64.deb ...
  Unpacking libsepol1:amd64 (2.8-1) over (2.7-1) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-gdCSiW/32-lxd_1%3a0.4_all.deb
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** S

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

stranger and stranger .. if you install kernel 5.0.0-8.9 at the first
boot into any new install partition before changing any thing else .. it
does not fix the issue .. once you return sda1 to being grub master ..
neither sda7 nor sda6 will keep lightdm running ..both briefly flash
lightdm login screen and then blank out screen , briefly showing a
cursor .. a long hold down of power button does eventually powerdown
machine .. note: can't even get to consoles .. not a nice fail.

note resetting grub back to the "new install version" works but there
is a stutter in lightdm .. it shows briefly blanks for 2 seconds then
shows again and and you can login..

only other way into partition is through recovery boot option, or via a
chroot.

this is now using xubuntu-am64-desktop.iso -beta version ( two installs
sda6 and sda7 )

I'm beginning to think that using a chroot to reinstall/or update the
kernel might be a "work around only" for the issue .. as a native update
does not work ..

I'm going to test this further .. replace sda6 and sda7 sequentially and
see what happens using chroots for updates more later .. any ideas
what else to look for or check?

--
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/1821609

Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
New

Bug description:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..

back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively

on the test installs as long as the iso is using the grub boot loader
installed from that install the system will boot normally .. the display manger
tends to flicker on and off but does final start and login can proceed.

but if another install re-installs grub as master the display manager
fails to stay active or even come-up for sda6 or sda7 only if their
own grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work
by running dpkg fix which does nothing .. and then resuming the boot .. then
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power
down and reboot gives access. (sometime requiring radical depowering ..
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias:
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: li

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

2019-03-27 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821609

** Tags added: iso-testing

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses
kernel 5.0.0-7

updating from proposed with  kernel 5.0.0-8.9  it works properly

i.e. any linux os partion can be used to install grub and another partion with 
linux can be 
selected and boot normally 

e.g. beta install is on sda7 another linux os version is on sda1 which is used 
to install grub to /dev/sda  thus sda1 is master/main linix os used .. the beta 
on sda7 will start lightdm but it flickers on and dies when using kernel 
5.0.0-7 
but when using kernel 5.0.0-8.9 it works properly lightdm stays running and 
does  not even flicker...  the only apparent difference is the kernel selected 
..

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications ab

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

** This bug is no longer a duplicate of bug 1819943
   intel video driver not installed by default in ubuntu 19.04 (Disco) [needed 
for graphics support on Intel Core 2 Duo systems]

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1821609/+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 1821936] Re: ALC274 unsupported

Apologies my first run of apport was mainline 5.0. I immediately
rebooted and use a standard default kernel for 18.04. I deleted both
mainlines since they didn't solve my issue anyway.

-- 
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/1821936

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1821936] Re: ALC274 unsupported

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

-- 
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/1821936

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd

2019-03-27 Thread Stéphane Graber

** Changed in: lxd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1813622

Title:
  systemd-resolved, systemd-networkd and others fail to start in lxc
  container with v240 systemd

Status in lxd:
  Fix Released
Status in systemd:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This is a regression from 239-7ubuntu15 to 240-5ubuntu1.

  Steps to reproduce:

  lxc launch ubuntu-daily:disco rbasak-resolv
  lxc exec rbasak-resolv bash
  systemctl status systemd-resolved  # observe running
  echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe 
multiverse restricted" >> /etc/apt/sources.list
  apt update
  # Update to 240-5ubuntu1 from proposed
  apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd
  reboot
  lxc exec rbasak-resolv bash
  systemctl status systemd-resolved  # observe failed

  ● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 
28s ago
   Docs: man:systemd-resolved.service(8)
     https://www.freedesktop.org/wiki/Software/systemd/resolved
     
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
     
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
    Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, 
status=226/NAMESPACE)
   Main PID: 290 (code=exited, status=226/NAMESPACE)

  Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service 
has no hold-off time (RestartSec=0), scheduling restart.
  Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled 
restart job, restart counter is at 5.
  Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution.
  Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed 
with result 'exit-code'.
  Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name 
Resolution.

  This causes /etc/resolv.conf to point to a file that isn't created, so
  all name resolution fails. As far as I can determine, landing this in
  the release pocket would cause all default LXD containers to stop
  working.

  In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd
  ubuntu-daily:disco"

  Tagging block-proposed as migration would regress the release pocket,
  and marking Critical as it breaks the system (presumably only in a
  container though, and it is only in proposed currently).

  === Workaround ===

  $ lxc config set test-v240 raw.apparmor 'mount 
options=(ro,nodev,remount,bind),
  mount options=(ro,nosuid,nodev,remount,bind),
  mount options=(ro,nosuid,noexec,remount,strictatime),
  mount options=(ro,nosuid,noexec,remount,bind,strictatime),
  mount options=(ro,nosuid,nodev,noexec,remount,bind),'

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/1813622/+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 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

Verified 239-7ubuntu10.11 on Cosmic:

test@test-Standard-PC-i440FX-PIIX-1996:~$ systemd-detect-virt --container 
none
test@test-Standard-PC-i440FX-PIIX-1996:~$ echo $?
1
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd239-7ubuntu10.11 amd64system and service manager


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

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

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  SourcePackage: grub2
  Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus

[Touch-packages] [Bug 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

Verified 239-7ubuntu10.11 on Cosmic:

...
ubuntu@DESKTOP-V4DDKSS:~$ dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd239-7ubuntu10.11 amd64system and service manager
ubuntu@DESKTOP-V4DDKSS:~$ systemd-detect-virt --container
wsl
ubuntu@DESKTOP-V4DDKSS:~$ systemd-detect-virt 
wsl
...


...
root@cc-daily:~# systemd-detect-virt 
lxc
root@cc-daily:~# dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---===
ii  systemd 239-7ubuntu10.11 amd64system and 
service manager
...

-- 
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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-

[Touch-packages] [Bug 1821960] [NEW] [wma codec problem, playback] Playback problem

2019-03-27 Thread BertN45

Public bug reported:

The song Waterloo of ABBA plays correct with 
Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
I use Quod Libet as audio payer.
The song plays for one second, halts for one second and than plays again for a 
second.
I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
 /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
 /dev/snd/timer:  bertadmin   1987 f pulseaudio
CurrentDesktop: XFCE
Date: Wed Mar 27 14:36:21 2019
InstallationDate: Installed on 2018-11-08 (139 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Built-in Audio - Intel 82801AA-ICH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot_2019-03-27_14-35-24.png"
   
https://bugs.launchpad.net/bugs/1821960/+attachment/5249890/+files/Screenshot_2019-03-27_14-35-24.png

-- 
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/1821960

Title:
  [wma codec problem, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The song Waterloo of ABBA plays correct with 
  Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
  Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
  I use Quod Libet as audio payer.
  The song plays for one second, halts for one second and than plays again for 
a second.
  I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1987 f pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 27 14:36:21 2019
  InstallationDate: Installed on 2018-11-08 (139 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svni

[Touch-packages] [Bug 1821822] Re: Temporary failure in name resolution in Python 3.7.2

2019-03-27 Thread Dale Osm

** Tags added: disco

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

Title:
  Temporary failure in name resolution in Python 3.7.2

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  My Python application works in 18.10 fine, but when upgrading to 19.10
  for development reasons the same script produces the errors reported
  below. I have checked on the Python bug tracker and there are no
  related bug reports.

  Traceback (most recent call last):
    File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
  encode_chunked=req.has_header('Transfer-encoding'))
    File "/usr/lib/python3.7/http/client.py", line 1229, in request
  self._send_request(method, url, body, headers, encode_chunked)
    File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
  self.endheaders(body, encode_chunked=encode_chunked)
    File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
  self._send_output(message_body, encode_chunked=encode_chunked)
    File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
  self.send(msg)
    File "/usr/lib/python3.7/http/client.py", line 956, in send
  self.connect()
    File "/usr/lib/python3.7/http/client.py", line 1384, in connect
  super().connect()
    File "/usr/lib/python3.7/http/client.py", line 928, in connect
  (self.host,self.port), self.timeout, self.source_address)
    File "/usr/lib/python3.7/socket.py", line 707, in create_connection
  for res in getaddrinfo(host, port, 0, SOCK_STREAM):
    File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
  for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
  socket.gaierror: [Errno -3] Temporary failure in name resolution

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/pihole-panel/main.py", line 312, in 
  win = GridWindow()
    File "/usr/lib/pihole-panel/main.py", line 37, in __init__
  self.updates_frame = self.draw_updates_frame()
    File "/usr/lib/pihole-panel/main.py", line 132, in draw_updates_frame
  if self.version_check() == True:
    File "/usr/lib/pihole-panel/main.py", line 53, in version_check
  get_version = urlopen('https://urlchanged.com').read()
    File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
  return opener.open(url, data, timeout)
    File "/usr/lib/python3.7/urllib/request.py", line 525, in open
  response = self._open(req, data)
    File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
  '_open', req)
    File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
  result = func(*args)
    File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open
  context=self._context, check_hostname=self._check_hostname)
    File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open
  raise URLError(err)
  urllib.error.URLError: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1821822/+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 1755311] Re: "Warning: libpng warning: iCCP: known incorrect sRGB profile"

2019-03-27 Thread Mattia Rizzolo

So, I'm reassigning this bug to qt5webkit, thank you Gianfranco for
investigating the issue.  That was very obscure!

I'll take care of closing this bug once somebody merges in the new
qt5webkit version (which may be for disco+1)

** Package changed: sigil (Ubuntu) => qtwebkit-opensource-src (Ubuntu)

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Status: New => Incomplete

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "Warning: libpng warning: iCCP: known incorrect sRGB profile"

Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  When sigil is started, it prints the following warning twice to
  stderr:

  Warning: libpng warning: iCCP: known incorrect sRGB profile

  This may be symptomatic of a deeper issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sigil 0.9.9+dfsg-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Mar 13 09:58:34 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: sigil
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1755311/+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 1755311] Re: "Warning: libpng warning: iCCP: known incorrect sRGB profile"

I just did the qt5webkit merge for disco, lets close directly.

Of course I don't plan to SRU for bionic or cosmic or whatever, because it is 
just a cosmetic error
(I mean, the PNG bad files should have been around since the begin, just later 
libpng versions are becoming pickier about them)

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: qtwebkit-opensource-src (Ubuntu)
 Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)

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

Title:
  "Warning: libpng warning: iCCP: known incorrect sRGB profile"

Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  When sigil is started, it prints the following warning twice to
  stderr:

  Warning: libpng warning: iCCP: known incorrect sRGB profile

  This may be symptomatic of a deeper issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sigil 0.9.9+dfsg-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Mar 13 09:58:34 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: sigil
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1755311/+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 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

Verified 229-4ubuntu21.19 on Xenial:


# systemd-detect-virt --container
wsl

...
root@x-uu-upgrade:~# systemd-detect-virt 
lxc
oot@x-uu-upgrade:~# dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd229-4ubuntu21.19 amd64system and service manager
...

...
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ systemd-detect-virt --container
none
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ echo $?
1
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---===
...


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

-- 
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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details

[Touch-packages] [Bug 1755311] [NEW] "Warning: libpng warning: iCCP: known incorrect sRGB profile"

You have been subscribed to a public bug:

When sigil is started, it prints the following warning twice to stderr:

Warning: libpng warning: iCCP: known incorrect sRGB profile

This may be symptomatic of a deeper issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sigil 0.9.9+dfsg-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Mar 13 09:58:34 2018
InstallationDate: Installed on 2018-03-12 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
SourcePackage: sigil
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic
-- 
"Warning: libpng warning: iCCP: known incorrect sRGB profile"
https://bugs.launchpad.net/bugs/1755311
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtwebkit-opensource-src 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 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

Verified 237-3ubuntu10.17 on Bionic:
...
[K]0;ubuntu@DESKTOP-V4DDKSS: 
~[01;32mubuntu@DESKTOP-V4DDKSS[00m:[01;34m~[00m$ systemd-detect-virt 
--container
wsl
...

...
root@bb-ua:~# dpkg -l systemd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd237-3ubuntu10.17 amd64system and service manager
root@bb-ua:~# systemd-detect-virt --container
lxc
...

...
rbalint@yogi:~$ dpkg -l systemd |cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd237-3ubuntu10.17 amd64system and service manager
rbalint@yogi:~$ systemd-detect-virt 
none
rbalint@yogi:~$ 
...


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

-- 
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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned err

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

-- 
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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+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 1821936] Missing required logs.

2019-03-27 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1821936

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

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

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

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1821936] Re: ALC274 unsupported

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+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 1307170] Re: /usr/bin/software-properties-kde crashed when triggering mirror selection and clicking ok quickly

2019-03-27 Thread Paul White

Cleaning up by marking fixed.

** Changed in: software-properties
   Status: New => Fix Released

-- 
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/1307170

Title:
  /usr/bin/software-properties-kde crashed when triggering mirror
  selection and clicking ok quickly

Status in Software Properties:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  See https://docs.google.com/file/d/0B-
  ihXi2hkCPfMGlCbnpyU2syYXc/edit?pli=1

  Backtrace:

  #0  0x7f3d0fd36fbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3d0c2b1fe4 in g_main_context_poll (priority=2147483647, n_fds=2, 
fds=0x7f3cf40034b0, timeout=-1, context=0x7f3cf40009c0) at 
/build/buildd/glib2.0-2.40.0/./glib/gmain.c:4028
  #2  g_main_context_iterate (context=context@entry=0x7f3cf40009c0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.40.0/./glib/gmain.c:3729
  #3  0x7f3d0c2b20ec in g_main_context_iteration (context=0x7f3cf40009c0, 
may_block=1) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3795
  #4  0x7f3d0c71b7be in QEventDispatcherGlib::processEvents 
(this=0x7f3cf40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
  #5  0x7f3d0c6ed0af in QEventLoop::processEvents 
(this=this@entry=0x7f3cf94e5e60, flags=...) at kernel/qeventloop.cpp:149
  #6  0x7f3d0c6ed3a5 in QEventLoop::exec (this=this@entry=0x7f3cf94e5e60, 
flags=...) at kernel/qeventloop.cpp:204
  #7  0x7f3d0c5e9c5f in QThread::exec (this=this@entry=0x2e52190) at 
thread/qthread.cpp:537
  #8  0x7f3d0c6ce823 in QInotifyFileSystemWatcherEngine::run 
(this=0x2e52190) at io/qfilesystemwatcher_inotify.cpp:265
  #9  0x7f3d0c5ec32f in QThreadPrivate::start (arg=0x2e52190) at 
thread/qthread_unix.cpp:349
  #10 0x7f3d10017182 in start_thread (arg=0x7f3cf94e6700) at 
pthread_create.c:312
  #11 0x7f3d0fd4430d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

  Thread 1 (Thread 0x7f3d10428740 (LWP 4570)):
  [KCrash Handler]
  #6  QWidget::~QWidget (this=0x2dd66b0, __in_chrg=) at 
kernel/qwidget.cpp:1632
  #7  0x7f3d0b74abc9 in ?? () from 
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
  #8  0x7f3d0b70277e in ?? () from 
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
  #9  0x7f3d0bc0a486 in ?? () from 
/usr/lib/python3/dist-packages/sip.cpython-34m-x86_64-linux-gnu.so
  #10 0x7f3d0bc0b659 in ?? () from 
/usr/lib/python3/dist-packages/sip.cpython-34m-x86_64-linux-gnu.so
  #11 0x0046bbe2 in subtype_dealloc.16050 (self=0x7f3d0128c708) at 
../Objects/typeobject.c:1172
  #12 0x00431980 in dict_dealloc.9974 (mp=0x7f3d0ed50bc8) at 
../Objects/dictobject.c:1383
  #13 0x0046bce9 in subtype_dealloc.16050 (self=0x7f3d01293b00) at 
../Objects/typeobject.c:1157
  #14 0x00454b2b in insertdict.10035 (mp=mp@entry=0x7f3d1038a348, 
key=key@entry=0x7f3d102a9848, hash=2785936968932569566, value=0x9def60 
<_Py_NoneStruct>) at ../Objects/dictobject.c:823
  #15 0x00454dca in PyDict_SetItem (op=op@entry=0x7f3d1038a348, 
key=key@entry=0x7f3d102a9848, value=) at 
../Objects/dictobject.c:1207
  #16 0x004ac48a in _PyModule_ClearDict (d=0x7f3d1038a348) at 
../Objects/moduleobject.c:353
  #17 0x005bf6ed in _PyModule_Clear (m=0x7f3d103894a8) at 
../Objects/moduleobject.c:304
  #18 PyImport_Cleanup () at ../Python/import.c:515
  #19 0x005bf945 in Py_Finalize.part.6.32879 () at 
../Python/pythonrun.c:616
  #20 0x005bfc7c in Py_Finalize () at ../Python/pythonrun.c:2714
  #21 Py_Exit (sts=sts@entry=0) at ../Python/pythonrun.c:2712
  #22 0x0041e5d9 in handle_system_exit.part.7 () at 
../Python/pythonrun.c:1811
  #23 0x005bffc3 in handle_system_exit () at ../Python/pythonrun.c:1856
  #24 PyErr_PrintEx (set_sys_last_vars=set_sys_last_vars@entry=1) at 
../Python/pythonrun.c:1821
  #25 0x0060c170 in PyErr_Print () at ../Python/pythonrun.c:1717
  #26 PyRun_SimpleFileExFlags (fp=fp@entry=0x2588900, filename=, 
filename@entry=0x7f3d102a2cb0 "/usr/bin/software-properties-kde", 
closeit=closeit@entry=1, flags=flags@entry=0x7fff07fa85d0) at 
../Python/pythonrun.c:1610
  #27 0x0060d3ac in PyRun_AnyFileExFlags (flags=0x7fff07fa85d0, 
closeit=, filename=, fp=0x2588900) at 
../Python/pythonrun.c:1292
  #28 run_file (p_cf=0x7fff07fa85d0, filename=0x2520200 
L"/usr/bin/software-properties-kde", fp=0x2588900) at ../Modules/main.c:319
  #29 Py_Main (argc=argc@entry=5, argv=argv@entry=0x251e010) at 
../Modules/main.c:751
  #30 0x0041ec0d in main (argc=5, argv=) at 
../Modules/python.c:69

  
  Despite having -dbg or if not available -dbgsy packages of the package 
containing /usr/lib/python3/dist-packages/sip.cpython-34m-x86_64-linux-gnu.so 
(its python3-sip) and  
/usr/lib/python3/d

[Touch-packages] [Bug 1821939] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-03-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Mar 27 15:11:18 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-01-21 (65 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1821939/+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 1821939] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-03-27 Thread Jeffrey Suchomel

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Mar 27 15:11:18 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2019-01-21 (65 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
Missing privilege separation directory: /var/run/sshd
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Mar 27 15:11:18 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-01-21 (65 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1821939/+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 1821936] [NEW] ALC274 unsupported

Public bug reported:

I find this to be an issue with current LTS 18.04's latest 4.19 kernel.
I tested this on mainline 4.20 and 5.0 kernels as well.

No audio because ALC274 not properly loaded for use, so no audio output.
A related card had a similar bug, which was fixed, and may be of use in
resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485


# cat /proc/asound/card0/codec* | grep Codec
Codec: Realtek ALC274
Codec: Intel Kabylake HDMI

# cat /proc/asound/card0/pcm0c/info
card: 0
device: 0
subdevice: 0
stream: CAPTURE
id: ALC274 Analog
name: ALC274 Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

d# hwinfo --sound
21: PCI 1f.3: 0403 Audio device 
  [Created at pci.378]
  Unique ID: nS1_.WnojYJLVCm0
  SysFS ID: /devices/pci:00/:00:1f.3
  SysFS BusID: :00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa348 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x31d0 
  Revision: 0x10
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
  Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
  IRQ: 145 (663 events)
  Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
  Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

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


** Tags: alc274 audio driver kernel

-- 
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/1821936

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications

[Touch-packages] [Bug 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

2019-03-27 Thread Seb Bonnard

I have also this pb. It seems gpg cannot handle more than
/etc/apt/trusted.gpg (one keyring) + 39 keyrings in
/etc/apt/trusted.gpg.d/ : https://lists.gnupg.org/pipermail/gnupg-
users/2013-December/048571.html

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key 
" not changed
  gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key 
" not changed
  gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) 
" not changed
  gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) 
" not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the "resource limit" message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1263540/+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 1821920] Re: apparmor-profiles installs the chromium-browser profile but not the abstraction

Jamie said that he'd pull in the postinst snippet and include that
change in an upload that he's already preparing.

** Changed in: apparmor (Ubuntu)
   Status: New => In Progress

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

-- 
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/1821920

Title:
  apparmor-profiles installs the chromium-browser profile but not the
  abstraction

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
  disco-proposed is not handling the chromium-browser profile and
  abstraction correctly. It installs the profile but not the abstraction
  which makes profile loading fail.

  $ sudo apt install apparmor-profiles/disco-proposed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
  The following NEW packages will be installed:
apparmor-profiles
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 32.5 kB of archives.
  After this operation, 353 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
   2.13.2-9ubuntu2 [32.5 kB]
  Fetched 32.5 kB in 0s (95.3 kB/s)  
  Selecting previously unselected package apparmor-profiles.
  (Reading database ... 119746 files and directories currently installed.)
  Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
  Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
  Setting up apparmor-profiles (2.13.2-9ubuntu2) ...
  AppArmor parser error for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/
  usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'

  This makes the apparmor service fail to start:

  $ sudo service apparmor restart
  Job for apparmor.service failed because the control process exited with error 
code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.

  
  $ systemctl status apparmor.service | cat
  ● apparmor.service - Load AppArmor profiles
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2019-03-27 13:05:37 UTC; 41s 
ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 5103 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
   Main PID: 5103 (code=exited, status=1/FAILURE)

  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Restarting AppArmor
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Reloading AppArmor 
profiles
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d in /etc/apparmor.d/usr.bin.chromium-browser at line 20: 
Could not open 'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Error: At least one 
profile failed to load
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: Failed to start Load AppArmor 
profiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1821920/+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 1821929] Re: Bluetooth mouse is not able to connect

2019-03-27 Thread Pavel Moukhataev

** Attachment added: "HCI trace captured by btmon"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1821929/+attachment/5249821/+files/hcitrace.snoop

-- 
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/1821929

Title:
  Bluetooth mouse is not able to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I recently bought not expensive wireless mouse with bluetooth support:
  
https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS

  I works in MacOS X and Windows but doesn't work in Linux. I suppose I
  can debug that mouse under Windows to collect more information if I
  have proper instructions.

  I collected some information about that mouse:
  # uname -a
  Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  
  # lsb_release -a
  Distributor ID:Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:bionic

  
  # lsusb 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb)
  Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam)
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


  
  # usb-devices
  T:  Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#=  6 Spd=12  MxCh= 0
  D:  Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0bda ProdID=8763 Rev=02.00
  S:  Manufacturer=Realtek
  S:  Product=Bluetooth Radio
  S:  SerialNumber=00e04c01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb



  
  # bluetoothctl --version
  bluetoothctl: 5.48

  
  # hciconfig -a
  hci0:Type: Primary  Bus: USB
  BD Address: 94:E9:79:1A:89:1D  ACL MTU: 820:8  SCO MTU: 255:16
  UP RUNNING PSCAN 
  RX bytes:1604 acl:0 sco:0 events:170 errors:0
  TX bytes:28036 acl:0 sco:0 commands:166 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF PARK 
  Link mode: SLAVE ACCEPT 
  Name: 'asus-N752VX'
  Class: 0x1c010c
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Laptop
  HCI Version: 4.0 (0x6)  Revision: 0xe3e
  LMP Version: 4.0 (0x6)  Subversion: 0x4380
  Manufacturer: Realtek Semiconductor Corporation (93)

  
  # bluetoothctl
  [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default]
  [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0

  
  # show
  Controller 94:E9:79:1A:89:1D (public)
  Name: asus-N752VX
  Alias: asus-N752VX
  Class: 0x001c010c
  Powered: yes
  Discoverable: no
  Pairable: yes
  UUID: Headset AG(1112--1000-8000-00805f9b34fb)
  UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
  UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
  UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
  UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (5005--1000-8000-0002ee01)
  UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
  UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
  UUID: Headset   (1108--1000-8000-00805f9b34fb)
  Modalias: usb:v1D6Bp0246d0530
  Discovering: no

  
  # devices
  Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0

  
  # info 5A:4B:3C:0E:07:B2
  Device 5A:4B:3C:0E:07:B2 (public)
  Name: Bluetooth Mouse 4.0
  Alias: Bluetooth Mouse 4.0
  Class: 0x2580
  Icon: input-mouse
  Paired: yes
  Trusted: yes
  Blocked: no
  Connected: no
  LegacyPairing: no
  UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  Modalias:

[Touch-packages] [Bug 1821929] [NEW] Bluetooth mouse is not able to connect

2019-03-27 Thread Pavel Moukhataev

Public bug reported:

I recently bought not expensive wireless mouse with bluetooth support:
https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS

I works in MacOS X and Windows but doesn't work in Linux. I suppose I
can debug that mouse under Windows to collect more information if I have
proper instructions.

I collected some information about that mouse:
# uname -a
Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux


# lsb_release -a
Distributor ID:Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:bionic


# lsusb 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb)
Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


# usb-devices
T:  Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=8763 Rev=02.00
S:  Manufacturer=Realtek
S:  Product=Bluetooth Radio
S:  SerialNumber=00e04c01
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb



# bluetoothctl --version
bluetoothctl: 5.48


# hciconfig -a
hci0:Type: Primary  Bus: USB
BD Address: 94:E9:79:1A:89:1D  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:1604 acl:0 sco:0 events:170 errors:0
TX bytes:28036 acl:0 sco:0 commands:166 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF PARK 
Link mode: SLAVE ACCEPT 
Name: 'asus-N752VX'
Class: 0x1c010c
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0xe3e
LMP Version: 4.0 (0x6)  Subversion: 0x4380
Manufacturer: Realtek Semiconductor Corporation (93)


# bluetoothctl
[NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default]
[NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0


# show
Controller 94:E9:79:1A:89:1D (public)
Name: asus-N752VX
Alias: asus-N752VX
Class: 0x001c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Vendor specific   (5005--1000-8000-0002ee01)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: no


# devices
Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0


# info 5A:4B:3C:0E:07:B2
Device 5A:4B:3C:0E:07:B2 (public)
Name: Bluetooth Mouse 4.0
Alias: Bluetooth Mouse 4.0
Class: 0x2580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129


# paired-devices
Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0


# trust 5A:4B:3C:0E:07:B2
Changing 5A:4B:3C:0E:07:B2 trust succeeded


# connect 5A:4B:3C:0E:07:B2
Attempting to connect to 5A:4B:3C:0E:07:B2
Failed to connect: org.bluez.Error.Failed


# rfkill list
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


/var/log/syslog:
16:34:35 asus-N752VX bluetoothd[1313]: src/device.c:connect_profiles() 
/org/bluez/hci0/dev_5A_4B_3C_0E_07_B2 (all), client :1.197
16:34:35 asus-N752VX bluetoothd[1313]: 
profiles/input/device.c:input

[Touch-packages] [Bug 1821920] Re: apparmor-profiles installs the chromium-browser profile but not the abstraction

It looks like the change mentioned in the above comment came from
Debian. Here's the commit:

  https://salsa.debian.org/apparmor-
team/apparmor/commit/dc14f24b2c2943c29d0368f913020f1307d8f1d3

They obviously don't have  so they
opted to remove that logic from the postinst. I think we should have
kept it during our merge.

-- 
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/1821920

Title:
  apparmor-profiles installs the chromium-browser profile but not the
  abstraction

Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
  disco-proposed is not handling the chromium-browser profile and
  abstraction correctly. It installs the profile but not the abstraction
  which makes profile loading fail.

  $ sudo apt install apparmor-profiles/disco-proposed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
  The following NEW packages will be installed:
apparmor-profiles
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 32.5 kB of archives.
  After this operation, 353 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
   2.13.2-9ubuntu2 [32.5 kB]
  Fetched 32.5 kB in 0s (95.3 kB/s)  
  Selecting previously unselected package apparmor-profiles.
  (Reading database ... 119746 files and directories currently installed.)
  Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
  Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
  Setting up apparmor-profiles (2.13.2-9ubuntu2) ...
  AppArmor parser error for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/
  usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'

  This makes the apparmor service fail to start:

  $ sudo service apparmor restart
  Job for apparmor.service failed because the control process exited with error 
code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.

  
  $ systemctl status apparmor.service | cat
  ● apparmor.service - Load AppArmor profiles
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2019-03-27 13:05:37 UTC; 41s 
ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 5103 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
   Main PID: 5103 (code=exited, status=1/FAILURE)

  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Restarting AppArmor
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Reloading AppArmor 
profiles
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d in /etc/apparmor.d/usr.bin.chromium-browser at line 20: 
Could not open 'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Error: At least one 
profile failed to load
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: Failed to start Load AppArmor 
profiles.

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

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

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

2019-03-27 Thread Mario Limonciello

If it's intermittent at least what evidence points to fwupd? Is it the
last thing seen in a log somewhere?

Ideally please leave verbose logging turned on in fwipd systemd unit and
leave it enabled. When this repros again we can see the logs.

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

2019-03-27 Thread Dean Henrichsmeyer

This seems intermittent for me. I admit I don't reboot often but I've
been unable to reproduce it, even with leaving fwupd enabled.

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-27 Thread Seth Forshee

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

-- 
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/1818204

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.da

[Touch-packages] [Bug 1821920] Re: apparmor-profiles installs the chromium-browser profile but not the abstraction

This failure was noticed by the kernel team as it makes the kernel
autopkgtests to fail while running QRT's test-apparmor.py.

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => High

-- 
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/1821920

Title:
  apparmor-profiles installs the chromium-browser profile but not the
  abstraction

Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
  disco-proposed is not handling the chromium-browser profile and
  abstraction correctly. It installs the profile but not the abstraction
  which makes profile loading fail.

  $ sudo apt install apparmor-profiles/disco-proposed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
  The following NEW packages will be installed:
apparmor-profiles
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 32.5 kB of archives.
  After this operation, 353 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
   2.13.2-9ubuntu2 [32.5 kB]
  Fetched 32.5 kB in 0s (95.3 kB/s)  
  Selecting previously unselected package apparmor-profiles.
  (Reading database ... 119746 files and directories currently installed.)
  Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
  Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
  Setting up apparmor-profiles (2.13.2-9ubuntu2) ...
  AppArmor parser error for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/
  usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'

  This makes the apparmor service fail to start:

  $ sudo service apparmor restart
  Job for apparmor.service failed because the control process exited with error 
code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.

  
  $ systemctl status apparmor.service | cat
  ● apparmor.service - Load AppArmor profiles
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2019-03-27 13:05:37 UTC; 41s 
ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 5103 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
   Main PID: 5103 (code=exited, status=1/FAILURE)

  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Restarting AppArmor
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Reloading AppArmor 
profiles
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d in /etc/apparmor.d/usr.bin.chromium-browser at line 20: 
Could not open 'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Error: At least one 
profile failed to load
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: Failed to start Load AppArmor 
profiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1821920/+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 1821920] Re: apparmor-profiles installs the chromium-browser profile but not the abstraction

I see this change in the debdiff from the last apparmor upload to what's
currently in proposed:

diff -Nru apparmor-2.12/debian/apparmor-profiles.postinst 
apparmor-2.13.2/debian/apparmor-profiles.postinst
--- apparmor-2.12/debian/apparmor-profiles.postinst 2018-03-22 
20:19:58.0 +
+++ apparmor-2.13.2/debian/apparmor-profiles.postinst   2019-02-25 
06:10:18.0 +
@@ -20,14 +20,6 @@
 # dh_installdeb will replace this with shell code automatically
 # generated by other debhelper scripts.
 
-case "$1" in
-configure)
-if [ ! -e 
/etc/apparmor.d/abstractions/ubuntu-browsers.d/chromium-browser ]; then
-cp 
/usr/share/apparmor/extra-profiles/abstractions/ubuntu-browsers.d/chromium-browser
 /etc/apparmor.d/abstractions/ubuntu-browsers.d || true
-fi
-;;
-esac
-
 #DEBHELPER#
 
 exit 0

---

/usr/share/apparmor/extra-profiles/abstractions/ubuntu-browsers.d
/chromium-browser does exist but /etc/apparmor.d/abstractions/ubuntu-
browsers.d/chromium-browser does not. The removal of this 'cp'
invocation from the apparmor-profile.postinst is likely the cause.

-- 
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/1821920

Title:
  apparmor-profiles installs the chromium-browser profile but not the
  abstraction

Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
  disco-proposed is not handling the chromium-browser profile and
  abstraction correctly. It installs the profile but not the abstraction
  which makes profile loading fail.

  $ sudo apt install apparmor-profiles/disco-proposed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
  The following NEW packages will be installed:
apparmor-profiles
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 32.5 kB of archives.
  After this operation, 353 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
   2.13.2-9ubuntu2 [32.5 kB]
  Fetched 32.5 kB in 0s (95.3 kB/s)  
  Selecting previously unselected package apparmor-profiles.
  (Reading database ... 119746 files and directories currently installed.)
  Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
  Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
  Setting up apparmor-profiles (2.13.2-9ubuntu2) ...
  AppArmor parser error for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/
  usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'

  This makes the apparmor service fail to start:

  $ sudo service apparmor restart
  Job for apparmor.service failed because the control process exited with error 
code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.

  
  $ systemctl status apparmor.service | cat
  ● apparmor.service - Load AppArmor profiles
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2019-03-27 13:05:37 UTC; 41s 
ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 5103 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
   Main PID: 5103 (code=exited, status=1/FAILURE)

  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Restarting AppArmor
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Reloading AppArmor 
profiles
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d in /etc/apparmor.d/usr.bin.chromium-browser at line 20: 
Could not open 'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Error: At least one 
profile failed to load
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Mar 27 13:05:37 sec-disco-amd64 systemd[1]: Failed to start Load AppArmor 
profiles.

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

[Touch-packages] [Bug 1821920] [NEW] apparmor-profiles installs the chromium-browser profile but not the abstraction

Public bug reported:

The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
disco-proposed is not handling the chromium-browser profile and
abstraction correctly. It installs the profile but not the abstraction
which makes profile loading fail.

$ sudo apt install apparmor-profiles/disco-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
The following NEW packages will be installed:
  apparmor-profiles
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.5 kB of archives.
After this operation, 353 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
 2.13.2-9ubuntu2 [32.5 kB]
Fetched 32.5 kB in 0s (95.3 kB/s)  
Selecting previously unselected package apparmor-profiles.
(Reading database ... 119746 files and directories currently installed.)
Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
Setting up apparmor-profiles (2.13.2-9ubuntu2) ...
AppArmor parser error for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/
usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'

This makes the apparmor service fail to start:

$ sudo service apparmor restart
Job for apparmor.service failed because the control process exited with error 
code.
See "systemctl status apparmor.service" and "journalctl -xe" for details.


$ systemctl status apparmor.service | cat
● apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-03-27 13:05:37 UTC; 41s ago
 Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  Process: 5103 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
 Main PID: 5103 (code=exited, status=1/FAILURE)

Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Restarting AppArmor
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Reloading AppArmor 
profiles
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d in /etc/apparmor.d/usr.bin.chromium-browser at line 20: 
Could not open 'abstractions/ubuntu-browsers.d/chromium-browser'
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: AppArmor parser error 
for /etc/apparmor.d/usr.bin.chromium-browser in 
/etc/apparmor.d/usr.bin.chromium-browser at line 20: Could not open 
'abstractions/ubuntu-browsers.d/chromium-browser'
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 27 13:05:37 sec-disco-amd64 apparmor.systemd[5103]: Error: At least one 
profile failed to load
Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
Mar 27 13:05:37 sec-disco-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
Mar 27 13:05:37 sec-disco-amd64 systemd[1]: Failed to start Load AppArmor 
profiles.

** Affects: apparmor (Ubuntu)
 Importance: High
 Status: New

-- 
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/1821920

Title:
  apparmor-profiles installs the chromium-browser profile but not the
  abstraction

Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor-profiles binary package from apparmor 2.13.2-9ubuntu2 in
  disco-proposed is not handling the chromium-browser profile and
  abstraction correctly. It installs the profile but not the abstraction
  which makes profile loading fail.

  $ sudo apt install apparmor-profiles/disco-proposed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2.13.2-9ubuntu2' (Ubuntu:19.04/disco-proposed [all]) for 
'apparmor-profiles'
  The following NEW packages will be installed:
apparmor-profiles
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 32.5 kB of archives.
  After this operation, 353 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 
apparmor-profiles all
   2.13.2-9ubuntu2 [32.5 kB]
  Fetched 32.5 kB in 0s (95.3 kB/s)  
  Selecting previously unselected package apparmor-profiles.
  (Reading database ... 119746 files and directories currently installed.)
  Preparing to unpack .../apparmor-profiles_2.13.2-9ubuntu2_all.deb ...
  Unpacking apparmor-profiles (2.13.2-9ubuntu2) ...
  Setting up apparmor-profiles (2.13.2-9ubunt

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943

addional clarification .. if sda6 (recovery booted or chrooted)
installed grub then sda6 boots with some brief flashing normally. if
sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1)
installed grub then sda6 would boot and lighjtdm would briefly flash
onto screen and the disappear (blank screen) showing just aflashing
underline cursor.

so xorg video drivers appear  NOT to be involved. except maybe as kernel
i915 modules missing I have not checked

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1821609/+subscriptions

-- 
Mailing list: http

[Touch-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

@Brian

Now the disco fix is in both cosmic and bionic queues.
please accept them :)
I checked if wl-asneeded was removed from rules, if the patch was added, and 
also the upgrade path for versioning was correct for bionic->cosmic->disco

please double check! I also fixed the description

** Changed in: libunistring (Ubuntu Cosmic)
 Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)

** Changed in: libunistring (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

** Changed in: libidn (Ubuntu Cosmic)
 Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943

this effected only the more recent installs

you have miss understood the details in the initial report .. the system
would boot normally as long as the grub used (installed) was from the
install partition (sda6 or sda7) .. if another partition was used to
install grub the lightdm would appear briefly and then crash or vanish
to a underline flashing cursor

the video system did work it would flash once on start-up but come back
in about 5 seconds or less is the correct (ie this partition installed
the grub version used)

the main sda1 partition always worked .. only difference was the kernel image 
used .. 
I have not yet checked to see if the sda1 5.0.0.7 image fails currently but it 
worked fine before.

the installation of the newer video drivers did not fix this issue!!! It
remained as long as a 5.0.0.7 kernel was selected to boot sda6 or sda7

sda1 was not effected.

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  vers

[Touch-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

libunistring backport patch to cosmic from Disco:
diff -Nru libunistring-0.9.10/debian/changelog 
libunistring-0.9.10/debian/changelog
--- libunistring-0.9.10/debian/changelog2018-07-23 16:46:28.0 
+0200
+++ libunistring-0.9.10/debian/changelog2019-03-27 12:21:30.0 
+0100
@@ -1,3 +1,10 @@
+libunistring (0.9.10-1ubuntu1.18.10.1) cosmic; urgency=medium
+
+  * Cherry-pick pthread fix from upstream and disco release.
+(LP: #1813587)
+
+ -- Gianfranco Costamagna   Wed, 27 Mar 2019 
12:21:30 +0100
+
 libunistring (0.9.10-1ubuntu1) cosmic; urgency=medium

   * Do not set as-needed, to work-around a testsuite failure
diff -Nru 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
--- 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
   1970-01-01 01:00:00.0 +0100
+++ 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
   2019-03-27 12:21:14.0 +0100
@@ -0,0 +1,15 @@
+Description: Fix link failure with upstream gnulib patch
+Origin: 
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36
+Last-Update: 2019-03-20
+
+--- libunistring-0.9.10.orig/tests/glthread/thread.h
 libunistring-0.9.10/tests/glthread/thread.h
+@@ -133,8 +133,6 @@ extern int glthread_in_use (void);
+call to foo(...) in the same function.  To avoid this, we test the
+address of a function in libpthread that we don't use.  */
+ 
+-#  pragma weak pthread_create
+-
+ #  ifndef pthread_sigmask /* Do not declare rpl_pthread_sigmask weak.  */
+ #   pragma weak pthread_sigmask
+ #  endif
diff -Nru libunistring-0.9.10/debian/patches/series 
libunistring-0.9.10/debian/patches/series
--- libunistring-0.9.10/debian/patches/series   2018-07-23 16:46:28.0 
+0200
+++ libunistring-0.9.10/debian/patches/series   2019-03-27 12:21:14.0 
+0100
@@ -1,2 +1,3 @@
 0100-float-endian-detection.patch
 0700-multiarch-libc.patch
+cca32830b57e91f837c01d15b8732f23ff97fc36.patch

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

Ok Brian, so lets backport the fix from 19.04 and fix also 18.10

** Also affects: libidn (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: libunistring (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: libunistring (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: libidn (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: libidn (Ubuntu Bionic)
   Status: Incomplete => In Progress

** Description changed:

  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.
  
  Test Case
  -
  Does libunistring build successfully?
  
  Regression Potential
  
- We are simply backporting the workaround we applied in Ubuntu 18.10.
+ We are simply backporting the workaround we applied in Ubuntu 19.04.
  
  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
  libunistring ftbfs.
  
  FAIL: test-thread_create
  
  
  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943

** Summary changed:

- lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870

-- 
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/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1821609/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-27 Thread El jinete sin cabeza

@Till

I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636

-- 
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/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1821882] [NEW] Screen is very dark and brightness cannot be adjusted

2019-03-27 Thread Pierre Equoy

Public bug reported:

Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the 
nVidia GPU is used.

When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)

There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
intel_backlight):

$ ll /sys/class/backlight/
total 0
drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

Trying to manually change brightness doesn't do anything:

$ sudo su
root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
root@ubuntu:/sys/class/backlight/nv_backlight# ll
total 0
drwxr-xr-x 3 root root0 Mar 27 09:28 ./
drwxr-xr-x 4 root root0 Mar 27 09:28 ../
-r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
-rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
-rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
-r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
drwxr-xr-x 2 root root0 Mar 27 09:28 power/
lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
-r--r--r-- 1 root root 4096 Mar 27 09:28 type
-rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
50

Although the value is changed, the screen brightness doesn't change.

in dmesg, I can see the following:

[0.241878] ACPI: Added _OSI(Module Device)
[0.241878] ACPI: Added _OSI(Processor Device)
[0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.241878] ACPI: Added _OSI(Processor Aggregator Device)
[0.241878] ACPI: Added _OSI(Linux-Dell-Video)
[0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288625] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289376] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.289379] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.289381] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289382] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

** Attachment added: "journalctl -b"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+attachment/5249682/+files/journalctl-b.txt

-- 
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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+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 1821867] Re: network interface is down after post-install reboot of a default disco installation

systemd-networkd.service is not active after reboot:

systemctl status systemd-networkd.service  
 systemd-networkd.service - Network Service ¬m  
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime
 ¬m  
   Active: inactive (dead) ¬m  
 Docs: man:systemd-networkd.service(8) ¬m  
 ¬7mlines 1-4/4 (END) ¬27m ¬K

attaching journalctl as well ...


** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821867/+attachment/5249681/+files/journalctl.txt

** Package changed: debian-installer (Ubuntu) => systemd (Ubuntu)

-- 
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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+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 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)

2019-03-27 Thread Andrew Zonenberg

@Ricardo: Yes, that was my intent with the original report. I didn't
even know about the other issue when I submitted this issue.

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

Title:
  BASH_CMDS is writable in restricted bash shells (fixed upstream, need
  to backport patch)

Status in bash package in Ubuntu:
  New

Bug description:
  In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows
  a trivial escape from rbash to run arbitrary shell commands.

  This issue is fixed upstream:
  http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1821867] [NEW] network interface is down after post-install reboot of a default disco installation

You have been subscribed to a public bug:

After doing a default disco installation on s390x using the beta ISO image aka 
daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
Hence no remote connections are possible.

The ip cmd shows:
ip a  
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group defaul
t qlen 1000  
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
inet 127.0.0.1/8 scope host lo  
   valid_lft forever preferred_lft forever  
inet6 ::1/128 scope host   
   valid_lft forever preferred_lft forever  
2: enc600:  mtu 1500 qdisc noop state DOWN group default ql
en 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

The netplan yaml file looks fine:
cat /etc/netplan/*.yaml  
# This file describes the network interfaces available on your system
# For more information, see netplan(5).  
network:  
  version: 2  
  renderer: networkd  
  ethernets:  
enc600:  
  addresses: ¬ 10.245.236.27/24 |  
  gateway4: 10.245.236.1  
  nameservers:  
  search: ¬ canonical.com |  
  addresses:  
  - "10.245.236.1"  

Using ip to bring the interface up doesn't help:
buntu§hwe0007:ß$ sudo ip link set enc600 up
sudo ip link set enc600 up
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600  
2: enc600:  mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
inet6 fe80::28:bff:fe00:15/64 scope link   
   valid_lft forever preferred_lft forever  
ubuntu§hwe0007:ß$

But finally executing netplan apply does help:
sudo netplan apply --dryrun
sudo netplan apply --dryrun  
ubuntu§hwe0007:ß$ sudo netplan apply
sudo netplan apply  
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600  
2: enc600:  mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
   valid_lft forever preferred_lft forever  
inet6 fe80::28:bff:fe00:15/64 scope link   
   valid_lft forever preferred_lft forever  
ubuntu§hwe0007:ß$ 

(Sorry for the partly duplicate lines and some strange characters, but
this is due to the fact that I copied the output from the console that
requires a 3270 terminal emulation)

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


** Tags: disco iso-testing s390x
-- 
network interface is down after post-install reboot of a default disco 
installation
https://bugs.launchpad.net/bugs/1821867
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1759014] Re: Netplan has no way to control DHCP client

2019-03-27 Thread Michael Steffens

Hi Mathieu, I don't think Cosmic or Disco systemd are affected. They are
both >= v239, and Cosmic behaved fine when verifying
https://bugs.launchpad.net/netplan/+bug/1776228.

It would just be a shame having the LTS release remain broken with DHCP
configurations, that used to work before.

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2019-03-27 Thread Kai-Heng Feng

Please backport this two MR:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1773897

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1773897/+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 1821867] [NEW] network interface is down after post-install reboot of a default disco installation

Public bug reported:

After doing a default disco installation on s390x using the beta ISO image aka 
daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
Hence no remote connections are possible.

The ip cmd shows:
ip a  
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group defaul
t qlen 1000  
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
inet 127.0.0.1/8 scope host lo  
   valid_lft forever preferred_lft forever  
inet6 ::1/128 scope host   
   valid_lft forever preferred_lft forever  
2: enc600:  mtu 1500 qdisc noop state DOWN group default ql
en 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

The netplan yaml file looks fine:
cat /etc/netplan/*.yaml  
# This file describes the network interfaces available on your system
# For more information, see netplan(5).  
network:  
  version: 2  
  renderer: networkd  
  ethernets:  
enc600:  
  addresses: ¬ 10.245.236.27/24 |  
  gateway4: 10.245.236.1  
  nameservers:  
  search: ¬ canonical.com |  
  addresses:  
  - "10.245.236.1"  

Using ip to bring the interface up doesn't help:
buntu§hwe0007:ß$ sudo ip link set enc600 up
sudo ip link set enc600 up
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600  
2: enc600:  mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
inet6 fe80::28:bff:fe00:15/64 scope link   
   valid_lft forever preferred_lft forever  
ubuntu§hwe0007:ß$

But finally executing netplan apply does help:
sudo netplan apply --dryrun
sudo netplan apply --dryrun  
ubuntu§hwe0007:ß$ sudo netplan apply
sudo netplan apply  
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600  
2: enc600:  mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000  
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
   valid_lft forever preferred_lft forever  
inet6 fe80::28:bff:fe00:15/64 scope link   
   valid_lft forever preferred_lft forever  
ubuntu§hwe0007:ß$ 

(Sorry for the partly duplicate lines and some strange characters, but
this is due to the fact that I copied the output from the console that
requires a 3270 terminal emulation)

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


** Tags: disco s390x

** Attachment added: "logs from /var/log/installer/*"
   
https://bugs.launchpad.net/bugs/1821867/+attachment/5249675/+files/inst_log.tgz

** Package changed: systemd (Ubuntu) => debian-installer (Ubuntu)

-- 
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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in debian-installer package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1

[Touch-packages] [Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)

2019-03-27 Thread Riccardo Schirone

After looking a bit more into this, it seems the issue in
https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html is
maybe not a real security concern, since rbash was wrongly configured.
Having . in PATH is not good with rbash and that makes the whole thing
flawed. So, we could say CVE-2019-9924 is just for the issue in
https://lists.gnu.org/archive/html/bug-bash/2017-03/msg00077.html .

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

Title:
  BASH_CMDS is writable in restricted bash shells (fixed upstream, need
  to backport patch)

Status in bash package in Ubuntu:
  New

Bug description:
  In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows
  a trivial escape from rbash to run arbitrary shell commands.

  This issue is fixed upstream:
  http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1759014] Re: Netplan has no way to control DHCP client

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

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

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1759014] Re: Netplan has no way to control DHCP client

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

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

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1759014] Re: Netplan has no way to control DHCP client