[Touch-packages] [Bug 1841088] Re: curl with -v parameter writes many 'Expire in 200 ms for 1 (transfer 0x55e0729015c0)'

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  curl with -v parameter  writes many 'Expire in 200 ms for 1 (transfer
  0x55e0729015c0)'

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  This is a known issue
  
https://www.linuxquestions.org/questions/slackware-14/curl-expire-in-1-ms-for-1-transfer-0xa5a060-4175649204/

  The fix has already been released, just include the new version of
  curl into the distribution.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: curl 7.64.0-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 22 19:22:39 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-01-06 (592 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: curl
  UpgradeStatus: Upgraded to disco on 2019-07-25 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1841088/+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 1841088] Re: curl with -v parameter writes many 'Expire in 200 ms for 1 (transfer 0x55e0729015c0)'

2019-09-20 Thread Jay Tuckey
This is pretty annoying, can it be fixed soon?

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

Title:
  curl with -v parameter  writes many 'Expire in 200 ms for 1 (transfer
  0x55e0729015c0)'

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  This is a known issue
  
https://www.linuxquestions.org/questions/slackware-14/curl-expire-in-1-ms-for-1-transfer-0xa5a060-4175649204/

  The fix has already been released, just include the new version of
  curl into the distribution.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: curl 7.64.0-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 22 19:22:39 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-01-06 (592 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: curl
  UpgradeStatus: Upgraded to disco on 2019-07-25 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1841088/+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 1832421] [openssl/disco] verification still needed

2019-09-20 Thread Brian Murray
The fix for this bug has been awaiting testing feedback in the -proposed
repository for disco for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  openssl reboot needed message using incorrect path to X server

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

Bug description:
  [Impact]

   * On desktop, upgrading libssl1.1 does not show reboot required
  notification

  [Test Case]

   * Boot ubuntu desktop
   * Upgrade libssl1.1
   * Observe reboot notification pop-up from update-notifier is _not_ shown

  [Regression Potential]

   * Tweaking postinst only to correct for the Xorg path. Current code
  is innert, but is well excercised in prior releases.

  [Other Info]

   * Original bug report:

  Hello, the openssl library postinst file is using pidof /usr/bin/X,
  but that doesn't appear to be the path to the X11 server any more:

  debian/libssl1.1.postinst:

  # Only issue the reboot notification for servers; we proxy this by
  # testing that the X server is not running (LP: #244250)
  if ! pidof /usr/bin/X > /dev/null && [ -x 
/usr/share/update-notifier/notify-reboot-required ]; then
  /usr/share/update-notifier/notify-reboot-required
  fi

  On my 18.04 LTS laptop:

  $ ps auxw | grep Xorg
  root  2440  0.5  0.4 495932 78996 tty7 Rsl+ May10 264:45 
/usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.1
  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: Tue Jun 11 18:06:51 2019
  InstallationDate: Installed on 2012-10-18 (2427 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832421/+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 1832522] [openssl/disco] verification still needed

2019-09-20 Thread Brian Murray
The fix for this bug has been awaiting testing feedback in the -proposed
repository for disco for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  openssl maintainer scripts do not trigger services restart

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

Bug description:
  [Impact]

   * Major libssl ugprades require services to be restarted, for them to 
continue to function correctly at runtime.
   * The maintainer scripts were not adjusted to trigger.

  [Test Case]

   * Install bionic from release pocket and install ssl using daemon e.g. 
openssh-server libapache-mod-ssl
   * Upgrade libssl1.1
   * Ensure that services that use openssl are offered to be restarted.

  [Regression Potential]

   * We are rebuilding libssl1.1 and changing maintainer scripts. Given
  that we have missed upgrade trigger, we will ask users to restart
  services again even if they may have restarted them already.

  [Other Info]
   
   * Previous major libssl upgrade issue of similar nature was
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832522/+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 1017243] Re: Program received signal SIGBUS, Bus error.

2019-09-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Incomplete => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #713
   https://gitlab.freedesktop.org/mesa/mesa/issues/713

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

Title:
  Program received signal SIGBUS, Bus error.

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  i'm using ubuntu 12.10 (i386) with latest updates installed (see end
  of dscription).

  
  i'm trying to use clutter and textures and get a "Bus Error". The attached 
python program can reproduce the error. Here is a backtrace (produced with 
another C program):

  Program received signal SIGBUS, Bus error.
  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  1417  main/texstore.c: No such file or directory.
  (gdb) bt
  #0  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  #1  0xb6d29f01 in _mesa_texstore (ctx=ctx@entry=0x807a218, dims=dims@entry=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768,
  dstSlices=dstSlices@entry=0xbfffea98, srcWidth=srcWidth@entry=3648, 
srcHeight=srcHeight@entry=2736, srcDepth=srcDepth@entry=1, 
srcFormat=srcFormat@entry=6407,
  srcType=srcType@entry=5121, srcAddr=srcAddr@entry=0xa4fde008, 
srcPacking=srcPacking@entry=0x8088cac) at main/texstore.c:4386
  #2  0xb6d2a173 in store_texsubimage (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008, packing=packing@entry=0x8088cac, 
caller=caller@entry=0xb6e4efe5 "glTexSubImage2D") at main/texstore.c:4517
  #3  0xb6d2a795 in _mesa_store_texsubimage2d (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  width=width@entry=3648, height=height@entry=2736, 
format=format@entry=6407, type=type@entry=5121, pixels=pixels@entry=0xa4fde008, 
packing=packing@entry=0x8088cac)
  at main/texstore.c:4653
  #4  0xb6eeaf9a in intelTexSubImage2D (ctx=0x807a218, texImage=0x82a4e40, 
xoffset=1, yoffset=2739, width=3648, height=2736, format=6407, type=5121, 
pixels=0xa4fde008,
  packing=0x8088cac) at intel_tex_subimage.c:164
  #5  0xb6d1535c in texsubimage (ctx=0x807a218, dims=dims@entry=2, 
target=target@entry=3553, level=level@entry=0, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008) at main/teximage.c:2808
  #6  0xb6d18712 in texsubimage (pixels=0xa4fde008, type=5121, format=6407, 
depth=1, height=2736, width=3648, zoffset=0, yoffset=2739, xoffset=1, level=0, 
target=3553,
  dims=2, ctx=) at main/teximage.c:2751
  #7  _mesa_TexSubImage2D (target=3553, level=0, xoffset=1, yoffset=2739, 
width=3648, height=2736, format=6407, type=5121, pixels=0xa4fde008) at 
main/teximage.c:2853
  #8  0xb7a854c6 in _cogl_texture_driver_upload_subregion_to_gl 
(gl_target=3553, gl_handle=6, is_foreign=0, src_x=0, src_y=0, dst_x=1, 
dst_y=2739, width=3648,
  height=2736, source_bmp=0x8071af0, source_gl_format=6407, 
source_gl_type=5121) at ./driver/gl/cogl-texture-driver-gl.c:176
  #9  0xb7ac014a in _cogl_texture_2d_set_region (tex=0x82a7ad0, src_x=0, 
src_y=0, dst_x=1, dst_y=2739, dst_width=3648, dst_height=2736, bmp=0x8071af0)
  at ./cogl-texture-2d.c:783
  #10 0xb7abf004 in cogl_texture_set_region_from_bitmap_EXP (texture=0x82a7ad0, 
src_x=src_x@entry=0, src_y=src_y@entry=0, dst_x=1, dst_y=2739,
  dst_width=dst_width@entry=3648, dst_height=dst_height@entry=2736, 
bmp=bmp@entry=0x8071af0) at ./cogl-texture.c:641
  #11 0xb7ac60d2 in _cogl_atlas_texture_set_region_with_border 
(atlas_tex=atlas_tex@entry=0x82a6770, src_x=src_x@entry=0, src_y=src_y@entry=0, 
dst_x=dst_x@entry=0,
  dst_y=dst_y@entry=0, dst_width=dst_width@entry=3648, 
dst_height=dst_height@entry=2736, bmp=bmp@entry=0x8071af0) at 
./cogl-atlas-texture.c:445
  #12 0xb7ac6f9f in _cogl_atlas_texture_new_from_bitmap 
(bmp=bmp@entry=0x8071aa0, flags=flags@entry=COGL_TEXTURE_NONE, 
internal_format=,
  

[Touch-packages] [Bug 1801540]

2019-09-20 Thread albertogomezmarin
(In reply to Takashi Iwai from comment #280)
> Yours has a different controller chip, so the patch doesn't have any effect
> as is.
> 
> Try a freshly submitted / merged patch on top of the previous fixes:
>  
> https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/
> ?id=d2c63b7dfd06788a466d5ec8a850491f084c5fc2

Will this patch be in the future stable Linux releases ? I mean if Linux 5.3.1 
will have this patch by default.
It is curiosity because I don't know how Linux versions works

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]

2019-09-20 Thread tiwai
Yours has a different controller chip, so the patch doesn't have any
effect as is.

Try a freshly submitted / merged patch on top of the previous fixes:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=d2c63b7dfd06788a466d5ec8a850491f084c5fc2

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1017243]

2019-09-20 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/mesa/mesa/issues/713.

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

Title:
  Program received signal SIGBUS, Bus error.

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  i'm using ubuntu 12.10 (i386) with latest updates installed (see end
  of dscription).

  
  i'm trying to use clutter and textures and get a "Bus Error". The attached 
python program can reproduce the error. Here is a backtrace (produced with 
another C program):

  Program received signal SIGBUS, Bus error.
  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  1417  main/texstore.c: No such file or directory.
  (gdb) bt
  #0  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  #1  0xb6d29f01 in _mesa_texstore (ctx=ctx@entry=0x807a218, dims=dims@entry=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768,
  dstSlices=dstSlices@entry=0xbfffea98, srcWidth=srcWidth@entry=3648, 
srcHeight=srcHeight@entry=2736, srcDepth=srcDepth@entry=1, 
srcFormat=srcFormat@entry=6407,
  srcType=srcType@entry=5121, srcAddr=srcAddr@entry=0xa4fde008, 
srcPacking=srcPacking@entry=0x8088cac) at main/texstore.c:4386
  #2  0xb6d2a173 in store_texsubimage (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008, packing=packing@entry=0x8088cac, 
caller=caller@entry=0xb6e4efe5 "glTexSubImage2D") at main/texstore.c:4517
  #3  0xb6d2a795 in _mesa_store_texsubimage2d (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  width=width@entry=3648, height=height@entry=2736, 
format=format@entry=6407, type=type@entry=5121, pixels=pixels@entry=0xa4fde008, 
packing=packing@entry=0x8088cac)
  at main/texstore.c:4653
  #4  0xb6eeaf9a in intelTexSubImage2D (ctx=0x807a218, texImage=0x82a4e40, 
xoffset=1, yoffset=2739, width=3648, height=2736, format=6407, type=5121, 
pixels=0xa4fde008,
  packing=0x8088cac) at intel_tex_subimage.c:164
  #5  0xb6d1535c in texsubimage (ctx=0x807a218, dims=dims@entry=2, 
target=target@entry=3553, level=level@entry=0, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008) at main/teximage.c:2808
  #6  0xb6d18712 in texsubimage (pixels=0xa4fde008, type=5121, format=6407, 
depth=1, height=2736, width=3648, zoffset=0, yoffset=2739, xoffset=1, level=0, 
target=3553,
  dims=2, ctx=) at main/teximage.c:2751
  #7  _mesa_TexSubImage2D (target=3553, level=0, xoffset=1, yoffset=2739, 
width=3648, height=2736, format=6407, type=5121, pixels=0xa4fde008) at 
main/teximage.c:2853
  #8  0xb7a854c6 in _cogl_texture_driver_upload_subregion_to_gl 
(gl_target=3553, gl_handle=6, is_foreign=0, src_x=0, src_y=0, dst_x=1, 
dst_y=2739, width=3648,
  height=2736, source_bmp=0x8071af0, source_gl_format=6407, 
source_gl_type=5121) at ./driver/gl/cogl-texture-driver-gl.c:176
  #9  0xb7ac014a in _cogl_texture_2d_set_region (tex=0x82a7ad0, src_x=0, 
src_y=0, dst_x=1, dst_y=2739, dst_width=3648, dst_height=2736, bmp=0x8071af0)
  at ./cogl-texture-2d.c:783
  #10 0xb7abf004 in cogl_texture_set_region_from_bitmap_EXP (texture=0x82a7ad0, 
src_x=src_x@entry=0, src_y=src_y@entry=0, dst_x=1, dst_y=2739,
  dst_width=dst_width@entry=3648, dst_height=dst_height@entry=2736, 
bmp=bmp@entry=0x8071af0) at ./cogl-texture.c:641
  #11 0xb7ac60d2 in _cogl_atlas_texture_set_region_with_border 
(atlas_tex=atlas_tex@entry=0x82a6770, src_x=src_x@entry=0, src_y=src_y@entry=0, 
dst_x=dst_x@entry=0,
  dst_y=dst_y@entry=0, dst_width=dst_width@entry=3648, 
dst_height=dst_height@entry=2736, bmp=bmp@entry=0x8071af0) at 
./cogl-atlas-texture.c:445
  #12 0xb7ac6f9f in 

[Touch-packages] [Bug 1017243]

2019-09-20 Thread Elizabethx-de-la-torre-mena
Hello Thomas, is this still valid with latest SW? Thank you.

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

Title:
  Program received signal SIGBUS, Bus error.

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  i'm using ubuntu 12.10 (i386) with latest updates installed (see end
  of dscription).

  
  i'm trying to use clutter and textures and get a "Bus Error". The attached 
python program can reproduce the error. Here is a backtrace (produced with 
another C program):

  Program received signal SIGBUS, Bus error.
  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  1417  main/texstore.c: No such file or directory.
  (gdb) bt
  #0  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  #1  0xb6d29f01 in _mesa_texstore (ctx=ctx@entry=0x807a218, dims=dims@entry=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768,
  dstSlices=dstSlices@entry=0xbfffea98, srcWidth=srcWidth@entry=3648, 
srcHeight=srcHeight@entry=2736, srcDepth=srcDepth@entry=1, 
srcFormat=srcFormat@entry=6407,
  srcType=srcType@entry=5121, srcAddr=srcAddr@entry=0xa4fde008, 
srcPacking=srcPacking@entry=0x8088cac) at main/texstore.c:4386
  #2  0xb6d2a173 in store_texsubimage (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008, packing=packing@entry=0x8088cac, 
caller=caller@entry=0xb6e4efe5 "glTexSubImage2D") at main/texstore.c:4517
  #3  0xb6d2a795 in _mesa_store_texsubimage2d (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  width=width@entry=3648, height=height@entry=2736, 
format=format@entry=6407, type=type@entry=5121, pixels=pixels@entry=0xa4fde008, 
packing=packing@entry=0x8088cac)
  at main/texstore.c:4653
  #4  0xb6eeaf9a in intelTexSubImage2D (ctx=0x807a218, texImage=0x82a4e40, 
xoffset=1, yoffset=2739, width=3648, height=2736, format=6407, type=5121, 
pixels=0xa4fde008,
  packing=0x8088cac) at intel_tex_subimage.c:164
  #5  0xb6d1535c in texsubimage (ctx=0x807a218, dims=dims@entry=2, 
target=target@entry=3553, level=level@entry=0, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008) at main/teximage.c:2808
  #6  0xb6d18712 in texsubimage (pixels=0xa4fde008, type=5121, format=6407, 
depth=1, height=2736, width=3648, zoffset=0, yoffset=2739, xoffset=1, level=0, 
target=3553,
  dims=2, ctx=) at main/teximage.c:2751
  #7  _mesa_TexSubImage2D (target=3553, level=0, xoffset=1, yoffset=2739, 
width=3648, height=2736, format=6407, type=5121, pixels=0xa4fde008) at 
main/teximage.c:2853
  #8  0xb7a854c6 in _cogl_texture_driver_upload_subregion_to_gl 
(gl_target=3553, gl_handle=6, is_foreign=0, src_x=0, src_y=0, dst_x=1, 
dst_y=2739, width=3648,
  height=2736, source_bmp=0x8071af0, source_gl_format=6407, 
source_gl_type=5121) at ./driver/gl/cogl-texture-driver-gl.c:176
  #9  0xb7ac014a in _cogl_texture_2d_set_region (tex=0x82a7ad0, src_x=0, 
src_y=0, dst_x=1, dst_y=2739, dst_width=3648, dst_height=2736, bmp=0x8071af0)
  at ./cogl-texture-2d.c:783
  #10 0xb7abf004 in cogl_texture_set_region_from_bitmap_EXP (texture=0x82a7ad0, 
src_x=src_x@entry=0, src_y=src_y@entry=0, dst_x=1, dst_y=2739,
  dst_width=dst_width@entry=3648, dst_height=dst_height@entry=2736, 
bmp=bmp@entry=0x8071af0) at ./cogl-texture.c:641
  #11 0xb7ac60d2 in _cogl_atlas_texture_set_region_with_border 
(atlas_tex=atlas_tex@entry=0x82a6770, src_x=src_x@entry=0, src_y=src_y@entry=0, 
dst_x=dst_x@entry=0,
  dst_y=dst_y@entry=0, dst_width=dst_width@entry=3648, 
dst_height=dst_height@entry=2736, bmp=bmp@entry=0x8071af0) at 
./cogl-atlas-texture.c:445
  #12 0xb7ac6f9f in _cogl_atlas_texture_new_from_bitmap 
(bmp=bmp@entry=0x8071aa0, flags=flags@entry=COGL_TEXTURE_NONE, 
internal_format=,
  internal_format@entry=COGL_PIXEL_FORMAT_RGB_888) at 
./cogl-atlas-texture.c:768
  #13 0xb7abe1fa in cogl_texture_new_from_bitmap (bitmap=0x8071aa0, 

[Touch-packages] [Bug 1843999] Re: Printing fails since last update

2019-09-20 Thread Adrian Midgley
I had previously installed Gimp-Gutenprint as the driver for the
printer, via the control panel, and in fact going via Gimp File Print
gets a print, with the Gutenprint options in the "ordinary" print
dialogue.  I'm not sure it is quite so good though, so far, and I don't
have the icc profile stuff.

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

Title:
  Printing fails since last update

Status in cups package in Ubuntu:
  New

Bug description:
  I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
  It fails each time, reporting filter failure.
  I forget what the last update was, yesterday or day before, but it is only 
since then.

  ESC/P utility can print a nozzle check from the printer, that's
  working.

  CUPS seems to be telling me that a filter failed, due to a mismatch
  between device colour model and profile.

  I've tried with no profile in the setup:printer dialogue, no
  different.

  Where should I look?
  Is it likely to be a change in the last update?

  
  I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


  W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
  org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
  path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
  has already been added
  E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
  E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
  E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
  errors; please consult the error_log file for details.
  D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
  recorded from 00:29:51 to 00:29:51
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
  queued by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
  "Stylus-Photo-R2400" by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
  D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
  D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
  application/vnd.cups-pdf, cost 66)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
  (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
  (application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
  D [14/Sep/2019:00:29:51 +0100] [Job 350]
  argv[3]="[8-channel-printer-a] (imported)"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
  StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
  ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
  StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
  StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
  StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
  StpColorCorrection=None StpLightMagentaScale=None
  Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
  StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
  StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
  StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
  StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
  StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
  StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
  StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
  StpFineYellowDensity=None StpFineHGray2Trans=None
  StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
  StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
  StpFineHGray4Scale=None StpFineYellowBalance=None
  StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBleed
  StpFineHGray1Trans=None StpYellowBalance=None MediaType=Plain
  StpLightCyanValue=None StpBlackGamma=None StpContrast=None
  StpInkSet=ultra3photo StpFineDropSize1=None StpFineDropSize2=None
  StpFineDropSize3=None StpColorPrecision=Best StpFineMagentaGamma=None
  StpFineHGray2Value=None StpFineHGray3Scale=None
  StpPrintingDirection=None StpLightCyanScale=None
  StpFineLightMagentaTrans=None StpFineBlackDensity=None number-up=1
  StpFineHGray2Scale=None StpSubchannelCutoff=None StpImageType=Photo
  

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

2019-09-20 Thread Bryan Quigley
Yes, if we can get it into dev, I'd happily make debdiffs to SRU it to
bionic/disco.

>And please just that alone?
Yes, just updating the patch to your latest version. I'm ok if it needs to be 
queued up for SRU with other systemd changes if that's what you are getting at.

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 726033] Re: does not display icons until hovered

2019-09-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #334
   https://gitlab.freedesktop.org/mesa/mesa/issues/334

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

Title:
  does not display icons until hovered

Status in Mesa:
  Unknown
Status in Nux:
  Fix Released
Status in Unity:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: unity-place-applications

  while unity-places-files and the unity launcher display their content
  on launching, unity-place-applications does not display anything until
  the respecting elements were activated (hovering, clicking). see
  screenshot for the look, where only a few icons were hovered.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity-place-applications 0.2.34-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  Architecture: i386
  Date: Sun Feb 27 14:13:47 2011
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-place-applications
  --- 
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1400x1050 1400x1050 1280x1024 1280x1024 1280x960 1280x854 1280x800 
1280x720 1152x768 1024x768 1024x768 800x600 800x600 848x480 720x480 640x480 
640x480
   edid-base64: 
AP///wAwrkNPAQOAHhd46q8AmVhTjColUFQhCACBgAEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMAMeQQAAAYKCN4IFEaEEAwcBMAMeQQAAAYDwCQQzKQQygUBgAyDAAA/gBMUDE1MEUwNS1BMgogAJs=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc M66GL [ATI Mobility FireGL V5250] [1002:71d4] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20a4]
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild__: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  MachineType: LENOVO 2007FVG
  Package: unity 3.4.6-0ubuntu1
  PackageArchitecture: i386
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature_: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature__: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Renderer: Unknown
  Tags: natty running-unity natty running-unity natty running-unity ubuntu 
compiz-0.9
  Uname: Linux 2.6.38-5-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007FVG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007FVG:pvrThinkPadT60p:rvnLENOVO:rn2007FVG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007FVG
  dmi.product.version: ThinkPad T60p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4-0ubuntu1
  version.libdrm2: libdrm2 2.4.23-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/726033/+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 726033]

2019-09-20 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/mesa/mesa/issues/334.

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

Title:
  does not display icons until hovered

Status in Mesa:
  Unknown
Status in Nux:
  Fix Released
Status in Unity:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: unity-place-applications

  while unity-places-files and the unity launcher display their content
  on launching, unity-place-applications does not display anything until
  the respecting elements were activated (hovering, clicking). see
  screenshot for the look, where only a few icons were hovered.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity-place-applications 0.2.34-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  Architecture: i386
  Date: Sun Feb 27 14:13:47 2011
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-place-applications
  --- 
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1400x1050 1400x1050 1280x1024 1280x1024 1280x960 1280x854 1280x800 
1280x720 1152x768 1024x768 1024x768 800x600 800x600 848x480 720x480 640x480 
640x480
   edid-base64: 
AP///wAwrkNPAQOAHhd46q8AmVhTjColUFQhCACBgAEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMAMeQQAAAYKCN4IFEaEEAwcBMAMeQQAAAYDwCQQzKQQygUBgAyDAAA/gBMUDE1MEUwNS1BMgogAJs=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc M66GL [ATI Mobility FireGL V5250] [1002:71d4] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20a4]
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild__: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  MachineType: LENOVO 2007FVG
  Package: unity 3.4.6-0ubuntu1
  PackageArchitecture: i386
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature_: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature__: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Renderer: Unknown
  Tags: natty running-unity natty running-unity natty running-unity ubuntu 
compiz-0.9
  Uname: Linux 2.6.38-5-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007FVG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007FVG:pvrThinkPadT60p:rvnLENOVO:rn2007FVG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007FVG
  dmi.product.version: ThinkPad T60p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4-0ubuntu1
  version.libdrm2: libdrm2 2.4.23-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu5

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

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

[Touch-packages] [Bug 1807440] Re: sensible-browser cannot process $BROWSER variable when it contains a whitespace character

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sensible-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  sensible-browser cannot process $BROWSER variable when it contains a
  whitespace character

Status in sensible-utils package in Ubuntu:
  Confirmed

Bug description:
  If path to a browser defined via the $BROWSER environment variable
  contains a whitespace character, running sensible-browser should
  launch browser defined by $BROWSER.

  If path to a browser defined via the $BROWSER environment variable
  contains a whitespace character, running sensible-browser will not
  parse the whitespace characters and therefore not load the browser
  defined by $BROWSER.

  Bug can be fixed by updating line 8 in /usr/bin/sensible-browser:
  ${BROWSER} "$@" > "${BROWSER}" "$@"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sensible-utils 0.0.12
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 11:05:17 2018
  Dependencies:

  InstallationDate: Installed on 2018-12-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sensible-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1807440/+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 1752053] Re: nvidia-390 fails to boot graphical display

2019-09-20 Thread truf
Faced with this problem in Lenovo G780, NVIDIA 635M and nvidia-
driver-390 package

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
Kernel Version: 5.0.0-29-generic

Addition of "WaylandEnable=false" to
/usr/share/lightdm/lightdm.conf.d/90-nvidia.conf resolved the problem.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1769297] Re: resume from hibernation broken when resume image is autodetected

2019-09-20 Thread Dimitri John Ledkov
** Tags added: rls-ee-incoming

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1843381] Re: Dell system takes a long time to connect network with external dock

2019-09-20 Thread Francis Ginther
** Tags added: id-5d84ab32951ae364f0c9f3b7

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

Title:
  Dell system takes a long time to connect network with external dock

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This is a bug reopen from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700
  The original one caused systemd regressed.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651

  This issue needs an alternative solution.
  

  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch
  [5]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1843381/+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 1832356] Re: Upgrade OpenSSH to 7.9p1-10 or better in stable series

2019-09-20 Thread Marc Deslauriers
** Changed in: openssh (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Upgrade OpenSSH to 7.9p1-10 or better in stable series

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Confirmed
Status in openssh source package in Cosmic:
  Won't Fix
Status in openssh source package in Disco:
  Fix Released
Status in openssh source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * 18.04 LTS release with a long support time frame
   * There are two versions of OpenSSL shipped in 18.04:
 - obsolete 1.0.2
 - current long term supported 1.1.1 series
   * OpenSSH in 18.04 is the only package in main using libcrypto from 1.0.2
   * The fact that OpenSSH uses a different libcrypto implementation impacts 
certification, 
 compliance, and security maintenance.
   * Furthermore OpenSSH does not benefit from hardware accelerated crypto, as 
available in 1.1.1
   * Thus there is a desire to upgrade OpenSSH in 18.04 from 1:7.6p1-4 to 
1:7.9p1-10 and compile 
 against OpenSSL 1.1.1
   * 1:7.9p1-10 is currently shipped in Disco/Eoan, and it is likely that 20.04 
will ship with 
 1:8.0p1 or newer. Thus security maintainance burden is slightly increased. 
However, 1:7.9p1-10
 is likely to be shipped in the next stable Debian release, and supported 
there for a long-ish
 time including debian-lts efforts. Thus there are some synergies.

  [Upstream Changelogs]

   * https://www.openssh.com/txt/release-7.9
   * https://www.openssh.com/txt/release-7.8
   * https://www.openssh.com/txt/release-7.7

  [Test Case]

   * Install openssh-server and openssh-client, check that they depend on 
libssl1.1 and do not depend 
 on libssl1.0
   
   * Check that there are no new connectivity issues between old/new servers 
and clients,
 at the very least between various Ubuntu releases in the public clouds.

  [Regression Potential]

  v7.9

   * ssh(1), sshd(8): the setting of the new CASignatureAlgorithms
 option (see below) bans the use of DSA keys as certificate
 authorities.

  DSA keys as certificate authorities are widely banned already. May
  affect connectivity.

   * sshd(8): the authentication success/failure log message has
 changed format slightly. It now includes the certificate
 fingerprint (previously it included only key ID and CA key
 fingerprint).

  This may impact log parsers, i.e. logwatch and similar. Possibly worth
  a NEWS entry.

  v7.8

   * ssh-keygen(1): write OpenSSH format private keys by default
 instead of using OpenSSL's PEM format. The OpenSSH format,
 supported in OpenSSH releases since 2014 and described in the
 PROTOCOL.key file in the source distribution, offers substantially
 better protection against offline password guessing and supports
 key comments in private keys. If necessary, it is possible to write
 old PEM-style keys by adding "-m PEM" to ssh-keygen's arguments
 when generating or updating a key.

  Normally, it shouldn't matter which format newly generated keys use.
  Existing keys remain unchanged. Systems that automatically
  generate/parse/store keys may be impacted. The risk here is low. As
  potential mitigation we can revert the default back to PEM for the SRU
  into bionic.

   * sshd(8): remove internal support for S/Key multiple factor
 authentication. S/Key may still be used via PAM or BSD auth.

  S/Key is not widely deployed. Most common OTP implementations use PAM
  stack, and use HOTP, TOTP, Yubikey and similar one time passwords,
  rather than S/Key. This is deemed low.

   * ssh(1): remove vestigal support for running ssh(1) as setuid. This
 used to be required for hostbased authentication and the (long
 gone) rhosts-style authentication, but has not been necessary for
 a long time. Attempting to execute ssh as a setuid binary, or with
 uid != effective uid will now yield a fatal error at runtime.

  This is security and hardening improvement. We do not ship sshd
  setuid.

   * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar
 HostbasedAcceptedKeyTypes options have changed. These now specify
 signature algorithms that are accepted for their respective
 authentication mechanism, where previously they specified accepted
 key types. This distinction matters when using the RSA/SHA2
 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their
 certificate counterparts. Configurations that override these
 options but omit these algorithm names may cause unexpected
 authentication failures (no action is required for configurations
 that accept the default for these options).

  This is potentially a problem. We can add upgrade hooks to warn users
  about these, or abort the 

[Touch-packages] [Bug 1844790] [NEW] Update OpenSSH in bionic to (1:7.9p1-10) for FIPS

2019-09-20 Thread Marc Deslauriers
*** This bug is a duplicate of bug 1832356 ***
https://bugs.launchpad.net/bugs/1832356

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

Public security bug reported:

Now that OpenSSL 1.1.1 has been added to Bionic, we would like to update
OpenSSH to a version that can be linked to OpenSSL 1.1.1.

We would like to do this for two reasons:

1- The security team would like for the entirety of packages in main to be 
linked to OpenSSL 1.1.1 for maintenance reasons.
2- The security team would like OpenSSH to be build against OpenSSL 1.1.1 for 
FIPS certification.

Version (1:7.9p1-10) from Disco is compatible with OpenSSL 1.1.1, and
would be the version we would use.

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

** This bug has been marked a duplicate of bug 1832356
   Upgrade OpenSSH to 7.9p1-10 or better in stable series

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

Title:
  Update OpenSSH in bionic to (1:7.9p1-10) for FIPS

Status in openssh package in Ubuntu:
  New

Bug description:
  Now that OpenSSL 1.1.1 has been added to Bionic, we would like to
  update OpenSSH to a version that can be linked to OpenSSL 1.1.1.

  We would like to do this for two reasons:

  1- The security team would like for the entirety of packages in main to be 
linked to OpenSSL 1.1.1 for maintenance reasons.
  2- The security team would like OpenSSH to be build against OpenSSL 1.1.1 for 
FIPS certification.

  Version (1:7.9p1-10) from Disco is compatible with OpenSSL 1.1.1, and
  would be the version we would use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1844790/+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 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

2019-09-20 Thread Adam Collard
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

** Changed in: maas
   Status: Confirmed => Invalid

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

Title:
  Consider supporting IPv6 autoconf in configure_networking

Status in MAAS:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Because DHCPv6 only does addresses, and not routes,
  configure_networking needs to wait for the kernel to process a router-
  advertisement before returning claiming an IPv6 config (since all it
  will have is a /128 and no routes, making for a pretty useless network
  stack.)  See Bug #1609898 for context.

  (The syntax for ip= should probably also be extended to allow SLAAC
  configuration.  If the user said "dhcp", then we should insist on
  getting our answer from DHCP.)

  On the bright side, iscsi retries, so after 1 or more failures to
  connect, the router-advertisement comes in and the connect succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+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 1784499] Re: AppArmor treats regular NFS file access as network op

2019-09-20 Thread John Johansen
zyga well patches are welcome ;-)

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

Title:
  AppArmor treats regular NFS file access as network op

Status in AppArmor:
  Confirmed
Status in snapd:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 
audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2788 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y 

[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

2019-09-20 Thread John Johansen
With that said, some networking work is being done this cycle and we
will try to address this.

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

Title:
  AppArmor treats regular NFS file access as network op

Status in AppArmor:
  Confirmed
Status in snapd:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 
audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" 

[Touch-packages] [Bug 1833046] Re: 18.04 timesyncd stop working after rack controller installed

2019-09-20 Thread Newell Jensen
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: maas
   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/1833046

Title:
  18.04 timesyncd stop working after rack controller installed

Status in MAAS:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  This is an upstream bug from systemd, see details here:

  https://github.com/systemd/systemd/issues/7883

  But it's directly triggered by install maas -> avahi-daemon enabled ->
  nsswitch.conf changed.

  `timedatectl status` will always return "System clock synchronized:
  no" on rack controller host.

  systemd-timesyncd will exit immediately after start, strace
  /lib/systemd/systemd-timesyncd give me the following error:

  ```
  writev(2, [{iov_base="Cannot resolve user name systemd"..., iov_len=58}, 
{iov_base="\n", iov_len=1}], 2Cannot resolve user name systemd-timesync: No 
such process
  ) = 59
  exit_group(1)   = ?
  +++ exited with 1 +++
  ```

  I'm not sure if maas can provide some workaround on this by default,
  right now I fix it by:

  sudo useradd -r systemd-timesync

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1833046/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2019-09-20 Thread Adam Collard
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

** Changed in: maas
   Status: Confirmed => Invalid

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Invalid
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Released
Status in ifupdown source package in Yakkety:
  Fix Released
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  The systemd networking.service unit will bring down the loopback device (lo)
  when it is stopped.  This behavior differs from the behavior in other
  Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.

  The problem that was seen was that iscsi root over ipv6 would hang on
  shutdown.  

  [Test Case]
  Test is fairly simple and can be demonstrated in lxc container.
  The key is really that the lo device should not have its link set down
  after stopping networking.service.  So, below:
out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty

  should not show 'empty', but should have LOOPBACK,UP,LOWER in its
  output.

  $ release=yakkety; name=y1
  $ lxc launch ubuntu-daily:$release $name
  $ sleep 10
  $ lxc exec $name /bin/bash

  ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  empty

  ## Now enable proposed, install update, reboot and show.
  % rel=$(lsb_release -sc)
  % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  sudo tee /etc/apt/sources.list.d/proposed.list
  % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  
  [Regression Potential]
  Should be pretty low.  zesty and  yakkety-proposed have this.
  Taking down 'lo' is often cause of problems, and never the solution to
  problems as far as I'm aware.

  [Other Info]

  === End SRU Template ===

  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1621507: ipv6 network boot does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
** Description changed:

  This is a tracker bug for getting HDR support integrated in Ubuntu.
  
  Kernel
- - 5.3 (i915 on Ice Lake)
+ i915:
+ - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
+ - gen4+ needs https://patchwork.freedesktop.org/series/63373/
+ - so anything beyond initial Ice Lake support will not be in 5.4
  
  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942
  
  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804
  
  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
looks like media driver is fixed as well

** Changed in: intel-media-driver (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
likewise with ffmpeg

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

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
we have libva 2.5.0 which should contain that commit already

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

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

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2019-09-20 Thread Gunnar Hjalmarsson
Reopening the ibus (ubuntu) task.

Background:
The change in ibus 1.5.19-1ubuntu3, which set the abstract socket path to 
'unix:tmpdir=/tmp/ibus', was upstreamed and is now included in the 1.5.21 
source. However, the path proved to not work well on BSD systems:

https://github.com/ibus/ibus/issues/2116

That resulted in a new upstream approach to make the path
indistinguishable, and to make a long story short, the path is about to
be changed in 1.5.22 to 'unix:tmpdir=$XDG_CACHE_HOME/ibus'. To prevent
yet another change in this respect in the ff cycle, I propose that we
change it in eoan again and add two upstream commits so Ubuntu 19.10 is
released with the new (final?) path.

Proposed upload in this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

** Bug watch added: github.com/ibus/ibus/issues #2116
   https://github.com/ibus/ibus/issues/2116

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

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur 

[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

2019-09-20 Thread Zygmunt Krynicki
I'm marking this bug as a property (good or bad is in the eye of the
beholder) of the kernel stack. The snapd project cannot do anything
about it.

** Changed in: apparmor
   Status: New => Confirmed

** Changed in: snapd
   Status: New => Invalid

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

Title:
  AppArmor treats regular NFS file access as network op

Status in AppArmor:
  Confirmed
Status in snapd:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived clusters

2019-09-20 Thread Lucas Kanashiro
** Also affects: heartbeat (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: heartbeat (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: heartbeat (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: heartbeat (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: heartbeat (Ubuntu Disco)
   Status: New => Triaged

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

** Changed in: heartbeat (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: heartbeat (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

** Changed in: heartbeat (Ubuntu Disco)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

** Changed in: heartbeat (Ubuntu Eoan)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

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

Title:
  [master] Restarting systemd-networkd breaks keepalived clusters

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Triaged
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in heartbeat source package in Bionic:
  Triaged
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in heartbeat source package in Disco:
  Triaged
Status in keepalived source package in Disco:
  Confirmed
Status in systemd source package in Disco:
  Confirmed
Status in heartbeat source package in Eoan:
  Triaged
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  

[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Gary Wang
I also put information for HDR feature in media's software stack
(ffmpeg/libva/iHD driver(media-driver)/

intel's video codec with HDR is enabled in Linux media stack for transcoding, I 
list the code commits of media libraries related to HDR for reference,
FFmpeg 
https://github.com/FFmpeg/FFmpeg/commit/38a413213216fc7add112f67e26326492c859c08
Libva
https://github.com/intel/libva/commit/cf11abe5e1b9c93ee75cf974076957162c1605b9
intel's iHD driver
https://github.com/intel/media-driver/commit/7e0ebbc794e83202808f6404f20f2a41c32a181d

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

Title:
  HDR support for Ubuntu 20.04

Status in intel-media-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
** Package changed: libva (Ubuntu) => intel-media-driver (Ubuntu)

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

Title:
  HDR support for Ubuntu 20.04

Status in intel-media-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: intel-media-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  HDR support for Ubuntu 20.04

Status in intel-media-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1844775/+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 1844634] Re: Removals keep removing dependencies if removal of a package fails

2019-09-20 Thread Bug Watch Updater
** Changed in: apt (Debian)
   Status: New => 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/1844634

Title:
  Removals keep removing dependencies if removal of a package fails

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

Bug description:
  [Impact]

  Assuming packages A and B, with A depending on B. A has a failing
  prerm script.

  Expected behavior:
  - A fails to be removed, A and B stay unchanged
  Actual behavior:
  - A fails to be removed
  - B is still removed

  This might crash their system (e.g. if A is systemd and B is
  libsystemd0).

  [Test case]
  See Impact. An automated version of the test case 
(test-apt-get-remove-depends) is included and run on autopkgtest.

  [Regression potential]
  We now abort earlier in removal failures, that might be harder to recover 
from or not, nobody really knows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1844634/+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 1843394] Re: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1

2019-09-20 Thread Lucas Kanashiro
** Changed in: ipxe (Ubuntu)
   Status: New => Triaged

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

** Tags added: server-next

** Changed in: ipxe (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 /
  binutils 2.32.51.20190905-0ubuntu1

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  New
Status in ipxe package in Ubuntu:
  Triaged

Bug description:
  This might be due to new gcc-9 being more strict, but the build that
  worked before now fails with:

  arch/x86_64/core/gdbidt.S: Assembler messages:
  arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push'
  arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push'
  arch/x86_64/core/gdbidt.S:161: Error: operand type mismatch for `pop'
  arch/x86_64/core/gdbidt.S:162: Error: operand type mismatch for `pop'
  make[2]: *** [Makefile.housekeeping:937: bin-x86_64-efi/gdbidt.o] Error 1

  Full log at: https://launchpadlibrarian.net/441262285/buildlog_ubuntu-
  eoan-amd64.ipxe_1.0.0+git-20190109.133f4c4-0ubuntu2_BUILDING.txt.gz

  Now all of this is about push/pop of %fs and %gs.
  That needs to match the size of the registers which depend on the current 
running mode.

  In this particular case in ./src/arch/x86_64/core/gdbidt.S
  The failing file is in ".code64" mode.
  In that I'd expect %gs/%fs to be 64 bit.

  
  Usually we see push/pop "w" in .code16 (word), l in .code32 (long) but in 
that sense here q (quad word) seems right at first (should be what correctly 
matches the .code64).
  That matches what I see throughout the ipxe code but also throughout the 
archive 
https://codesearch.debian.net/search?q=pop%5Ba-z%5D.*%25fs=0=2

  Maybe I misread the mode it is in, or it is actually a false positives.
  Or the sizes of FS/GS do not change - haven't touched them in a lng time.
  Was it that segment registers didn't change size?
  I'll need to do a few checks to first see what the compiler would expect 
there and from there need to understand this.

  The command used also points to AS being in 64 bit mode when this happens:
  gcc -E  -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce 
-fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 
-mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie -mno-red-zone 
-Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include 
-Iarch/x86_64/include/efi -Os -g -ffreestanding -Wall -W -Wformat-nonliteral  
-fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  -fno-unwind-tables 
-fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@' -DASSEMBLY  -DOBJECT=gdbidt arch/x86_64/core/gdbidt.S | as  
--64-o bin-x86_64-efi/gdbidt.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1843394/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
** No longer affects: mesa (Ubuntu Ff-series)

** No longer affects: mutter (Ubuntu Ff-series)

** No longer affects: weston (Ubuntu Ff-series)

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

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

Title:
  HDR support for Ubuntu 20.04

Status in intel-media-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: weston (Ubuntu Ff-series)
   Status: New => Confirmed

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (Ubuntu Ff-series)
   Status: New => Confirmed

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (Ubuntu Ff-series)
   Status: New => Confirmed

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 1844775] Re: HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
** Description changed:

  This is a tracker bug for getting HDR support integrated in Ubuntu.
  
  Kernel
  - 5.3 (i915 on Ice Lake)
+ - plus at least https://patchwork.freedesktop.org/series/65656/
  
  Mesa
- - needs current git master plus 
+ - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942
  
  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804
  
  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in weston package in Ubuntu:
  Confirmed
Status in mesa source package in FF-Series:
  Confirmed
Status in mutter source package in FF-Series:
  Confirmed
Status in weston source package in FF-Series:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 828538] Re: Europe/Moscow not updated

2019-09-20 Thread Adam Conrad
** Changed in: tzdata (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Europe/Moscow not updated

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  Please, update zone Russia (Europe/Moscow, etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

2019-09-20 Thread Dimitri John Ledkov
@bryanquigley are you going to SRU that?

And please just that alone?

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1844775] [NEW] HDR support for Ubuntu 20.04

2019-09-20 Thread Timo Aaltonen
Public bug reported:

This is a tracker bug for getting HDR support integrated in Ubuntu.

Kernel
- 5.3 (i915 on Ice Lake)

Mesa
- needs current git master plus 
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

Mutter:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

Weston:
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

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

** Affects: mesa (Ubuntu Ff-series)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: mutter (Ubuntu Ff-series)
 Importance: Undecided
 Status: New

** Affects: weston (Ubuntu Ff-series)
 Importance: Undecided
 Status: New

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

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

** Also affects: mesa (Ubuntu Ff-series)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Ff-series)
   Importance: Undecided
   Status: New

** Also affects: weston (Ubuntu Ff-series)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu Ff-series)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Summary changed:

- HDR support for Ubuntu
+ HDR support for Ubuntu 20.04

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

Title:
  HDR support for Ubuntu 20.04

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New
Status in mesa source package in FF-Series:
  New
Status in mutter source package in FF-Series:
  New
Status in weston source package in FF-Series:
  New

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  - 5.3 (i915 on Ice Lake)

  Mesa
  - needs current git master plus 
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844775/+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 964438] Re: The hour did not go forward today when it should have (UK)

2019-09-20 Thread Adam Conrad
Looks like this bug got lost long ago, as did the system it was reported
from.  That said, the original bug claimed it was "GMT", which is a
timezone that doesn't do daylight savings time, so likely the fix was
"use Europe/London" or similar.

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

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

Title:
  The hour did not go forward today when it should have (UK)

Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  I'm in the GMT timezone and the time should be 10:45 but it's 9:45 on
  my Ubuntu system.

  This means all OCSP responses are invalid:

  The OCSP response is not yet valid (contains a date in the future).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: tzdata 2012b-1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 25 09:41:46 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120201.1)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/964438/+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 1042547] Re: Debconf/Log.pm

2019-09-20 Thread Adam Conrad
This bug reported against precise (and almost certainly the wrong
package) isn't obviously reproducible in current supported releases.

** Changed in: tzdata (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Debconf/Log.pm

Status in tzdata package in Ubuntu:
  Won't Fix

Bug description:
  Good day.

  I can't update my system(ubuntu 12.04) becouse i recieve that message

  "Can't locate Debconf/Log.pm in @INC"...

  but my @INC contain that package.

  What can I do?
  Thanks.
  ___
  With best regards
  Tigran Hovhannisyan.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: tzdata 2012e-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  Date: Tue Aug 28 09:56:57 2012
  DpkgTerminalLog:
   Setting up tzdata (2012e-0ubuntu0.12.04) ...
   Can't locate Debconf/Db.pm in @INC (@INC contains: 
/usr/local/lib/perl5/site_perl/5.16.0/i686-linux 
/usr/local/lib/perl5/site_perl/5.16.0 /usr/local/lib/perl5/5.16.0/i686-linux 
/usr/local/lib/perl5/5.16.0 .) at /usr/share/debconf/frontend line 6.
   BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
   dpkg: error processing tzdata (--configure):
subprocess installed post-installation script returned error exit status 2
  DuplicateSignature:
   Setting up tzdata (2012e-0ubuntu0.12.04) ...
   Can't locate Debconf/Db.pm in @INC (@INC contains: 
/usr/local/lib/perl5/site_perl/5.16.0/i686-linux 
/usr/local/lib/perl5/site_perl/5.16.0 /usr/local/lib/perl5/5.16.0/i686-linux 
/usr/local/lib/perl5/5.16.0 .) at /usr/share/debconf/frontend line 6.
   BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
   dpkg: error processing tzdata (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  SourcePackage: tzdata
  Title: package tzdata 2012e-0ubuntu0.12.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1042547/+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 1830495] Re: tzdata noninteractive mode is being ignored

2019-09-20 Thread Adam Conrad
I can't reproduce this locally.  See below.  Is there anything extra
special about this environment?

(bionic-amd64)root@nosferatu:~# debconf-show debconf
* debconf/frontend: Readline
  debconf-apt-progress/title:
  debconf-apt-progress/media-change:
  debconf-apt-progress/info:
  debconf-apt-progress/preparing:
* debconf/priority: high
(bionic-amd64)root@nosferatu:~# apt-get purge tzdata && rm /etc/timezone 
[...]
Purging configuration files for tzdata (2019b-0ubuntu0.18.04) ...
(bionic-amd64)root@nosferatu:~# apt-get install tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/190 kB of archives.
After this operation, 3106 kB of additional disk space will be used.
Preconfiguring packages ...
Configuring tzdata
--

Please select the geographic area in which you live. Subsequent configuration 
questions will narrow
this down by presenting a list of cities, representing the time zones in which 
they are located.

  1. Africa   3. Antarctica  5. Arctic  7. Atlantic  9. Indian11. SystemV  
13. Etc
  2. America  4. Australia   6. Asia8. Europe10. Pacific  12. US
Geographic area: 
[...]

(bionic-amd64)root@nosferatu:~# apt-get purge tzdata && rm /etc/timezone 
[...]
Purging configuration files for tzdata (2019b-0ubuntu0.18.04) ...
(bionic-amd64)root@nosferatu:~# DEBIAN_FRONTEND=noninteractive apt-get install 
tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/190 kB of archives.
After this operation, 3106 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package tzdata.
(Reading database ... 10885 files and directories currently installed.)
Preparing to unpack .../tzdata_2019b-0ubuntu0.18.04_all.deb ...
Unpacking tzdata (2019b-0ubuntu0.18.04) ...
Setting up tzdata (2019b-0ubuntu0.18.04) ...

Current default time zone: 'Etc/UTC'
Local time is now:  Fri Sep 20 09:20:00 UTC 2019.
Universal Time is now:  Fri Sep 20 09:20:00 UTC 2019.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(bionic-amd64)root@nosferatu:~#


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

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

Title:
  tzdata noninteractive mode is being ignored

Status in tzdata package in Ubuntu:
  Incomplete

Bug description:
  This bug is related to Bug #1773687

  I am trying to automate the build of an AMI with a package that
  requires tzdata. I am blocked from automation because tzdata will not
  install non-interactively. This is despite setting
  DEBIAN_FRONTEND=noninteractive.

  Here is an interactive session that shows the same problem.

  
  ```
  ubuntu@ip-172-31-95-248:~$ env
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  SSH_CONNECTION=172.58.185.180 50092 172.31.95.248 22
  LANG=C.UTF-8
  XDG_SESSION_ID=3
  USER=ubuntu
  PWD=/home/ubuntu
  HOME=/home/ubuntu
  SSH_CLIENT=172.58.185.180 50092 22
  XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
  DEBIAN_FRONTEND=noninteractive
  SSH_TTY=/dev/pts/0
  MAIL=/var/mail/ubuntu
  

[Touch-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-09-20 Thread Colin Ian King
@Robert, was there a specific class of virtual machine you were using
when this issue occurred?

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1843381] Re: Dell system takes a long time to connect network with external dock

2019-09-20 Thread Che Cheng
I would like to propose to write a rule to rename a removable Realtek
8153 interface with ID_NET_NAME_PATH instead of ID_NET_NAME_MAC.

The solution may impact users using Realtek 8153 and manipulate it by
the interface name since the name is not consistent and will change when
switching USB port. Networkmanager is not affected since it identifies
interfaces via UUID.

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

Title:
  Dell system takes a long time to connect network with external dock

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This is a bug reopen from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700
  The original one caused systemd regressed.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651

  This issue needs an alternative solution.
  

  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch
  [5]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

2019-09-20 Thread Sebastien Bacher
** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

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

Status in Ayatana Design:
  New
Status in NetworkManager:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1844518] Re: Ubuntu 19:10 - Python 3 os.path.isfile not working as expected

2019-09-20 Thread Brian Murray
** Changed in: python3-defaults (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubuntu 19:10 - Python 3 os.path.isfile not working as expected

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  When one runs "os.path.isfile("/vmlinuz")" or the same for
  os.path.exists, False is returned. However, given the information at:
  https://docs.python.org/3.8/library/os.path.html#os.path.isfile and
  https://docs.python.org/3.7/library/os.path.html#os.path.isfile, True
  should be returned for links as well.

  "os.path.islink("/vmlinuz")" works as expected, so I'm not sure what's
  going on here.

  Any ideas? It could be my VM as it's been running 19.10 for a little
  while now.

  Hamish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1844518/+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