date:20190521

@jimnong,

Please do a test:

don't plug anything in the jack and run: sudo hdajacksensetest -a

Then plug the apple type headset in the jack and run: sudo
hdajacksensetest -a

please upload the output. thx.

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => 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/1821269

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+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 1820770] Re: when printing from the internet at Wikipedia the 8 page document only printed pages 2, 3, 4 and did not print 1, 5, 6, 7 and 8.

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

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

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

Title:
  when printing from the internet at Wikipedia the 8 page document only
  printed pages 2,3,4 and did not print 1,5,6,7 and 8.

Status in cups package in Ubuntu:
  Expired

Bug description:
  Other random internet pages do not print at all.  The printer is a
  Brother HL-L2305W.  I have been to brother and installed the driver
  package from them with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 16:18:36 2019
  InstallationDate: Installed on 2018-12-25 (83 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat:
   device for HL-L2305-2: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
   device for HLL2305: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HLL2305.ppd', 
'/etc/cups/ppd/HL-L2305-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HLL2305.ppd: Permission denied
   grep: /etc/cups/ppd/HL-L2305-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=15257050-0864-47a7-8179-fe818fbcbe2f ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1693
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 14.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1693:rvrKBCVersion14.16:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1820770/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+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 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

2019-05-21 Thread Ron Stephen Mathew

Now  I've modified this bug report and hopefully waiting for an answer.

** Description changed:

- All .desktop configuration files are opening in text editor. Because of
- that we can't creat custom shortcuts and having troubles while
- application making. Please fix this bug on next update. I have an Ubuntu
- 19.04.
+ Error : Desktop configuration files are not launching from nautilus but its 
working from desktop.
+ Occured Error while : made a shortcut and tried to open from nautilus
+ {
+ [Desktop Entry]
+ Name=Install Niram
+ Exec=/usr/share/niram/NiramStock/install.sh
+ Type=Application
+ StartupNotify=true
+ Comment=Install Stock Niram Theme
+ Path=/usr/share
+ Icon=/home/newtron/Documents/NiramStock/20190107_201717.png
+ }
+ but it's opening in text editor. Also ubuntu's default examples have this 
error and showing it as a normal text file.
+ 
+ What I've expected : On older versions of nautilus and all versions of
+ nemo it directly opens .desktop files from file manager.
+ 
+ Now  I've modified this bug report and hopefully waiting for an answer.
  
  Tanks

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

Title:
  [ubuntu 19.04]All .desktop configuration files are not opening in
  nautilus

Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  Error : Desktop configuration files are not launching from nautilus but its 
working from desktop.
  Occured Error while : made a shortcut and tried to open from nautilus
  {
  [Desktop Entry]
  Name=Install Niram
  Exec=/usr/share/niram/NiramStock/install.sh
  Type=Application
  StartupNotify=true
  Comment=Install Stock Niram Theme
  Path=/usr/share
  Icon=/home/newtron/Documents/NiramStock/20190107_201717.png
  }
  but it's opening in text editor. Also ubuntu's default examples have this 
error and showing it as a normal text file.

  What I've expected : On older versions of nautilus and all versions of
  nemo it directly opens .desktop files from file manager.

  Now  I've modified this bug report and hopefully waiting for an
  answer.

  Tanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

Too complicated. I have no idea for your problem.

Probably you could file a bug against the upstream linux kernel, let the
audio maintainer and community to help.

Just like this one:
https://bugzilla.kernel.org/show_bug.cgi?id=201251

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

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

Rebooted into windows 10, verified that I had sound then rebooted back to Ubuntu
NO SOUND

Rebooted ubuntu again and got sound from the speakers but no sound from
the headphones.

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

2019-05-21 Thread Ron Stephen Mathew

** Summary changed:

- [ubuntu 19.04]All .desktop configuration files are opening in text editor
+ [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

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

Title:
  [ubuntu 19.04]All .desktop configuration files are not opening in
  nautilus

Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  All .desktop configuration files are opening in text editor. Because
  of that we can't creat custom shortcuts and having troubles while
  application making. Please fix this bug on next update. I have an
  Ubuntu 19.04.

  Tanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

I didn't care for the way that I did troubleshooting nor the way I
reported what I did, so I did the following:

No Sound in speaker and headphones
commented out "options snd-hda-intel power_save=0" from alsa-base.conf

Here is the contents of alsa-base.conf:

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet 
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet 
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
#options snd-hda-intel power_save=0

rebooted and sound came on for a few seconds.
uncommented options snd-hda-intel power_save=0

rebooted no sound
commented out snd-hda-intel power_save=0
added options snd-hda-intel model=auto

rebooted no sound
commented out options snd-hda-intel model=auto
added options snd-hda-intel model=alc295

rebooted a garbled sound lasting a second or so
commented out options snd-hda-intel model=alc295
so now there are no snd-hda-intel options in alsa-base.conf

rebooted no sound
copied snd-hda-intel.conf back into /etc/modprobe.d snd-hda-intel.conf contains 
"options snd-hda-intel model=auto

rebooted and have continuous sound in both speakers and headphones

rebooted and still have continuous sound in both speakers and headphones

go figure

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH

[Touch-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns

2019-05-21 Thread Mal

Yup, it shows up at the top of the global resolver list:

$ systemd-resolve --status  

   
Global  

   
 DNS Servers: 127.0.0.54
 DNSSEC NTA: [...]

Unfortunately, I'm not au fait with debdiffs, and don't have the
bandwidth to get into world of compiling custom packages at the moment.
:(

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

Title:
  network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured
  dns

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Bionic:
  New

Bug description:
  On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1
  1.10.14-0ubuntu2` lead to scoped DNS servers defined in
  `/etc/systemd/resolved.conf.d/*.conf` being ignored.

  Downgrading with `sudo apt-get install network-
  manager=1.10.6-2ubuntu1.1` has resolved the issue for now.

  Example systemd-resolved conf:

  [Resolve]
  Cache=no
  DNS=127.0.0.54
  Domains=~.local.org.com

  Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving
  queries in that subdomain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1829915] Re: Radeon issue

Thanks for the bug report.

It appears your low resolution is due to the radeon kernel driver not
being able to detect the monitor's EDID correctly:

[5.219380] radeon :01:00.0: DP-1: EDID is invalid:
[5.219384]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219385]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219386]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219387]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219387]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219388]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219389]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.219390]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

In case this was caused by a hardware change, please try a different
DisplayPort cable or even a different monitor. Maybe even try just
unplugging it at both ends and plugging it in again.

If those don't fix the problem then the next step is to try some older
kernel versions so as to try and find the last version in which the bug
was not present. You can get all the kernel versions from here:

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

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

** Summary changed:

- Radeon issue
+ Radeon receives invalid EDID (all zeroes)

** Tags added: radeon

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1829915

Title:
  Radeon receives invalid EDID (all zeroes)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
   I installed ubuntu 18.04 than upgraded to 19.04 and everything was 
fine(resolution 1920x1080 on a samsung TV) for a few weeks than suddenly it 
dropped to 1024x768.
I'm running a AMD HD7670 video card with a display port to HDMI cable to 
the tv

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 21 21:25:49 2019
  DistUpgraded: 2019-05-20 01:35:47,157 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 
235/310 OEM] [1002:6778] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 7470 [1028:2120]
  InstallationDate: Installed on 2019-05-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 755
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-05-19 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1905161830.922d92~oibaf~d
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1905190730.4689e9~oibaf~d
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1905190730.4689e9~oibaf~d
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/linux/+bug/1829915/+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 1829912] Re: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.

Firstly, please disable "overamplification" because it is expected to
make the sound quality bad. If the sound quality continues to be bad
after that then this sounds most likely like a kernel driver issue.

** Summary changed:

- Sound very low, and quality of audio very bad.
+ [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.

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

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

Title:
  [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very
  bad.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio 
quality in Ubuntu is horrible to say the least, It is very low, and in case I 
use VLC or enable overamplification, the quality of sound output becomes worse.
  I have ensured that the volume on alsamixer is 100.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phaneesh   1605 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 21 23:41:49 2019
  InstallationDate: Installed on 2019-05-17 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+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 1829888] Re: Al arrancar la pantalla queda nula

Xorg can't access your GPU:

[97.403] (EE) open /dev/dri/card0: No such file or directory

This is because you are using the kernel command line options 'recovery
nomodeset':

[88.880] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=3f37daeb-b04b-4157
-aeba-7a8cb4e19e1f ro recovery nomodeset

meaning the machine is stuck in "safe mode".

To fix that, please:

1. Reboot and as soon as the purple screen appears tap Escape.
2. Navigate through the menus and find a kernel option to boot that is NOT 
recovery.

** Tags added: radeon

** Summary changed:

- Al arrancar la pantalla queda nula
+ [radeon] Al arrancar la pantalla queda nula

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

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

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

Title:
  [radeon] Al arrancar la pantalla queda nula

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Arranco el ordenador y no consigo poder funcionar porque la pantalla
  que da sin energia. lo apago forzado y al reiniciarlo arranca con la
  pantalla de opciones Ubuntu, lo corrige y ya puedo trabajar, pero la
  siguiente vez que lo arranco vuelve hacer lo mismo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May 21 17:39:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] [1043:3000]
  InstallationDate: Installed on 2017-06-18 (701 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: ASUSTeK Computer INC. V-P8H67E
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=3f37daeb-b04b-4157-aeba-7a8cb4e19e1f ro vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: V-P8H67E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd02/11/2011:svnASUSTeKComputerINC.:pnV-P8H67E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P8H67E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: V-P8H67E
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue May 21 13:41:28 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1829888/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

So for speaker:

If we don't add "model=auto" or "power_save=0", the speaker works fine?
or only works for 10s?

If adding "model=auto", the speaker only works for 10s?

If adding "power_save=0", the speaker doesn't work?

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829540] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

Sorry, it is /etc/modprobe.d/alsa-base.conf rather than /etc/modproble.d
/alsa-base.conf

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After computer returns from being locked, after I type my password,
  the option of where to hear the sounds from the computer appears,
  selecting speaker, still I can not hear any sound from the
  computer!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 17 17:07:11 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2019-02-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0C77WG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3573
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829540/+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 1829913] Re: openconnect VPN is not propagating internal DNS anymore

2019-05-21 Thread Joe_Bishop

I see no 237-3ubuntu10.22

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+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 1829913] Re: openconnect VPN is not propagating internal DNS anymore

Could you also try whether the combination of both the network-manager
update (1.10.14) AND the proposed systemd update (237-3ubuntu10.22) of
bug 1754671 works for you?

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+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 1777512] Re: key retrieval timeouts cause failures

2019-05-21 Thread Jason Hobbs

** No longer affects: cdoqa-system-tests

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

Title:
  key retrieval timeouts cause failures

Status in juju:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  We have been seeing keyserver timeouts causing failed runs at an
  increased rate recently (over the last 6+ months). Here is an example
  failure:

  [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ 
--yes "ppa:curtin-dev/proposed"
  [10.244.40.32] out: Error: retrieving gpg key timed out.

  One idea is that this needs to be addressed by making the client
  (software-properties) more robust.

  
  We have an RT about this:
  https://portal.admin.canonical.com/C112309/

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1777512/+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 1829913] Re: openconnect VPN is not propagating internal DNS anymore

2019-05-21 Thread Joe_Bishop

~ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"


Downgrading to the previous network-manager solves the problem

~ apt policy network-manager
network-manager:
  Installed: 1.10.6-2ubuntu1.1
  Candidate: 1.10.14-0ubuntu2
  Version table:
 1.10.14-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
 *** 1.10.6-2ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
 1.10.6-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

I am afraid I am not smart enough to play with patches and compilation.

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+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 1829857] Re: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-05-21 Thread Steve Langasek

what are the targets of /usr/bin/python and /usr/bin/python2 on your
system?

** Changed in: python-defaults (Ubuntu)
   Status: New => Incomplete

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

Title:
  package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Incomplete
Status in python-django package in Ubuntu:
  New

Bug description:
  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-django 1.6.11-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue May 21 17:26:39 2019
  DuplicateSignature: package:python-django:1.6.11-0ubuntu1.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-11 (1012 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.19
  SourcePackage: python-django
  Title: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-removal 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/python-defaults/+bug/1829857/+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 1829857] Re: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-05-21 Thread Seth Arnold

Hello, can you please provide the output of:

head -1 /usr/bin/pyclean
ls -l /usr/bin/python

Thanks

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

Title:
  package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Incomplete
Status in python-django package in Ubuntu:
  New

Bug description:
  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-django 1.6.11-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue May 21 17:26:39 2019
  DuplicateSignature: package:python-django:1.6.11-0ubuntu1.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-11 (1012 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.19
  SourcePackage: python-django
  Title: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-removal 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/python-defaults/+bug/1829857/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns

Are these DNS servers listed in the output of

systemd-resolve --status

If yes, could you try the updated network-manager in combination with
the proposed systemd update of bug 1754671?

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

Title:
  network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured
  dns

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Bionic:
  New

Bug description:
  On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1
  1.10.14-0ubuntu2` lead to scoped DNS servers defined in
  `/etc/systemd/resolved.conf.d/*.conf` being ignored.

  Downgrading with `sudo apt-get install network-
  manager=1.10.6-2ubuntu1.1` has resolved the issue for now.

  Example systemd-resolved conf:

  [Resolve]
  Cache=no
  DNS=127.0.0.54
  Domains=~.local.org.com

  Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving
  queries in that subdomain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1829913] Re: openconnect VPN is not propagating internal DNS anymore

Which version of Ubuntu are you using? If it is Bionic, could you also
try the systemd update of bug 1754671? If this does not help, try
downgrading network-manager.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+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 1829885] Re: Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

2019-05-21 Thread Seth Arnold

Probably this represents an LVM2 or hardware error instead of something
specific to certificates.

Thanks

** Package changed: ca-certificates (Ubuntu) => ubuntu

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

Title:
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned
  an error code (1)

Status in Ubuntu:
  New

Bug description:
  Encountered during a do-release-upgrade from 16.04.6 LTS to 18.04.2
  LTS.

  Processing triggers for resolvconf (1.79ubuntu10.18.04.3) ...
  Errors were encountered while processing:
   ca-certificates
   ubuntu-release-upgrader-core
   update-manager-core
   update-notifier-common
   snapd
   ubuntu-core-launcher
   software-properties-common
   python3-httplib2
   python3-certifi
   python3-requests
   python3-requests-unixsocket
   python3-apport
   apport
   landscape-common
   ubuntu-server
   ssh-import-id
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 21 16:11:17 2019
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 23
  InstallationDate: Installed on 2017-01-30 (840 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.10
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 23
  UpgradeStatus: Upgraded to bionic on 2019-05-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1829885/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-05-21 Thread Evgeny Vereshchagin

To judge from 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_185445_b37c3@/log.gz,
 VMs seems to also be throwing kernel panics:
```
[0.894903] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[0.895921] EDD information not available.
[0.985183] isapnp: No Plug & Play device found
[0.986013] md: Waiting for all devices to be available before autodetect
[0.987166] md: If you don't use raid, use raid=noautodetect
[0.988330] md: Autodetecting RAID arrays.
[0.989038] md: autorun ...
[0.989525] md: ... autorun DONE.
[0.990139] VFS: Cannot open root device 
"UUID=961ce78b-c06e-4632-9aa0-56a8356b081b" or unknown-block(0,0): error -6
[0.991923] Please append a correct "root=" boot option; here are the 
available partitions:
[0.993406] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[0.994818] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-50-generic 
#54-Ubuntu
[0.996121] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[0.997704] Call Trace:
[0.998138]  dump_stack+0x58/0x81
[0.998713]  panic+0x94/0x1e6
[0.999233]  mount_block_root+0x199/0x234
[1.000111]  ? calibrate_delay+0x190/0x4e0
[1.000833]  ? create_dev.constprop.7+0x3a/0x53
[1.001611]  mount_root+0x33/0x35
[1.002182]  prepare_namespace+0x11b/0x167
[1.002885]  kernel_init_freeable+0x1b3/0x1c5
[1.003634]  ? rest_init+0xa0/0xa0
[1.004238]  kernel_init+0xd/0x100
[1.004830]  ret_from_fork+0x1c/0x38
[1.005892] Kernel Offset: 0x1000 from 0xc100 (relocation range: 
0xc000-0xdf5fdfff)
[1.007376] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)
```
And there is another one at 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_100015_69099@/log.gz
```
[   41.006515] IP: rollback_registered_many+0x141/0x390
[   41.007872] *pdpt = 1da0b001 *pde =  
[   41.009424] Oops: 0002 [#1] SMP PTI
[   41.010396] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc 
aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid 
qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs 
xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 
floppy
[   41.017754] CPU: 0 PID: 85 Comm: kworker/u2:2 Not tainted 4.15.0-50-generic 
#54-Ubuntu
[   41.019883] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[   41.022385] Workqueue: netns cleanup_net
[   41.023459] EIP: rollback_registered_many+0x141/0x390
[   41.024825] EFLAGS: 00010202 CPU: 0
[   41.025783] EAX: 0008 EBX: 0008 ECX: 0020 EDX: 
[   41.027477] ESI: dae31ec4 EDI: 00ff EBP: dae31eac ESP: dae31e88
[   41.029162]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   41.030641] CR0: 80050033 CR2: dfc746c0 CR3: 1da28000 CR4: 001406f0
[   41.032333] Call Trace:
[   41.033030]  ? netdev_run_todo+0x4a/0x300
[   41.034136]  unregister_netdevice_many.part.104+0x10/0x80
[   41.035603]  default_device_exit_batch+0x13c/0x160
[   41.036933]  ? do_wait_intr_irq+0x80/0x80
[   41.038034]  ops_exit_list.isra.8+0x53/0x60
[   41.039169]  cleanup_net+0x18e/0x260
[   41.040152]  process_one_work+0x1b9/0x3d0
[   41.041246]  worker_thread+0x37/0x420
[   41.042254]  kthread+0xf0/0x110
[   41.043115]  ? process_one_work+0x3d0/0x3d0
[   41.044256]  ? kthread_create_worker_on_cpu+0x20/0x20
[   41.045640]  ret_from_fork+0x2e/0x38
[   41.046629] Code: ce d6 89 d8 03 0c 9d c0 34 bc d6 e8 5a d5 92 ff 89 d8 ba 
a0 e2 ce d6 e8 de de 11 00 3b 05 fc e3 ce d6 89 c3 72 d4 bf ff ff ff 00 <00> 00 
00 00 00 00 00 00 00 01 00 ff ff ff ff ff ff fa 16 3e bb
[   41.051663] EIP: rollback_registered_many+0x141/0x390 SS:ESP: 0068:dae31e88
[   41.053543] CR2: 0008
[   41.054464] ---[ end trace 06d0534c6301b91d ]---
[   41.057078] BUG: unable to handle kernel NULL pointer dereference at 
[   41.059059] IP: flush_backlog+0x3f/0x120
[   41.060132] *pdpt = 1da0b001 *pde =  
[   41.061682] Oops:  [#2] SMP PTI
[   41.062649] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc 
aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid 
qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs 
xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 
floppy
[   41.069990] CPU: 0 PID: 149 Comm: kworker/0:1H Tainted: G  D  
4.15.0-50-generic #54-Ubuntu
[   41.072469] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[   41.074954] Workqueue: events_highpri flush_backlo

[Touch-packages] [Bug 1829857] Re: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-05-21 Thread Seth Arnold

The error message from the terminal log:

(Reading database ... 1522438 files and directories currently installed.)
Preparing to unpack .../python-django_1.6.11-0ubuntu1.3_all.deb ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: error processing archive 
/var/cache/apt/archives/python-django_1.6.11-0ubuntu1.3_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1

** Also affects: python-defaults (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-django (Ubuntu)
 Assignee: Dhirendra (dhiru-research) => (unassigned)

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

Title:
  package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  New
Status in python-django package in Ubuntu:
  New

Bug description:
  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-django 1.6.11-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue May 21 17:26:39 2019
  DuplicateSignature: package:python-django:1.6.11-0ubuntu1.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-11 (1012 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.19
  SourcePackage: python-django
  Title: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-removal 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/python-defaults/+bug/1829857/+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 1829857] Re: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-05-21 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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1829857

Title:
  package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  New
Status in python-django package in Ubuntu:
  New

Bug description:
  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-django 1.6.11-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue May 21 17:26:39 2019
  DuplicateSignature: package:python-django:1.6.11-0ubuntu1.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-11 (1012 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.19
  SourcePackage: python-django
  Title: package python-django 1.6.11-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-removal 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/python-defaults/+bug/1829857/+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 1820886] Please test proposed package

Hello João, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.11 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

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

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system

Hello Balint, or anyone else affected,

Accepted apt into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.7.5 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

** Changed in: apt (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

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

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Please test proposed package

Hello Balint, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.11 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

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

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1820886] Please test proposed package

Hello João, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.32 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

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

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

Hello João, or anyone else affected,

Accepted apt into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.7.5 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

** Changed in: apt (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

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

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1821640] Please test proposed package

Hello Balint, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.32 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

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

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

Sorry, what fix are you referring to? Can you point me to a specific
comment?

> Does this mean that if you install the openvpn-systemd-resolved
package your problem gets solved without downgrading network-manager?

Nope, I need that package from the start anyway to make everything work,
I installed it when I installed my laptop with 18.04 when it was hot
from the press last year.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1778844] Reminder of SRU verification policy change

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Cosmic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Fix Released

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  In order to verify the fix, one needs to change MODULES option to dep
  on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot,
  check the system has booted fine. That should not break on systems
  with non nvme disks or systems with non multipath nvme systems, and
  that should now work on multipath nvme systems.

  sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf
  update-initramfs -u -k all
  reboot

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.

  -

  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau l

[Touch-packages] [Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files

After consideration, we're not going to prioritize fixing this for the
EE release (in other words, the Canonical Foundations time isn't going
to be actively working on fixing this). It doesn't mean the bug won't be
fixed, just that there is no company work assigned to the bug.

For now, there's a patch attached, it looks pretty good to me; but I
think it would be best to have that added to Debian first (so it lands
in both Debian and Ubuntu).

Please see https://wiki.ubuntu.com/Debian/Bugs for more info on how you
can submit the patch to Debian (it would be nice if you could do it,
that way you would get credited for it too).

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

Title:
  isc-dhcp-server & isc-dhcp-server6 systemd service units use the same
  RuntimeDirectory leading to loss of pid files

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Xenial:
  Triaged
Status in isc-dhcp source package in Bionic:
  Triaged
Status in isc-dhcp source package in Cosmic:
  Triaged
Status in isc-dhcp source package in Disco:
  Triaged

Bug description:
  dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or
  '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is
  found /run/dhcp-server.

  Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit
  files specify the RuntimeDirectory 'dhcp-server', which is removed
  when either unit stops (and thus would wipe out the other unit's pid
  file, were it being successfully written).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-server 4.3.3-5ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  9 21:34:08 2016
  InstallationDate: Installed on 2016-02-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.dhcp.dhcpd.conf: [modified]
  mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

In the initial posting you say that "systemd-resolve --status" shows the
new DNS but does not get used, could you also try out the systemd fix of
bug 1754671?

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files

** Tags removed: rls-ee-tracking
** Tags added: rls-ee-notfixing

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

Title:
  isc-dhcp-server & isc-dhcp-server6 systemd service units use the same
  RuntimeDirectory leading to loss of pid files

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Xenial:
  Triaged
Status in isc-dhcp source package in Bionic:
  Triaged
Status in isc-dhcp source package in Cosmic:
  Triaged
Status in isc-dhcp source package in Disco:
  Triaged

Bug description:
  dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or
  '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is
  found /run/dhcp-server.

  Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit
  files specify the RuntimeDirectory 'dhcp-server', which is removed
  when either unit stops (and thus would wipe out the other unit's pid
  file, were it being successfully written).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-server 4.3.3-5ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  9 21:34:08 2016
  InstallationDate: Installed on 2016-02-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.dhcp.dhcpd.conf: [modified]
  mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+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 1829785] Re: Evince: ∞ not found

Hello Md, or anyone else affected,

Accepted poppler into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/poppler/0.74.0-0ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: poppler (Ubuntu Disco)
   Status: New => Fix Committed

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

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

Title:
  Evince: ∞ not found

Status in Evince:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Disco:
  Fix Committed

Bug description:
  Impact
  Case-insensitive search of unicde chars in PDF documents is broken

  Test case
  1) Open the attached document in Evince
  2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
  3) Press Ctrl+F and paste the symbol from the clipboard into the search field

  The symbol should be found in the document

  Regression potential
  Check in different pdf renderer using poppler than search still work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1829785/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-05-21 Thread Steve Langasek

> Does this mean that if you install the openvpn-systemd-resolved package
> your problem gets solved without downgrading network-manager? Perhaps we
> could add a dependency which would install this package automatically.

This is a universe package which NetworkManager should not require in
order to properly configure resolved.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1829915] [NEW] Radeon issue

2019-05-21 Thread Marius Helmeseanu

Public bug reported:

 I installed ubuntu 18.04 than upgraded to 19.04 and everything was 
fine(resolution 1920x1080 on a samsung TV) for a few weeks than suddenly it 
dropped to 1024x768.
  I'm running a AMD HD7670 video card with a display port to HDMI cable to the 
tv

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 21 21:25:49 2019
DistUpgraded: 2019-05-20 01:35:47,157 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 
235/310 OEM] [1002:6778] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 7470 [1028:2120]
InstallationDate: Installed on 2019-05-19 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. OptiPlex 755
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to disco on 2019-05-19 (1 days ago)
dmi.bios.date: 06/11/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.98+git1905161830.922d92~oibaf~d
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1905190730.4689e9~oibaf~d
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1905190730.4689e9~oibaf~d
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco third-party-packages ubuntu

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

Title:
  Radeon issue

Status in xorg package in Ubuntu:
  New

Bug description:
   I installed ubuntu 18.04 than upgraded to 19.04 and everything was 
fine(resolution 1920x1080 on a samsung TV) for a few weeks than suddenly it 
dropped to 1024x768.
I'm running a AMD HD7670 video card with a display port to HDMI cable to 
the tv

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 21 21:25:49 2019
  DistUpgraded: 2019-05-20 01:35:47,157 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 
235/310 OEM] [1002:6778] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 7470 [1028:2120]
  InstallationDate: Installed on 2019-05-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 755
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-05-19 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1905161830.922d92~oibaf~d
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1905190730.4689e9~oibaf~d
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git190519

[Touch-packages] [Bug 1829917] [NEW] laptop fails to return from suspend after kernel upgrade

2019-05-21 Thread Kenneth Zadeck

Public bug reported:

most of the time when i do a software update that involves installing a
new kernel, the laptop fails to properly restore the screen when
returning from the suspension.  (i always reboot after doing the update,
that is not the problem).

I can "fix" this by getting into the power management configuration and
changing something (pretty much anything) and then changing it back.
Once i do this,  the computer works properly after a suspend.

It behaves "as if" there were some persistent state whose format or
location changes in an incompatible way with each kernel release and
that this gets reset by the power management app but is not cleared by
the update process.

this is an amd based machine with amd based graphics.

kenny

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pm-utils (not installed)
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May 21 14:30:20 2019
InstallationDate: Installed on 2018-06-21 (333 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  laptop fails to return from suspend after kernel upgrade

Status in pm-utils package in Ubuntu:
  New

Bug description:
  most of the time when i do a software update that involves installing
  a new kernel, the laptop fails to properly restore the screen when
  returning from the suspension.  (i always reboot after doing the
  update, that is not the problem).

  I can "fix" this by getting into the power management configuration
  and changing something (pretty much anything) and then changing it
  back.   Once i do this,  the computer works properly after a suspend.

  It behaves "as if" there were some persistent state whose format or
  location changes in an incompatible way with each kernel release and
  that this gets reset by the power management app but is not cleared by
  the update process.

  this is an amd based machine with amd based graphics.

  kenny

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pm-utils (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 21 14:30:20 2019
  InstallationDate: Installed on 2018-06-21 (333 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1829917/+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 1829913] [NEW] openconnect VPN is not propagating internal DNS anymore

2019-05-21 Thread Joe_Bishop

Public bug reported:

Openconnect VPN stopped propagating DNSes to the system.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1829912] [NEW] Sound very low, and quality of audio very bad.

2019-05-21 Thread Phaneesh G

Public bug reported:

I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio 
quality in Ubuntu is horrible to say the least, It is very low, and in case I 
use VLC or enable overamplification, the quality of sound output becomes worse.
I have ensured that the volume on alsamixer is 100.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  phaneesh   1605 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue May 21 23:41:49 2019
InstallationDate: Installed on 2019-05-17 (4 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Sound very low, and quality of audio very bad.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio 
quality in Ubuntu is horrible to say the least, It is very low, and in case I 
use VLC or enable overamplification, the quality of sound output becomes worse.
  I have ensured that the volume on alsamixer is 100.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phaneesh   1605 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 21 23:41:49 2019
  InstallationDate: Installed on 2019-05-17 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829912/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

In bug 120 you say:

I had this same issue and I circumvented it installing the update-
systemd-resolved script through the openvpn-systemd-resolved package.

Does this mean that if you install the openvpn-systemd-resolved package
your problem gets solved without downgrading network-manager? Perhaps we
could add a dependency which would install this package automatically.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

This test case doesn't involve snaps, notice the file switch to gdb:

--ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"'

This is still an issue with the version of gdb from eoan, 8.3-0ubuntu1,
and eoan's gnome-calculator package.

Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' 
'/srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox/usr/bin/gdb' 
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-prefix 
/srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox' --ex 
'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox' --ex 'set solib-search-path 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/lib/x86_64-linux-gnu:/srv/vms/apport-sandbox-dir/Ubuntu
 19.10/amd64/report-sandbox/usr/lib/x86_64-linux-gnu' --ex 'set data-directory 
/srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox/usr/share/gdb' 
--ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox//usr/bin/gnome-calculator"' --ex 'core-file 
/tmp/apport_core_b_z3909f'
/srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox/usr/bin/gdb: 
warning: Couldn't determine a path for the index cache directory.
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/usr/lib/debug/.build-id/42/410fc27971e3eb1d581449a1687495a876ab5b.debug...
could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/usr/lib/debug/.build-id/42/410fc27971e3eb1d581449a1687495a876ab5b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/usr/lib/debug/.build-id/42/410fc27971e3eb1d581449a1687495a876ab5b.debug)
[New LWP 14762]
[New LWP 14766]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-calculator'.

Attached you'll find the core file for gnome-calculator. Is there
anything more I can give you?

** Attachment added: "apport_core_b_z3909f.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+attachment/5265338/+files/apport_core_b_z3909f.gz

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/li

[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-21 Thread Gunnar Hjalmarsson

Dropping the fonts-noto-cjk Xenial task, since Noto is not default font
for Japanese in Xenial. (Takao is.)

** No longer affects: fonts-noto-cjk (Ubuntu Xenial)

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  New
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  New
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not in

[Touch-packages] [Bug 1829888] [NEW] Al arrancar la pantalla queda nula

2019-05-21 Thread diego muñoz

Public bug reported:

Arranco el ordenador y no consigo poder funcionar porque la pantalla que
da sin energia. lo apago forzado y al reiniciarlo arranca con la
pantalla de opciones Ubuntu, lo corrige y ya puedo trabajar, pero la
siguiente vez que lo arranco vuelve hacer lo mismo.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue May 21 17:39:52 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] [1043:3000]
InstallationDate: Installed on 2017-06-18 (701 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
MachineType: ASUSTeK Computer INC. V-P8H67E
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=3f37daeb-b04b-4157-aeba-7a8cb4e19e1f ro vesafb.invalid=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: V-P8H67E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd02/11/2011:svnASUSTeKComputerINC.:pnV-P8H67E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P8H67E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: V-P8H67E
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue May 21 13:41:28 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  Al arrancar la pantalla queda nula

Status in xorg package in Ubuntu:
  New

Bug description:
  Arranco el ordenador y no consigo poder funcionar porque la pantalla
  que da sin energia. lo apago forzado y al reiniciarlo arranca con la
  pantalla de opciones Ubuntu, lo corrige y ya puedo trabajar, pero la
  siguiente vez que lo arranco vuelve hacer lo mismo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May 21 17:39:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] [1043:3000]
  InstallationDate: Installed on 2017-06-18 (701 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: ASUSTeK Computer INC. V-P8H67E
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=3f37daeb-b04b-4157-aeba-7a8cb4e19e1f ro vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: V-P8H67E
  dmi.board.vendor: ASUSTeK Computer INC.
  dm

[Touch-packages] [Bug 1829588] Re: make it easy to add proposed; help text outdated

Thanks Seth, the "handle proposed" and "remove outdated example" should
probably be separate reports. Note that the project is owned by ubuntu-
core-dev and you can proposed code changes against
https://code.launchpad.net/software-properties (removing the outdated
websites should be easy, unsure if we want to replace them with another
similar example to still describe the corresponding syntax variant
though)

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  make it easy to add proposed; help text outdated

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I want to do some SRU testing but I have to look up how to add the
  -proposed lines to apt sources every time I want to do this task. The
  wiki page for it is pretty verbose and includes text like: "Replace
  "xenial" with "trusty", "vivid", "utopic", "precise", or "lucid"
  depending on which release you are on. "

  Adding -proposed should be as easy as running:

  sudo add-apt-repository proposed

  But this doesn't work:
  $ sudo add-apt-repository proposed
  Error: 'proposed' invalid

  The help text includes a bunch of examples of things that users almost
  never need to do any more:

  $ add-apt-repository -h
  [...]
Examples:
  apt-add-repository 'deb http://myserver/path/to/repo stable myrepo'
  apt-add-repository 'http://myserver/path/to/repo myrepo'
  apt-add-repository 'https://packages.medibuntu.org free non-free'
  apt-add-repository http://extras.ubuntu.com/ubuntu
  apt-add-repository ppa:user/repository
  apt-add-repository ppa:user/distro/repository
  apt-add-repository multiverse

  
  https://packages.medibuntu.org is now owned by a commerce site, or squatter, 
or something similar. It also fails certificate validation. This should be 
removed.

  http://extras.ubuntu.com/ubuntu/dists/ has precise through utopic.
  Maybe we shouldn't remove this yet, but someday we may want to revisit
  this one.

  It'd be great to have examples of adding proposed, universe, security,
  updates, etc.

  Maybe it'd be nice to put a reference to whatever tool would also
  enable ESM.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.7
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Fri May 17 18:32:49 2019
  InstallationDate: Installed on 2012-10-18 (2402 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829588/+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 520546] Re: [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

** Tags removed: verification-done verification-done-bionic 
verification-done-cosmic verification-done-disco verification-done-xenial
** Tags added: verification-failed verification-failed-bionic 
verification-failed-cosmic verification-failed-disco verification-failed-xenial

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

Title:
  [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY,
  and/or unwanted VT switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is

[Touch-packages] [Bug 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco

This bug was fixed in the package software-properties - 0.96.24.32.8

---
software-properties (0.96.24.32.8) bionic; urgency=medium

  * debian/control: Update Vcs-*: URLs
  * debian/gbp.conf: Add default configuration
  * Add .keep files to preserve empty directories
  * Backport Livepatch changes from Disco (LP: #1823761):
- Implement new design for authentication dialog.
- Add livepatch desktop file and icon.
- Move Livepatch UI in a diffrent tab.

 -- Andrea Azzarone   Mon, 08 Apr 2019
16:52:15 +0100

** Changed in: software-properties (Ubuntu Bionic)
   Status: Fix Committed => 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/1823761

Title:
  [SRU] Move Livepatch in a different tab as in Disco

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The livepatch graphical interfaces are currently limited in bionic, there is 
no easy way to know the current status and the details of the changes applied. 
The new design improves the user experience and we want that to benefit the LTS 
users

  * Test case
  Open software-properties-gtk, you should see a livepatch new tab which has 
the detail of the status (including the CVEs fixes with the applied livepatch 
where there is one)

  * Regression potential
  The changes are mostly new code so check that the livepatch tab works 
correctly.
  There is some UI refactoring so it's best to check that the other tabs still 
look the same.
  Note that the changes include some new strings. Those are translated in disco 
and have been announced to the translators in march as coming to bionic for a 
SRU
  (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html).
  Launchpad shares translations between series so we should get those 
translations included in the next bionic langpacks export.

  ---

  Backport the new Livepatch tab from Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+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 1823761] Update Released

The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Move Livepatch in a different tab as in Disco

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The livepatch graphical interfaces are currently limited in bionic, there is 
no easy way to know the current status and the details of the changes applied. 
The new design improves the user experience and we want that to benefit the LTS 
users

  * Test case
  Open software-properties-gtk, you should see a livepatch new tab which has 
the detail of the status (including the CVEs fixes with the applied livepatch 
where there is one)

  * Regression potential
  The changes are mostly new code so check that the livepatch tab works 
correctly.
  There is some UI refactoring so it's best to check that the other tabs still 
look the same.
  Note that the changes include some new strings. Those are translated in disco 
and have been announced to the translators in march as coming to bionic for a 
SRU
  (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html).
  Launchpad shares translations between series so we should get those 
translations included in the next bionic langpacks export.

  ---

  Backport the new Livepatch tab from Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+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 1829885] [NEW] Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

2019-05-21 Thread Robin Corps

Public bug reported:

Encountered during a do-release-upgrade from 16.04.6 LTS to 18.04.2 LTS.

Processing triggers for resolvconf (1.79ubuntu10.18.04.3) ...
Errors were encountered while processing:
 ca-certificates
 ubuntu-release-upgrader-core
 update-manager-core
 update-notifier-common
 snapd
 ubuntu-core-launcher
 software-properties-common
 python3-httplib2
 python3-certifi
 python3-requests
 python3-requests-unixsocket
 python3-apport
 apport
 landscape-common
 ubuntu-server
 ssh-import-id
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error 
code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Tue May 21 16:11:17 2019
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 23
InstallationDate: Installed on 2017-01-30 (840 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.10
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 23
UpgradeStatus: Upgraded to bionic on 2019-05-21 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned
  an error code (1)

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Encountered during a do-release-upgrade from 16.04.6 LTS to 18.04.2
  LTS.

  Processing triggers for resolvconf (1.79ubuntu10.18.04.3) ...
  Errors were encountered while processing:
   ca-certificates
   ubuntu-release-upgrader-core
   update-manager-core
   update-notifier-common
   snapd
   ubuntu-core-launcher
   software-properties-common
   python3-httplib2
   python3-certifi
   python3-requests
   python3-requests-unixsocket
   python3-apport
   apport
   landscape-common
   ubuntu-server
   ssh-import-id
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 21 16:11:17 2019
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 23
  InstallationDate: Installed on 2017-01-30 (840 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.10
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 23
  UpgradeStatus: Upgraded to bionic on 2019-05-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1829885/+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 1820886] Update Released

The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Cosmic:
  In Progress
Status in apt source package in Disco:
  Fix Released

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

This bug was fixed in the package apt - 1.8.1

---
apt (1.8.1) unstable; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Mon, 06 May 2019 10:41:52
+0200

** Changed in: apt (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Cosmic:
  In Progress
Status in apt source package in Disco:
  Fix Released

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system

This bug was fixed in the package apt - 1.8.1

---
apt (1.8.1) unstable; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Mon, 06 May 2019 10:41:52
+0200

** Changed in: apt (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Cosmic:
  In Progress
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Update Released

The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Cosmic:
  In Progress
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-21 Thread Marcus Tomlinson

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

** Changed in: libreoffice-l10n (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  New
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  New
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  New
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports

[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

unicode-data in eoan does include Reiwa. Reverse-depends probably still
need to be rebuilt (I'm testing gucharmap which seemed easy enough to
patch to work).

** Changed in: unicode-data (Ubuntu)
   Status: New => Fix Released

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  New
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  New
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  New
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  New
Status in libreoffice-l10n source package in Disco:
  New
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex charact

[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

mozc appears to be all done (LP: #1823444)

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

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

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

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

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  New
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  New
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  New
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  New
Status in libreoffice-l10n source package in Disco:
  New
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa

[Touch-packages] [Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

added options snd-hda-intel power_save=0 to /etc/modprobe.d/alsa-
base.conf, rebooted and now there is no sound.


!!
!!ALSA Information Script v 0.4.64
!!

!!Script ran on: Tue May 21 14:35:29 UTC 2019


!!Linux Distribution
!!--

Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 19.04"
NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
/privacy-policy" UBUNTU_CODENAME=disco


!!DMI Information
!!---

Manufacturer:  ASUSTeK COMPUTER INC.
Product Name:  GL703VD
Product Version:   1.0
Firmware Version:  GL703VD.308
Board Vendor:  ASUSTeK COMPUTER INC.
Board Name:GL703VD


!!ACPI Device Status Information
!!---

/sys/bus/acpi/devices/ACPI0003:00/status 15
/sys/bus/acpi/devices/ACPI000C:00/status 15
/sys/bus/acpi/devices/ATK4002:00/status  15
/sys/bus/acpi/devices/ELAN1200:00/status 15
/sys/bus/acpi/devices/INT33A1:00/status  15
/sys/bus/acpi/devices/INT33D0:00/status  15
/sys/bus/acpi/devices/INT340E:00/status  15
/sys/bus/acpi/devices/INT345D:00/status  15
/sys/bus/acpi/devices/INT3F0D:00/status  15
/sys/bus/acpi/devices/LNXPOWER:00/status 1
/sys/bus/acpi/devices/LNXPOWER:01/status 1
/sys/bus/acpi/devices/LNXPOWER:02/status 1
/sys/bus/acpi/devices/LNXPOWER:03/status 1
/sys/bus/acpi/devices/LNXPOWER:04/status 1
/sys/bus/acpi/devices/LNXPOWER:05/status 1
/sys/bus/acpi/devices/LNXPOWER:06/status 1
/sys/bus/acpi/devices/LNXPOWER:07/status 1
/sys/bus/acpi/devices/LNXPOWER:08/status 1
/sys/bus/acpi/devices/LNXPOWER:09/status 1
/sys/bus/acpi/devices/LNXPOWER:0a/status 1
/sys/bus/acpi/devices/LNXPOWER:0b/status 1
/sys/bus/acpi/devices/LNXPOWER:0c/status 1
/sys/bus/acpi/devices/LNXPOWER:0d/status 1
/sys/bus/acpi/devices/LNXPOWER:0e/status 1
/sys/bus/acpi/devices/LNXPOWER:0f/status 1
/sys/bus/acpi/devices/LNXPOWER:10/status 1
/sys/bus/acpi/devices/LNXPOWER:11/status 1
/sys/bus/acpi/devices/LNXPOWER:12/status 1
/sys/bus/acpi/devices/LNXPOWER:13/status 1
/sys/bus/acpi/devices/LNXPOWER:14/status 1
/sys/bus/acpi/devices/LNXPOWER:15/status 1
/sys/bus/acpi/devices/LNXPOWER:16/status 1
/sys/bus/acpi/devices/MSFT0101:00/status 15
/sys/bus/acpi/devices/PNP0103:00/status  15
/sys/bus/acpi/devices/PNP0C02:01/status  15
/sys/bus/acpi/devices/PNP0C02:03/status  3
/sys/bus/acpi/devices/PNP0C02:05/status  3
/sys/bus/acpi/devices/PNP0C02:06/status  15
/sys/bus/acpi/devices/PNP0C04:00/status  31
/sys/bus/acpi/devices/PNP0C09:01/status  15
/sys/bus/acpi/devices/PNP0C0A:00/status  31
/sys/bus/acpi/devices/PNP0C0C:00/status  15
/sys/bus/acpi/devices/PNP0C0E:00/status  11
/sys/bus/acpi/devices/PNP0C0F:00/status  9
/sys/bus/acpi/devices/PNP0C0F:01/status  9
/sys/bus/acpi/devices/PNP0C0F:02/status  9
/sys/bus/acpi/devices/PNP0C0F:03/status  9
/sys/bus/acpi/devices/PNP0C0F:04/status  9
/sys/bus/acpi/devices/PNP0C0F:05/status  9
/sys/bus/acpi/devices/PNP0C0F:06/status  9
/sys/bus/acpi/devices/PNP0C0F:07/status  9
/sys/bus/acpi/devices/device:69/status   15
/sys/bus/acpi/devices/device:79/status   11


!!Kernel Information
!!--

Kernel release:5.0.0-15-generic
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: x86_64
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: k5.0.0-15-generic
Library version:1.1.8
Utilities version:  1.1.8


!!Loaded ALSA modules
!!---

snd_hda_intel


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xdf42 irq 134


!!PCI Soundcards installed in the system
!!--

00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev
31)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:1f.3 0403: 8086:a171 (rev 31)
Subsystem: 1043:1bc0


!!Modprobe options (Sound related)
!!

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
s

[Touch-packages] [Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

deleted snd-hda-intel.conf which contained "options snd-hda-intel
model=auto" rebooted and rebooted and there is no sound

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

Oops; picked the wrong openjdk...

FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at
least are affected (so, everything prior to disco if updates are not
applied. Openjdk-8 updates appear to already be at 8u212, which should
include Reiwa support. Marking as Fix Released so we can see at a glance
that it's already been covered.

** Also affects: openjdk-13 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: unicode-data (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: poppler-data (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）
  
  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the work
  needed, and general test cases for verifying that things are working as
  expected.
  
  [Impact]
  Users who run Ubuntu in Japanese.
  
  [Test cases]
  
  == Date conversion ==
  
  On applications that support writing dates in long form, or with symbols
  to denote era (either in X00.00.00 format or in GG1G5G1G format  (G-
  glyph; X- character):
  
  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"
  
  == Date output ==
  
  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"
  
  === Displaying formatted year for Japanese era with glibc ===
  
  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)
  
  == Character maps / font support ==
  
  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:
  
   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)
  
  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the case,
  the unicode data supports the new character, but the selected font does
  not include the new glyph.
  
  == Typing / input methods ==
  
  1) Type in 'heisei'
  2) Verify that the input method in use gives you an option "平成", and 
optionally also the square era glyph.
  3) Type in 'reiwa'
  4) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)
  
  5) Type in the following strings, and verify that the options are provided in 
the input method:
- * "れいわ"(reiwa) => "令和"
- * "れいわ"(reiwa) => "㋿"
- * "２０１８ねん"(2018nenn) => "平成三十年"
- * "２０１８ねん"(2018nenn) => "平成三十年"
- * "２０１９ねん"(2019nenn) => "平成三十一年"
- * "２０１９ねん"(2019nenn) => "令和元年"
- * "２０２０ねん"(2020nenn) => "令和二年"
+ * "れいわ"(reiwa) => "令和"
+ * "れいわ"(reiwa) => "㋿"
+ * "２０１８ねん"(2018nenn) => "平成三十年"
+ * "２０１９ねん"(2019nenn) => "平成三十一年"
+ * "２０１９ねん"(2019nenn) => "令和元年"
+ * "２０２０ねん"(2020nenn) => "令和二年"
  
  /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF.
  
  [Regression potential]
  This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

** No longer affects: openjdk-13 (Ubuntu)

** Also affects: openjdk-8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: openjdk-8 (Ubuntu)
   Status: New => Fix Released

** Also affects: gucharmap (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: unicode-data (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: poppler-data (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: mozc (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libreoffice (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libreoffice-l10n (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: openjdk-8 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** A

[Touch-packages] [Bug 1829785] Re: Evince: ∞ not found

The issue is the same, it's non ascii encoding. The fix is in the eoan poppler 
update, let's SRU to disco
https://launchpad.net/ubuntu/+source/poppler/0.76.1-0ubuntu1

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

** Changed in: poppler (Ubuntu)
   Status: Triaged => Fix Released

** Description changed:

- Package: evince
- Version: 3.32.0-1ubuntu0.1
+ Impact
+ Case-insensitive search of unicde chars in PDF documents is broken
  
- OS: Disco 19.04
- 
- How to reproduce:
- 
+ Test case
  1) Open the attached document in Evince
  2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
  3) Press Ctrl+F and paste the symbol from the clipboard into the search field
- 4) Observe that evince doesn't find the symbol (shows no results in the 
search pane and lightens the search field red). I expect that the symbol, on 
the contrary, is found (i.e., that the pane shows page 1 and some context of 
the symbol).
  
- In qpdfview and okular, the symbol is found, as well as in evince from
- the current debian stable. Any bugfix?
+ The symbol should be found in the document
+ 
+ Regression potential
+ Check in different pdf renderer using poppler than search still work correctly

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

Title:
  Evince: ∞ not found

Status in Evince:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Impact
  Case-insensitive search of unicde chars in PDF documents is broken

  Test case
  1) Open the attached document in Evince
  2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
  3) Press Ctrl+F and paste the symbol from the clipboard into the search field

  The symbol should be found in the document

  Regression potential
  Check in different pdf renderer using poppler than search still work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1829785/+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 1829785] [NEW] Evince: ∞ not found

You have been subscribed to a public bug:

Package: evince
Version: 3.32.0-1ubuntu0.1

OS: Disco 19.04

How to reproduce:

1) Open the attached document in Evince
2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
3) Press Ctrl+F and paste the symbol from the clipboard into the search field
4) Observe that evince doesn't find the symbol (shows no results in the search 
pane and lightens the search field red). I expect that the symbol, on the 
contrary, is found (i.e., that the pane shows page 1 and some context of the 
symbol).

In qpdfview and okular, the symbol is found, as well as in evince from
the current debian stable. Any bugfix?

** Affects: evince
 Importance: Unknown
 Status: Fix Released

** Affects: poppler (Ubuntu)
 Importance: Low
 Status: Fix Released

-- 
Evince: ∞ not found
https://bugs.launchpad.net/bugs/1829785
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to poppler 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] Răsp.: [Bug 1829540] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

2019-05-21 Thread Luciana

The path does not exist.

Trimis din Yahoo Mail pe Android 
 
  Pe sâm., mai 18, 2019 la 6:10, Hui Wang a scris:   
Please edit /etc/modproble.d/alsa-base.conf

add a new line in this file: options snd-hda-intel probe_mask=0x1

reboot

Then suspend your machine and resume, could you still see the similar
problem?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1829540

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After computer returns from being locked, after I type my password,
  the option of where to hear the sounds from the computer appears,
  selecting speaker, still I can not hear any sound from the
  computer!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/pcmC0D0p:  luciana    2245 F...m pulseaudio
  /dev/snd/controlC0:  luciana    2245 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 17 17:07:11 2019
  DistributionChannelDescriptor:
  # This is a distribution channel descriptor
  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
  canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2019-02-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/pcmC0D0p:  luciana    2245 F...m pulseaudio
  /dev/snd/controlC0:  luciana    2245 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0C77WG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3573
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After computer returns from being locked, after I type my password,
  the option of where to hear the sounds from the computer appears,
  selecting speaker, still I can not hear any sound from the
  computer!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 17 17:07:11 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2019-02-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0C77WG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi

[Touch-packages] [Bug 1829872] [NEW] No more desktop effects since libdrm upgrade in Bionic

2019-05-21 Thread Thomas Nemeth

Public bug reported:

Hello.

I upgraded my system on 2019-05-09 and since then desktop effects do not work 
anymore. It installed
a new libdrm stack :

$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk 
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
 libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)
--
 libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)
--
 libdrm2:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)
--
 libdrm-intel1:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)
--
 libdrm-radeon1:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)
--
 libdrm-common:amd64 (2.4.95-1~18.04.1
 2.4.97-1ubuntu1~18.04.1)

I have an ATI Radeon that was working fine with KDE until then. I waited to see 
if someone had realized it before creating a bug report... It really is 
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.

System information :

$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

$ apt-cache policy libdrm2
libdrm2:
  Installé : 2.4.97-1ubuntu1~18.04.1
  Candidat : 2.4.97-1ubuntu1~18.04.1
 Table de version :
 *** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
 2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

Title:
  No more desktop effects since libdrm upgrade in Bionic

Status in libdrm package in Ubuntu:
  New

Bug description:
  Hello.

  I upgraded my system on 2019-05-09 and since then desktop effects do not work 
anymore. It installed
  a new libdrm stack :

  $ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk 
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
   libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm2:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-intel1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-radeon1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-common:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)

  I have an ATI Radeon that was working fine with KDE until then. I waited to 
see if someone had realized it before creating a bug report... It really is 
annoying : no more transparency, no
  more auto-hide of windows : my workflow is strongly impacted.

  System information :

  $ lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  $ apt-cache policy libdrm2
  libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
   Table de version :
   *** 2.4.97-1ubuntu1~18.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.95-1~18.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   2.4.91-2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  In Progress
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  In Progress
Status in udisks2 source package in Eoan:
  Invalid

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1778844] Re: nvme multipath does not report path relationships

2019-05-21 Thread bugproxy

--- Comment From indira.pr...@in.ibm.com 2019-05-21 08:26 EDT---
Installed latest initramfs-tools & kdump-tools packages from -proposed kernel 
as below

root@woo:~# dpkg -l initramfs*
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  initramfs-tools   0.130ubuntu3.8all 
  generic modular initramfs generator (automation)
ii  initramfs-tools-bin   0.130ubuntu3.8ppc64el 
  binaries used by initramfs-tools
ii  initramfs-tools-core  0.130ubuntu3.8all 
  generic modular initramfs generator (core tools)

root@woo:~# dpkg -l kdump-tools*
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  kdump-tools   1:1.6.5-1ubuntu1~18.0 ppc64el 
  scripts and tools for automating kdump (Linux crash dumps)

Triggered crash with nvme disk as root disk ,crash triggered properly
and dump file saved in /var/crash path

root@woo:~# uname -a
Linux woo 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:26:12 UTC 2019 ppc64le 
ppc64le ppc64le GNU/Linux

crash logs:
***
root@woo:~# cd /var/crash
root@woo:/var/crash# ls -l
total 580K
drwxrwxrwt  4 root root 4.0K May 21 07:51 ./
drwxr-xr-x 12 root root 4.0K May 18 12:23 ../
drwxr-xr-x  2 root root 4.0K May 20 13:12 201905201311/
drwxr-xr-x  2 root root 4.0K May 21 07:41 201905210740/
-rw-r--r--  1 root root  228 May 21 07:51 kexec_cmd
-rw-r-  1 root root  31K May 20 13:16 
linux-image-4.15.0-51-generic-201905201311.crash
-rw-r-  1 root root 177K May 21 07:51 
linux-image-4.15.0-51-generic-201905210740.crash
-rw---  1 root root 348K May 18 13:11 ssl-cert.0.crash

root@woo:/var/crash/201905210740# ls
total 538M
drwxr-xr-x 2 root root 4.0K May 21 07:41 ./
drwxrwxrwt 4 root root 4.0K May 21 07:51 ../
-rw--- 1 root root 994K May 21 07:41 dmesg.201905210740
-rw--- 1 root root 537M May 21 07:41 dump.201905210740
root@woo:/var/crash/201905210740# pwd
/var/crash/201905210740
root@woo:/var/crash/201905210740#

Issue is fixed with latest initramfs-tools package.

Regards,
Indira

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

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Cosmic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Fix Released

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  In order to verify the fix, one needs to change MODULES option to dep
  on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot,
  check the system has booted fine. That should not break on systems
  with non nvme disks or systems with non multipath nvme systems, and
  that should now work on multipath nvme systems.

  sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf
  update-initramfs -u -k all
  reboot

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.

  -

  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

This bug was fixed in the package linux - 5.0.0-15.16

---
linux (5.0.0-15.16) disco; urgency=medium

  * CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS

  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux (5.0.0-14.15) disco; urgency=medium

  * linux: 5.0.0-14.15 -proposed tracker (LP: #1826150)

  * [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
(LP: #1825210)
- vbox-update: updates for renamed makefiles
- ubuntu: vbox -- update to 6.0.6-dfsg-1

  * Intel I210 Ethernet card not working after hotplug [8086:1533]
(LP: #1818490)
- igb: Fix WARN_ONCE on runtime suspend

  * [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04
upgrade (LP: #1821663)
- ALSA: hda - Add two more machines to the power_save_blacklist

  * CVE-2019-9500
- brcmfmac: assure SSID length from firmware is limited

  * CVE-2019-9503
- brcmfmac: add subtype check for event handling in data path

  * CVE-2019-3882
- vfio/type1: Limit DMA mappings per container

  * autofs kernel module missing (LP: #1824333)
- [Config] Update autofs4 path in inclusion list

  * The Realtek card reader does not enter PCIe 1.1/1.2 (LP: #1825487)
- misc: rtsx: Enable OCP for rts522a rts524a rts525a rts5260
- SAUCE: misc: rtsx: Fixed rts5260 power saving parameter and sd glitch

  * headset-mic doesn't work on two Dell laptops. (LP: #1825272)
- ALSA: hda/realtek - add two more pin configuration sets to quirk table

  * CVE-2019-3887
- KVM: x86: nVMX: close leak of L0's x2APIC MSRs (CVE-2019-3887)
- KVM: x86: nVMX: fix x2APIC VTPR read intercept

  * CVE-2019-3874
- sctp: implement memory accounting on tx path
- sctp: implement memory accounting on rx path

  * CVE-2019-1999
- binder: fix race between munmap() and direct reclaim

  * apparmor does not start in Disco LXD containers (LP: #1824812)
- SAUCE: shiftfs: use separate llseek method for directories

 -- Stefan Bader   Mon, 06 May 2019 17:33:15
+0200

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...

[Touch-packages] [Bug 1829861] [NEW] handle TLS session renegotiation

Public bug reported:

[Impact]
TLS sessions can renegotiate keys, but APT does not support it; meaning their 
HTTPS connections stop working.

[Test case]
...

[Regression potential]
- Could we get stuck on renegotiation?

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

** Affects: apt (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Also affects: apt (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: apt (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  handle TLS session renegotiation

Status in apt package in Ubuntu:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Cosmic:
  New
Status in apt source package in Disco:
  New
Status in apt source package in Eoan:
  New

Bug description:
  [Impact]
  TLS sessions can renegotiate keys, but APT does not support it; meaning their 
HTTPS connections stop working.

  [Test case]
  ...

  [Regression potential]
  - Could we get stuck on renegotiation?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829861/+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 440036] Re: apt-key list should not change the mtime and ctime on /etc/apt

** Changed in: apt (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  apt-key list should not change the mtime and ctime on /etc/apt

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: apt

  In setting up host intrusion detection software (samhain) I discovered
  that `apt-key list` updates the ctime and mtime on /etc/apt. Poking at
  this with strace, it appears to be because gpg creates some temp file
  in /etc/apt, maybe a lock, I don't know. This is frustrating, as list
  should really be a readonly action, and should not require write
  access, let alone complex HIDS rules excluding it.

  I'm running hardy LTS, and have not tested in anything newer. This
  appears somewhat related to http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=393005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/440036/+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 1829776] Re: apt tries to use whiptail, which won't show

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

** This bug has been marked a duplicate of bug 1827697
   Enroll key whiptail prompt blocks kernel header package upgrades

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

Title:
  apt tries to use whiptail, which won't show

Status in apt package in Ubuntu:
  New

Bug description:
  If I install or update virtualbox-dkms, dpkg needs to ask me to
  configure Secure Boot. This works fine using apt-get (or a GUI), but
  not apt. When installing via apt, whiptail(1) doesn't show, and the
  installation/upgrade process gets stuck, forcing me to kill dpkg then
  run "dpkg --configure -a", then reinstall virtualbox-dkms using apt-
  get.

  Example process tree snippet attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829776/+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 1829860] [NEW] APT unlocks in same order as it locks

Public bug reported:

[Impact]
APT releases the locks in the same order it acquires them, rather than reverse 
order. Given that we have no waiting for locks, this is not _super_ 
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, 
rather than lock-frontend.

[Test case]
...

[Regression potential]
...

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

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

Title:
  APT unlocks in same order as it locks

Status in apt package in Ubuntu:
  New

Bug description:
  [Impact]
  APT releases the locks in the same order it acquires them, rather than 
reverse order. Given that we have no waiting for locks, this is not _super_ 
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, 
rather than lock-frontend.

  [Test case]
  ...

  [Regression potential]
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+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 707540] Re: Destroying pkgCacheFile releases system lock

** Changed in: apt (Ubuntu)
   Status: Confirmed => In Progress

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

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

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

Title:
  Destroying pkgCacheFile releases system lock

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: python-apt

  This code should work, but doesn't:

   >>> import apt_pkg
   >>> apt_pkg.init()
   >>> with apt_pkg.SystemLock():
   ... x = apt_pkg.Cache()
   ... del x
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done
   Traceback (most recent call last):
     File "", line 3, in 
   SystemError: E:Not locked

  (lines beginning with ... should be indented, but Launchpad collapses
  multiple spaces into one when not at the beginning of the line)

  Architecture: amd64
  apt 0.8.10ubuntu1
  python-apt 0.7.100.1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/707540/+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 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug

2019-05-21 Thread Francis Ginther

** Tags added: id-5ccb0d8d44da805739b5de37

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

Title:
  systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  systemd autopkgtest fails

  [test case]

  run systemd autopkgtest, check for output like:

  LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
  FAIL

  ==
  FAIL: test_luks_tmp (__main__.CryptsetupTest)
  LUKS device with "tmp" option
  --
  Traceback (most recent call last):
    File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, 
in setUp
  self.fail('%s exists already' % self.plaintext_dev)
  AssertionError: /dev/mapper/testcrypt1 exists already

  or for older releases something like:

  autopkgtest [19:27:26]: test storage: [---
  modprobe: FATAL: Module scsi_debug not found in directory 
/lib/modules/4.18.0-1011-kvm
  ERROR

  ==
  ERROR: setUpClass (__main__.CryptsetupTest)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21, 
in setUpClass
  subprocess.check_call(['modprobe', 'scsi_debug'])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned 
non-zero exit status 1.

  
  this has attempted to be fixed in disco/eoan so the output is a bit different 
across different releases, but all of them have the common point of failing to 
modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a 
failure.

  [regression potential]

  low; this is fixing a testcase only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

Thanks for new report and confirming that downgrading fixes the issue

** Tags added: regression-update

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1788048] Re: systemd journald failed unmounting var

2019-05-21 Thread Dan Streetman

It seems like the upstream commits to fix this may have made journalctl --flush 
flaky and/or introduced other regressions:
https://github.com/systemd/systemd/pull/12230#issuecomment-491593897

Additionally, the fix upstream is not a trivial backport and has the potential 
to cause even more problems for SRU releases.
https://github.com/systemd/systemd/pull/12230/commits

As this bug is rather limited in scope (only systems with /var or
/var/log mounted separately from /) and the only potential issue I see
is /var isn't cleanly unmounted, it seems like backporting the upstream
fix may bring more problems than it solves.

Possibly there is some simpler workaround we could add for SRU releases,
but it would take some more investigation.  I'm removing myself as bug
owner here, so possibly someone else can investigate, in case I'm not
able to get back to this.

** Tags removed: ddstreet-next

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

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

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

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Disco)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  systemd journald failed unmounting var

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in Disco:
  New
Status in systemd source package in Eoan:
  New

Bug description:
  [impact]

  on a system with /var and/or /var/log mounted separately from /,
  shutdown can't unmount /var (or /var/log) cleanly because systemd-
  journald is using it.

  [test case]

  install a system with /var mounted separately from /

  shutdown, and notice:

  [FAILED] Failed unmounting /var.

  [regression potential]

  TBD

  [other info]

  original description:

  --

  When the system is shut down or restarted the systemd-journal does not
  disassemble the disks correctly.

  On this thread https://unix.stackexchange.com/questions/378678/why-
  do-i-get-the-error-failed-unmounting-var-during-shutdown

  I checked what editing /etc/systemd/journald.conf
  to change the Storage = line to Storage = volatile the problem is solved, but 
some of the logs on the shutdown are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 20 18:15:07 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-08-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  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
  mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1788048/+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 1803993] Re: Password appears on the VT1 screen

2019-05-21 Thread Dan Streetman

This may have caused a regression upstream, see
https://github.com/systemd/systemd/pull/12378#issuecomment-493776598

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-05-21 Thread Evgeny Vereshchagin

@pitti would it be possible to temporarily skip the tests where VMs are
rebooted to reduce the blast radius so to speak? I really don't want to
turn Ubuntu CI off completely.

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  New

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |
  | updated  | 2019-05-16T07:00:42Z 
  |
  | user_id  | 8524250971084851b3792a68fbc398dd 
  |

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

Done: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1829838

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1828171] Re: New toolchain updates need to be rebuilt against -security only

2019-05-21 Thread Matthias Klose

** Also affects: eclipse-titan (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  New toolchain updates need to be rebuilt against -security only

Status in binutils package in Ubuntu:
  New
Status in eclipse-titan package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  New
Status in eclipse-titan source package in Bionic:
  New
Status in gcc-7 source package in Bionic:
  New
Status in gcc-7-cross source package in Bionic:
  New
Status in gcc-7-cross-ports source package in Bionic:
  New
Status in gcc-8 source package in Bionic:
  New
Status in gcc-8-cross source package in Bionic:
  New
Status in gcc-8-cross-ports source package in Bionic:
  New
Status in gcc-defaults source package in Bionic:
  New
Status in gcc-defaults-ports source package in Bionic:
  New
Status in binutils source package in Cosmic:
  New
Status in eclipse-titan source package in Cosmic:
  New
Status in gcc-7 source package in Cosmic:
  New
Status in gcc-7-cross source package in Cosmic:
  New
Status in gcc-7-cross-ports source package in Cosmic:
  New
Status in gcc-8 source package in Cosmic:
  New
Status in gcc-8-cross source package in Cosmic:
  New
Status in gcc-8-cross-ports source package in Cosmic:
  New
Status in gcc-defaults source package in Cosmic:
  New
Status in gcc-defaults-ports source package in Cosmic:
  New

Bug description:
  [Impact]
  With LP: #1814369, the toolchain packages have been updated in both cosmic 
and bionic, but due to an error those packages were built in -proposed as any 
regular SRU. For toolchain updates there exists a policy that those should be 
always built against -security *only*, and then released to both -security and 
-updates.

  Since this is not the case with the current toolchain update, we need
  to no-change rebuild all of the previously released toolchain packages
  in a -security enabled devirt PPA, sync them to -proposed with
  binaries and then release into the archives.

  [Regression Potential]
  As these are toolchain packages, there is always some regression potential. 
These will be no-change rebuilds so in theory the risk should be low, but the 
current versions of the packages have not been built against -security only 
before. It is hard to say how any regressions could manifest themselves.

  [Test Case]
  Making sure there are no reported regressions in the GCC and binutils test 
suites. Hopefully this will be sufficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+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 1829840] [NEW] Sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental (main)

2019-05-21 Thread Sylvestre Ledru

Public bug reported:

Please sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental
(main)

Changelog entries since current eoan version 3.1-20181209-1:

libedit (3.1-20190324-1~exp1) experimental; urgency=medium

  * New upstream release

 -- Sylvestre Ledru   Tue, 02 Apr 2019 12:06:41
+0200

** Affects: libedit (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: libedit (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental
  (main)

Status in libedit package in Ubuntu:
  New

Bug description:
  Please sync libedit 3.1-20190324-1~exp1 (main) from Debian
  experimental (main)

  Changelog entries since current eoan version 3.1-20181209-1:

  libedit (3.1-20190324-1~exp1) experimental; urgency=medium

* New upstream release

   -- Sylvestre Ledru   Tue, 02 Apr 2019 12:06:41
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1829840/+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 1829838] [NEW] 1.10.14-0ubuntu2 breaks DNS propagation from VPN

Public bug reported:

I have an OpenVPN connection, and I use the update-systemd-resolved to
correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu
18.04: the script is no longer invoked, and even invoking it manually
(sudo openvpn myfile.ovpn) does not work anymore, even if in that case
systemd-resolve --status shows the new DNS on the interface correctly.

As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
the issue.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

I can confirm that downgrading fixes the issue. I'll open a new report.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-05-21 Thread Bug Watch Updater

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

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1714178]

2019-05-21 Thread Timo Aaltonen

yeah, thanks! :)

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1714178]

2019-05-21 Thread Jani-saarinen-g

Thanks Ville making this!

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1714178]

2019-05-21 Thread Ville-syrjala-e

Took a while but we got there in the end.

commit 5c000fb33b767c3fa10d29a1021edbf4f92b76a2
Author: Ville Syrjälä 
Date:   Thu May 9 15:21:59 2019 +0300

drm/i915: Bump gen7+ fb size limits to 16kx16k

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1829599] Re: Does not report error about setting an unsupported resample method

Thank you for your bug report, could you also send it upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues ?

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

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

Title:
  Does not report error about setting an unsupported resample method

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Command 'pulseaudio --dump-resample-methods' displays available
  resample methods, but there are more methods described in 'man pulse-
  daemon.conf'. For example, if I run 'pulseaudio --resample-method
  =soxr-hq'. Either it should be documented which resample method is
  used, if an unavailable one is requested, or it should report an
  error. Anyway, as for 'pulseaudio --resample-method=' tab completion
  in Bash works well listing available methods.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May 18 10:26:58 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1699 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829599/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-05-21 Thread Dimitri John Ledkov

** Description changed:

[Impact]

* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.

* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
rapidly adopted due to increased set of supported hashes & algoes, as
well as improved handshake [re-]negotiation.

* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.

[Test Case]

* Rebuild all reverse dependencies

* Execute autopkg tests for all of them

* Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g.
mongodb)

* Backport TLS v1.3 support patches, where applicable

[Test cases for the python updates]

python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.

python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.

python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.

The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:

http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html

And analyzed in

https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652

[Regression Potential]

* Connectivity interop is the biggest issues which will be unavoidable
with introducing TLS v1.3. However, tests on cosmic demonstrate that
curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3
without issues.

* Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side software
or by backporting relevant support fixes

* Notable changes are listed here
https://wiki.openssl.org/index.php/TLS1.3

* Most common connectivity issues so far:
- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname.
Solution is client change to set hostname, or to clamp down the client to
TLSv1.2.

- session negotiation is different in TLSv1.3, existing client code
may fail to create/negotiate/resume session. Clients need to learn how
to use session callback.

-- non-application data records. TLSv1.3 sends more of these, when compared
with previous versions, and some applications may not handle this correctly.
Resulting in application data not being available, when previously expected.
Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or
setting max protocol version to TLSv1.2. For example see discussion identified
in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
+ - non-application data records. TLSv1.3 sends more of these, when compared
with previous versions, and some applications may not handle this correctly.
Resulting in application data not being available, when previously expected.
Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or
setting max protocol version to TLSv1.2. For example see discussion identified
in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
Similar hangs are possible with prior versions of TLS as well, it is however
easier to trigger this with TLSv1.3.
+
+ * Deprecated npn extenstion does not exist in TLSv1.3 implementation.

* This update bundles python 3.6 and 3.7 point releases

[Other Info]

* Previous FFe for OpenSSL in 18.10 is at
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

* TLS v1.3 support in NSS is expected to make it to 18.04 via security
updates

* TLS v1.3 support in GnuTLS is expected to be available in 19.04

* Test OpenSSL is being prepared in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

[Autopkgtest Regressions]

dovecot/armhf - flakey

libnet-ssleay-perl - awaiting sru accept into proposed of
libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
versioned breaks.

linux* - rebuild testcases pa

[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week

2019-05-21 Thread Martin Pitt

Indeed the downstream tests fail like this as well:
http://autopkgtest.ubuntu.com/packages/systemd/eoan/amd64

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  New

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |
  | updated  | 2019-05-16T07:00:42Z 
  |
  | user_id  | 8524250971084851b3792a68fbc398dd 
  |
  
+--+-

[Touch-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

Could well be a bug in gtk3-nocsd

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/58
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1811596/+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 1829829] [NEW] Ubuntu CI has been flaky for a week

2019-05-21 Thread Evgeny Vereshchagin

Public bug reported:

It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0

autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value  
|
+--++
| OS-DCF:diskConfig| MANUAL 
|
| OS-EXT-AZ:availability_zone  | nova   
|
| OS-EXT-SRV-ATTR:host | euler  
|
| OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack   
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a  
|
| OS-EXT-STS:power_state   | 1  
|
| OS-EXT-STS:task_state| -  
|
| OS-EXT-STS:vm_state  | active 
|
| OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00 
|
| OS-SRV-USG:terminated_at | -  
|
| accessIPv4   |
|
| accessIPv6   |
|
| config_drive |
|
| created  | 2019-05-16T07:00:33Z   
|
| flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
| id   | 91e76a78-d05c-412a-b383-55a26010ae69   
|
| image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
| metadata | {} 
|
| name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
| net_ues_proposed_migration network   | 10.42.40.13
|
| os-extended-volumes:volumes_attached | [] 
|
| progress | 0  
|
| security_groups  | autopkgtest@lcy01-27.secgroup  
|
| status   | ACTIVE 
|
| tenant_id| afaef86b96dd4828a1ed5ee395ea1421   
|
| updated  | 2019-05-16T07:00:42Z   
|
| user_id  | 8524250971084851b3792a68fbc398dd   
|
+--++
---
: failure: Timed out on waiting for ssh connection
autopkgtest [07:07:45]: ERROR: testbed failure: cannot send to testbed: [Errno 
32] Broken pipe
```

Though judging by https://github.com/systemd/systemd/pull/12626, it
appears that sometimes the tests pass.

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

--

[Touch-packages] [Bug 1829650] Re: OpenGl

Thank you for your bug report. What version of libreoffice do you use?
Do you have the snap or the deb?

Could you start it from a command line and copy the output when getting
the error (and/or attach the journalctl log from the session)

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

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

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

Title:
  OpenGl

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  So I was messing around in the Libre Office settings and enabled Open
  GL (Hoping for GL acceleration) . Once I restarted Libre office, It
  would load, but a window would appear briefly and close.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun May 19 12:40:25 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  MachineType: LENOVO 2349IP5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=66ca1202-c6da-48c1-be0e-f4b431fb8924 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET91WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349IP5
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET91WW(2.51):bd01/09/2013:svnLENOVO:pn2349IP5:pvrThinkPadT430:rvnLENOVO:rn2349IP5:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349IP5
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun May 19 02:45:50 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1829650/+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 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait

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

** Tags added: rls-bb-incoming

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

Title:
  Apply Bash 4.4.20 to fix cpu spinning on built-in wait

Status in bash package in Ubuntu:
  New

Bug description:
  Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops
  when spawning sub processes and waiting for them. There is a fix:

  https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  Our application started being affected (locking up) by this since
  migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1),
  Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version',
  because of their unusual versions as patches, apt shows it as
  4.4.18-2ubuntu1).

  The 4.4-020 version needs to be included. I think it's actually quite
  critical.

  The Bash bug report mentions longer running loops, but it seems hash
  collisions are the cause, meaning it's just a matter of chance,
  influenced by how fast PIDs are cycled on the machine.

  Edit as per the SRU procedure:

 [Impact]

  Long running bash loops that create and reap processes will crash,
  hanging at 100% CPU.

  A justification for including the fix would be that a standard
  language feature in a script language is broken, and that it's
  indeterminate when it breaks. Considering the wide spread use of bash,
  I'm surprised not more people have reported issues. My and a client
  started having issues with independently of each other very soon after
  upgrading to an affected version.

 [Test Case]

  Run this loop for a few days/weeks:

#!/bin/bash
while true; do
  sleep 0.5 &
  wait
done

  
  It will cause the 'wait' statement to hang, consuming 100% after some 
indeterminate amount of time, dependent on how fast PIDs are cycled in the 
machine.

 [Regression Potential]

  Using 'apt-get source bash' to get the original source version, I
  created a deb that includes the 4.4.20 patch and have been running it
  since April 2nd. The 100% CPU spinning is solved, and no other
  regressions have been observed.

  Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so
  this involves linearly progressing to the next version (so not
  skipping patches).

 [Other Info]

  Official patch to fix, and to bump to 4.4.20:

  http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  The newest Ubuntu tar.xz with patches I could find at:

  http://archive.ubuntu.com/ubuntu/pool/main/b/bash/

  also didn't have the 4.4.20 patch, so it seems no Ubuntu release has
  the fix yet.

  Although not completely sure, this problem seems to have been
  introduced in the 4.4 version of Bash, so in term of LTS versions,
  18.04 and up are affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses