[Touch-packages] [Bug 1571864] Re: update-motd.5 manpage references /var/run/motd

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~vorlon/ubuntu/+source/pam/+git/pam/+merge/341556

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

Title:
  update-motd.5 manpage references /var/run/motd

Status in pam package in Ubuntu:
  New

Bug description:
  Hi,

  The update-motd.5 manpage still references /var/run/motd, while the
  code is actually writing to /run/motd.dynamic

  The manpage should be updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1571864/+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 1755675] Re: Ubuntu 17.10 OpenVPN DNS Leaks

[LPNow]

CRAP I finally got it!

Now some people might not like the idea of disabling systemd, but as I
explain below, I'm not seeing problems on simple networks.

sudo systemctl disable systemd-resolved.service
sudo service systemd-resolved stop

Delete the symlink /etc/resolv.conf
rm /etc/resolv.conf

Install openresolv

Edit NetworkManager.conf

[main]
plugins=ifupdown,keyfile
rc-manager=resolvconf
dns=default

Restart network-manager
sudo service network-manager restart

Edit resolvconf.conf

name_server_blacklist=192.168.1.1

I have as example 192.168.1.1 to block my router, put in the nameserver
that appears in resolv.conf you want to block when starting the VPN.

Now when you check resolv.conf before connecting to the VPN it will look
like this as example;


# Generated by NetworkManager
nameserver 192.168.1.1

Connect now to your VPN and it will look like this as example;

# Generated by resolvconf
nameserver 12.1.12.1


ENJOY! :)

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

Title:
  Ubuntu 17.10 OpenVPN DNS Leaks

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager
  and OpenVPN, that DNS leaks from the Router or ISP, instead of only
  being tunneled from the VPN...

  I have spent hours playing with this, it's beyond absurd, the amount
  of time and effort needed to try and resolve something that should be
  working out the box!

  This is not LFS, or Slackware, in fact Slackware is simpler and easier
  to make this work in less then 5 mins!

  Seriously this has been an ongoing issue for ages/years in Ubuntu, and
  the end-users typically for Ubuntu are inexperienced users, again, the
  only thing end-users should have to do is install the correct OpenVPN
  packages, configure OpenVPN in the NetworkManager and it works, but it
  doesn't!

  While Canonical works on trying to resolve this, can someone PLEASE
  tell me a simple way in which to prevent DNS leaks while using OpenVPN
  through the NetworkManager?

  THANKS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755675/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Doug McMahon]

18.04 should really get the new driver, whether it's easier to do before or 
after release I don't know but it should be done.
For some reason Debian hasn't added it yet but that shouldn't stop Ubuntu from 
doing so.
In addition to bug symptoms there are other advantages to going to 2.1. For 
example there is a new interface for EGL interop, vaAcquireSurfaceHandle() in 
libva 2.1 but you need the 2.1 driver to implement.
So while the 2.1.x driver will certainly be available via ppa's before too long 
Ubuntu should plan on providing in 18.04 as best achieved.

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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice

[Touch-packages] [Bug 1756484] Re: Screen flickers and small moving artifacts

[Scott Palmer]

I believe I have corrected this by changing my refresh rate from 59.99
Hz to 59.86 Hz.

Is this a requirement for 2560x1600 resolution on DL-DVI?  Should this
perhaps be communicated upstream to someone who knows better?

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756484/+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 1669517] Re: apt-key del must absolutely detect all errors, and then provide NON-zero return code and error message

[Etienne URBAH]

In package 'apt' 1.6~beta1 from Kubuntu Bionic Beaver Beta1 (18.04) :

-  The 'apt-key' command is still present,

-  'apt-key del' still does NOT detect that the keyid given in parameter is 
invalid :
   It still erroneously displays 'OK' and provides a return code equal to zero.

** Tags added: bionic

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

Title:
  apt-key del must absolutely detect all errors, and then provide NON-
  zero return code and error message

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Currently, 'apt-key del' does NOT detect that the keyid given in parameter is 
invalid :
  It displays 'OK' and provides a return code equal to zero (see log below).

  I consider that letting erroneously believe that a GPG key has been
  successfully removed is a security issue.

  In fact 'apt-key del' must absolutely detect all errors, and then
  provide NON-zero return code and error message.

  
  # wget  -q  -O -  https://oss.oracle.com/el4/RPM-GPG-KEY-oracle  |  apt-key  
--keyring /etc/apt/trusted.gpg.d/oracle.gpg  add  -
  OK

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list
  /etc/apt/trusted.gpg.d/oracle.gpg
  -
  pub   1024D/B38A8516 2006-09-05 [expired: 2013-09-06]
  uid  Oracle OSS group (Open Source Software group) 


  
  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  del 1024D/B38A8516
  OK

  # echo $?
  0

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list
  /etc/apt/trusted.gpg.d/oracle.gpg
  -
  pub   1024D/B38A8516 2006-09-05 [expired: 2013-09-06]
  uid  Oracle OSS group (Open Source Software group) 


  
  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  del B38A8516
  OK

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list

  #

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar  2 17:34:07 2017
  InstallationDate: Installed on 2014-11-03 (849 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1669517/+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 1710752] Re: Intel HDA Audio doesn't work

[Scott Palmer]

I just installed the 18.04 daily and formatted a fresh partition (no
prior home directory or any existing data used) and this is still an
issue in 4.15.0-12-generic.

Can I run a command to manually turn on this jack at startup or force it
to recheck that input to see if something is plugged in?

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

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1756484] [NEW] Screen flickers and small moving artifacts

[Scott Palmer]

Public bug reported:

This is likely a wayland issue.  I can't bear the tearing if I don't use
wayland.

I get screen flickering (approximately every 5 seconds) and some windows
seem to bring up some mis-colored moving artifacts that clear when the
window is closed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 20:07:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic reproducible ubuntu wayland-session

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1755675] Re: Ubuntu 17.10 OpenVPN DNS Leaks

[LPNow]

Sorry I left out a package name.

I am a Linux Geek and I've spent a huge amount of time on this, to the
extent that no one should ever have to spend, and I'm not coming up with
a simple solution to this.

I'd greatly appreciate it if someone can tell me a simple way to this,
without having to install several things like openresolv, unbound,
etc...

Thanks

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

Title:
  Ubuntu 17.10 OpenVPN DNS Leaks

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager
  and OpenVPN, that DNS leaks from the Router or ISP, instead of only
  being tunneled from the VPN...

  I have spent hours playing with this, it's beyond absurd, the amount
  of time and effort needed to try and resolve something that should be
  working out the box!

  This is not LFS, or Slackware, in fact Slackware is simpler and easier
  to make this work in less then 5 mins!

  Seriously this has been an ongoing issue for ages/years in Ubuntu, and
  the end-users typically for Ubuntu are inexperienced users, again, the
  only thing end-users should have to do is install the correct OpenVPN
  packages, configure OpenVPN in the NetworkManager and it works, but it
  doesn't!

  While Canonical works on trying to resolve this, can someone PLEASE
  tell me a simple way in which to prevent DNS leaks while using OpenVPN
  through the NetworkManager?

  THANKS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755675/+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 1751797] Re: NetworkManager incorrectly uses resolved' route-only DNS setting, resulting in dns resolution only working for domains in 'search'.

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.4-1ubuntu3

---
network-manager (1.10.4-1ubuntu3) bionic; urgency=medium

  * Cherry-pick a partial patch from 1.11 branch, to stop agressively
setting route_only flag on nameservers in the systemd-resolved dns
plugin. LP: #1751797

 -- Dimitri John Ledkov   Thu, 15 Mar 2018 15:24:01
+

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => 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/1751797

Title:
  NetworkManager incorrectly uses resolved' route-only DNS setting,
  resulting in dns resolution only working for domains in 'search'.

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  After reboot, dns was broken.
  This is a very simple Network Manager managed interface that has dhcp.

  $ nmcli device show enp0s25  | pastebinit
  http://paste.ubuntu.com/p/sMVTdrMBxJ/

  
  I've attached systemd-resolve --status output.

  In order to file the bug I just modified /etc/resolv.conf to put the
  dns server in directly.

  Other information, it seems like it just will only look for dns under
  my search domains from the dhcp server:

  $ systemd-resolve home.mosers.us
  home.mosers.us: 23.28.108.176

  -- Information acquired via protocol DNS in 1.5ms.
  -- Data is authenticated: no

  $ systemd-resolve google.com
  google.com: resolve call failed: No appropriate name servers or networks for 
name found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:35:32 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751797/+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 1754888] Re: Menulibre: invalid desktop files detected!

[Sean Davis]

** Changed in: menulibre
   Status: Fix Committed => Fix Released

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Released
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/menulibre/+bug/1754888/+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 1754888] Re: Menulibre: invalid desktop files detected!

[Sean Davis]

Vim's desktop file is actually working as expected here. The TryExec key
is used to determine if the desktop file is usable... and when the vim
binary is missing, it is not.

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

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

** Also affects: menulibre
   Importance: Undecided
   Status: New

** Changed in: menulibre
   Status: New => Fix Committed

** Changed in: menulibre
 Assignee: (unassigned) => Sean Davis (bluesabre)

** Changed in: menulibre
Milestone: None => 2.2.0

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Committed
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/menulibre/+bug/1754888/+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 1756349] Re: Null pointer dereference on '.dump' or 'SELECT * FROM sqlite_master' on corrupted file

[Seth Arnold]

Use CVE-2018-8740.

Thanks Even and Richard.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-8740

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

Title:
  Null pointer dereference on '.dump' or 'SELECT * FROM sqlite_master'
  on corrupted file

Status in sqlite3 package in Ubuntu:
  Confirmed

Bug description:
  Starting with sqlite 3.7.10 and up to latest sqlite 3.22.0/master, the 
following on the attached database causes a segmentation fault.
  I can reproduce this on Ubuntu Xenial 16.04 with libsqlite3-0:amd64 
3.11.0-1ubuntu1. Should also affect Ubuntu Trusty that ship with sqlite 3.8.2

  $ echo ".dump" | valgrind sqlite3 gdal_ossfuzz_6964.db

  ==12781== Memcheck, a memory error detector
  ==12781== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==12781== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==12781== Command: .libs/sqlite3 
/home/even/gdal/trunk/gdal/gdal_ossfuzz_6964.db
  ==12781== 
  PRAGMA foreign_keys=OFF;
  BEGIN TRANSACTION;
  ==12781== Invalid read of size 8
  ==12781==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==12781==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==12781==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==12781==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==12781==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==12781==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==12781==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==12781==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==12781==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==12781==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==12781==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==12781==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)
  ==12781==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==12781== 
  ==12781== 
  ==12781== Process terminating with default action of signal 11 (SIGSEGV)
  ==12781==  Access not within mapped region at address 0x0
  ==12781==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==12781==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==12781==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==12781==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==12781==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==12781==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==12781==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==12781==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==12781==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==12781==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==12781==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==12781==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)

  This is a bug of the library and not the shell since the same occurs
  on this trivial C file

  mytest.c:

  {{{
  #include 

  int main(int argc, char* argv[])
  {
  sqlite3* hDB = 0;
  int nRowCount = 0, nColCount = 0;
  char** papszResult = 0;
  sqlite3_open(argv[1], );
  if( !hDB )
  return 1;
  sqlite3_get_table( hDB, "SELECT * FROM sqlite_master",
 , , ,
 0 );
  sqlite3_free_table(papszResult);
  sqlite3_close(hDB);
  return 0;
  }
  }}}

  $ gcc -Wall mytest.c -o mytest -lsqlite3

  $ valgrind ./mytest gdal_ossfuzz_6964.db
  ==24793== Memcheck, a memory error detector
  ==24793== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==24793== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==24793== Command: ./mytest /home/even/gdal/trunk/gdal/gdal_ossfuzz_6964.db
  ==24793== 
  ==24793== Invalid read of size 8
  ==24793==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==24793==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==24793==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==24793==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==24793==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==24793==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==24793==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==24793==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==24793==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==24793==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==24793==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==24793==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)
  ==24793==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==24793== 

  Based on the git clone at 
  https://github.com/mackyle/sqlite, I've bisected the first bad commit to be
  {{{
  fee0225c95052006f0776d837eeafd26b857db53 is the first bad commit
  commit fee0225c95052006f0776d837eeafd26b857db53
  Author: D. Richard Hipp 

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Launchpad Bug Tracker]

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

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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
 

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Launchpad Bug Tracker]

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

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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Prasad Murthy]

I can confirm this bug exists.

OS version: Ubuntu 18.04 beta rc
Hardware: Intel core i5 7400 (Kaby lake processor)
with Intel HD graphics 630 supporting VP9 10-bit and 8-bit video decoding.


In version 1.8.x of the driver the VP9 decoding is broken, the corresponding 
upstream patch got into 2.0.0. But since VP9 profiles are missing in 2.0.0 
driver in Ubuntu, hardware acceleration is absent, so high cpu and power usage. 
The buggy driver 1.8.x is used in the vlc snap too and snap developers doubt 
the driver version in snap will be upgraded. 

* VP9 decoding broken in 17.10
* VP9 decoding broken in snap packages
* VP9 decoding broken in 18.04 beta rc

Either driver version has to be updated to 2.1.0 or at-least cherry pick
a one line patch to current Ubuntu core snap, a link for which I will
mention below.

Upstream driver patch: https://github.com/intel/intel-vaapi-
driver/commit/9d66570032fb02b1e79a883af7697b035d700a8e

Upstream bug report: https://github.com/intel/intel-vaapi-
driver/issues/297

In any way kindly support VP9 hardware decoding via supported Intel
hardwares in 18.04 or in 17.10(by backporting/cherry picking) or atleast
via updated snap core/apps.


** Bug watch added: github.com/intel/intel-vaapi-driver/issues #297
   https://github.com/intel/intel-vaapi-driver/issues/297

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in libva package in Ubuntu:
  New

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:

[Touch-packages] [Bug 1756349] Re: Null pointer dereference on '.dump' or 'SELECT * FROM sqlite_master' on corrupted file

[Seth Arnold]

** Information type changed from Private Security to Public Security

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

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

Title:
  Null pointer dereference on '.dump' or 'SELECT * FROM sqlite_master'
  on corrupted file

Status in sqlite3 package in Ubuntu:
  Confirmed

Bug description:
  Starting with sqlite 3.7.10 and up to latest sqlite 3.22.0/master, the 
following on the attached database causes a segmentation fault.
  I can reproduce this on Ubuntu Xenial 16.04 with libsqlite3-0:amd64 
3.11.0-1ubuntu1. Should also affect Ubuntu Trusty that ship with sqlite 3.8.2

  $ echo ".dump" | valgrind sqlite3 gdal_ossfuzz_6964.db

  ==12781== Memcheck, a memory error detector
  ==12781== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==12781== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==12781== Command: .libs/sqlite3 
/home/even/gdal/trunk/gdal/gdal_ossfuzz_6964.db
  ==12781== 
  PRAGMA foreign_keys=OFF;
  BEGIN TRANSACTION;
  ==12781== Invalid read of size 8
  ==12781==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==12781==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==12781==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==12781==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==12781==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==12781==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==12781==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==12781==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==12781==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==12781==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==12781==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==12781==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)
  ==12781==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==12781== 
  ==12781== 
  ==12781== Process terminating with default action of signal 11 (SIGSEGV)
  ==12781==  Access not within mapped region at address 0x0
  ==12781==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==12781==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==12781==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==12781==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==12781==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==12781==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==12781==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==12781==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==12781==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==12781==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==12781==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==12781==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)

  This is a bug of the library and not the shell since the same occurs
  on this trivial C file

  mytest.c:

  {{{
  #include 

  int main(int argc, char* argv[])
  {
  sqlite3* hDB = 0;
  int nRowCount = 0, nColCount = 0;
  char** papszResult = 0;
  sqlite3_open(argv[1], );
  if( !hDB )
  return 1;
  sqlite3_get_table( hDB, "SELECT * FROM sqlite_master",
 , , ,
 0 );
  sqlite3_free_table(papszResult);
  sqlite3_close(hDB);
  return 0;
  }
  }}}

  $ gcc -Wall mytest.c -o mytest -lsqlite3

  $ valgrind ./mytest gdal_ossfuzz_6964.db
  ==24793== Memcheck, a memory error detector
  ==24793== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==24793== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==24793== Command: ./mytest /home/even/gdal/trunk/gdal/gdal_ossfuzz_6964.db
  ==24793== 
  ==24793== Invalid read of size 8
  ==24793==at 0x4E9302B: sqlite3EndTable (sqlite3.c:82695)
  ==24793==by 0x4EC129A: yy_reduce (sqlite3.c:109734)
  ==24793==by 0x4EC4A2E: sqlite3Parser (sqlite3.c:110900)
  ==24793==by 0x4EC5896: sqlite3RunParser (sqlite3.c:111737)
  ==24793==by 0x4EA6FC2: sqlite3Prepare (sqlite3.c:94064)
  ==24793==by 0x4EA731F: sqlite3LockAndPrepare (sqlite3.c:94156)
  ==24793==by 0x4EA74B7: sqlite3_prepare (sqlite3.c:94219)
  ==24793==by 0x4EA61C6: sqlite3InitCallback (sqlite3.c:93538)
  ==24793==by 0x4EA1FDE: sqlite3_exec (sqlite3.c:90752)
  ==24793==by 0x4EA68AB: sqlite3InitOne (sqlite3.c:93784)
  ==24793==by 0x4EA6A96: sqlite3Init (sqlite3.c:93850)
  ==24793==by 0x4EA6B94: sqlite3ReadSchema (sqlite3.c:93887)
  ==24793==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==24793== 

  Based on the git clone at 
  https://github.com/mackyle/sqlite, I've bisected the first bad commit to be
  {{{
  fee0225c95052006f0776d837eeafd26b857db53 is the first bad commit
  commit fee0225c95052006f0776d837eeafd26b857db53
  Author: D. 

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

[Jarno Suni]

M G, which method you used?

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1756446] [NEW] Include JournalErrors.txt

[Brian Murray]

Public bug reported:

JournalErrors is not in the list of acceptable_fields for whoopsie, this
is a good thing given how large it can get. That being said it would be
useful (per seb128) to include a portion of JournalErrors in the crash
reports in the Error Tracker.

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


** Tags: bionic rls-bb-incoming

** Tags added: bionic rls-bb-incoming

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

Title:
  Include JournalErrors.txt

Status in whoopsie package in Ubuntu:
  New

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756446/+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 1756372] Re: Merge 2.24.32-1 from Debian

[Simon Quigley]

I can take this merge.

** Changed in: gtk+2.0 (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => In Progress

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  In Progress

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a GtkEntry control in overwrite mode rings 
t...
   772794 segfault when on unchecked XListInputDevices return value
   773587 recent-manager: Add a limit to the list's size
   776909 gtk_adjustment_clamp_page: Conditional jump or move depends on 
uninit...
   777683 SIGBUS due to gdk_x11_window_set_opacity
   778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
   778811 Enter submenus when activating their parent item
   779009 Missing property-change::accessible-description events when the 
toolt...
   779081 GtkTextView: expose API to get Pango line direction
   779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
   781020 GIMP UI vector icons are drawn way too small
   781605 GtkVolumeButton limited to 10 values
   785165 Set translation domain for parameter_string in gtk_init_with_args
   785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
   786771 Critical about mismatched GdkDisplays when opening Inspector combobox
   787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
   787195 gtk_toolbar_set_show_arrow does not show an arrow
   787410 entry: fix memory leak
   788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by 
k...

  * Translation updates:
   Hungarian
   Indonesian
   Polish
  

  gtk+2.0 (2.24.32-1) unstable; urgency=medium

* New upstream release
* debian/libgtk2.0-0.symbols: Add symbols
* Update Vcs fields for migration to https://salsa.debian.org/
* Drop patches applied in new release:
  - 0001-Don-t-use-guint32-with-XChangeProperty.patch
  - 0002-GtkMenuShell-always-activate-menu-shells.patch

   -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

  gtk+2.0 (2.24.31-5) unstable; urgency=medium

* Update Vcs fields for conversion to git
* Add debian/gbp.conf
* Bump Standards-Version to 4.1.2

   -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1756372/+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 1756438] [NEW] Merge 0.62.0-2 from Debian

[Amr Ibrahim]

Public bug reported:

Please merge poppler 0.62.0-2 from Debian. It contains packaging fixes.

poppler (0.62.0-2) unstable; urgency=medium

  * 01-new-gtk-doc.patch: patch from upstream git, fix FTBFS with new
gtk-doc-tools. Closes: #887525.
  * rules: don't hardcode CXXFLAGS when setting -g, instead append to it
so that we also get dpkg's buildflags.
  * rules: pass CFLAGS down to CMake. This should get x32 the required flags
from dpkg to build with hardening=pie. This was lost during the switch
to CMake as it doesn't use CFLAGS directly. Closes: #883881.
  * debian/tests/test-qt4.cpp: drop, the qt4 build is gone.
  * qt-visibility.diff: drop qt4 hunk.
  * control: Switch Vcs to salsa.
  * Upload to unstable.

 -- Emilio Pozuelo Monfort   Sun, 04 Mar 2018 11:37:52
+0100

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

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

Title:
  Merge 0.62.0-2 from Debian

Status in poppler package in Ubuntu:
  New

Bug description:
  Please merge poppler 0.62.0-2 from Debian. It contains packaging
  fixes.

  poppler (0.62.0-2) unstable; urgency=medium

* 01-new-gtk-doc.patch: patch from upstream git, fix FTBFS with new
  gtk-doc-tools. Closes: #887525.
* rules: don't hardcode CXXFLAGS when setting -g, instead append to it
  so that we also get dpkg's buildflags.
* rules: pass CFLAGS down to CMake. This should get x32 the required flags
  from dpkg to build with hardening=pie. This was lost during the switch
  to CMake as it doesn't use CFLAGS directly. Closes: #883881.
* debian/tests/test-qt4.cpp: drop, the qt4 build is gone.
* qt-visibility.diff: drop qt4 hunk.
* control: Switch Vcs to salsa.
* Upload to unstable.

   -- Emilio Pozuelo Monfort   Sun, 04 Mar 2018
  11:37:52 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1756438/+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 1756437] [NEW] systemd starts suspend service on startup and gets stuck...

[Michael Neuffer]

Public bug reported:

root@charion:~# systemctl status
● charion
State: starting
 Jobs: 2 queued
   Failed: 1 units
Since: Fri 2018-03-16 20:37:37 CET; 39min ago
   CGroup: /
   ├─user.slice
   │ ├─user-122.slice
   │ │ ├─user@122.service
   │ │ │ ├─pulseaudio.service
   │ │ │ │ └─2981 /usr/bin/pulseaudio --daemonize=no
   │ │ │ ├─at-spi-dbus-bus.service
[...]

root@charion:~# systemctl list-jobs
 JOB UNITTYPE  STATE  
2076 systemd-suspend.service start running
2075 suspend.target  start waiting

2 jobs listed.
root@charion:~# 

On the console is visible:
"A start job is running for Suspend" and the time it is already running.

This is while I am logged into a gdm3/Gnome session.

I've already deleted all snap packages which provided additional 
shutdown/suspend targets.
I had those under suspicion initially.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 21:22:41 2018
InstallationDate: Installed on 2018-02-28 (16 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
MachineType: Dell Inc. Precision M4800
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=UUID=d0075e29-dbce-40fe-8c81-b56b505b40b9 ro video=vesa:off vga=normal
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0PMFT3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  systemd starts suspend service on startup and gets stuck...

Status in systemd package in Ubuntu:
  New

Bug description:
  root@charion:~# systemctl status
  ● charion
  State: starting
   Jobs: 2 queued
 Failed: 1 units
  Since: Fri 2018-03-16 20:37:37 CET; 39min ago
 CGroup: /
 ├─user.slice
 │ ├─user-122.slice
 │ │ ├─user@122.service
 │ │ │ ├─pulseaudio.service
 │ │ │ │ └─2981 /usr/bin/pulseaudio --daemonize=no
 │ │ │ ├─at-spi-dbus-bus.service
  [...]

  root@charion:~# systemctl list-jobs
   JOB UNITTYPE  STATE  
  2076 systemd-suspend.service start running
  2075 suspend.target  start waiting

  2 jobs listed.
  root@charion:~# 

  On the console is visible:
  "A start job is running for Suspend" and the time it is already running.

  This is while I am logged into a gdm3/Gnome session.

  I've already deleted all snap packages which provided additional 
shutdown/suspend targets.
  I had those under suspicion initially.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 21:22:41 2018
  InstallationDate: Installed on 2018-02-28 (16 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=UUID=d0075e29-dbce-40fe-8c81-b56b505b40b9 ro video=vesa:off vga=normal
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0PMFT3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756437/+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 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

[Till Kamppeter]

Can you please activate the CUPS debug mode following the instructions
of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems and leave it
activated. As soon as the problem occurs again, please attach your
error_log to this bug report.

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

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1756336/+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 1754843] Re: gdk-pixbuf version in artful > version in bionic

[Colin Watson]

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
   gdk-pixbuf version in artful > version in bionic

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  gdk-pixbuf in artful is 2.36.11-1ubuntu0.1 which is greater than
  2.36.11-1 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1754843/+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 1754332] Re: /var/log/journal not created on fresh install of systemd

[Dimitri John Ledkov]

Bah:

Removed log directory /var/log/journal as orphaned log dir

livecd-rootfs

/me shakes fist

** Also affects: livecd-rootfs (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
   Status: Invalid

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Artful)

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

Title:
  /var/log/journal not created on fresh install of systemd

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  New
Status in livecd-rootfs source package in Artful:
  New
Status in livecd-rootfs source package in Bionic:
  Confirmed

Bug description:
  (Such as during image builds.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1754332/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Sebastian Stark]

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in libva package in Ubuntu:
  New

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :VAEntrypointVLD

[Touch-packages] [Bug 1754332] Re: /var/log/journal not created on fresh install of systemd

[Dimitri John Ledkov]

I've tried to reproduce this, and failed...

$ sudo debootstrap --include=systemd bionic bionic
...
$ ls -lnatr bionic/var/log/ | grep journal
drwxr-sr-x+  2 0 101   4096 Mar 16 18:23 journal

So fresh installation of systemd works as expected.

I guess we need to trace where/what/why certain cloud-images appear to
be lacking this

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

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  /var/log/journal not created on fresh install of systemd

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  New
Status in livecd-rootfs source package in Artful:
  New
Status in livecd-rootfs source package in Bionic:
  Confirmed

Bug description:
  (Such as during image builds.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1754332/+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 1756418] [NEW] Error detected while processing /usr/share/vim/vim80/debian.vim

[ultrabit]

Public bug reported:

Just after virsh edit domain:

 Error detected while processing /usr/share/vim/vim80/debian.vim:
line   29:
E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
line   30:
E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
line   34:
E319: Sorry, the command is not available in this version:   endfor
line   35:
E319: Sorry, the command is not available in this version:   return 0
line   36:
E319: Sorry, the command is not available in this version: endfunction
Press ENTER or type command to continue

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vim-common 2:8.0.1401-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 19:34:33 2018
InstallationDate: Installed on 2018-02-27 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
PackageArchitecture: all
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Error detected while processing /usr/share/vim/vim80/debian.vim

Status in vim package in Ubuntu:
  New

Bug description:
  Just after virsh edit domain:

   Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction
  Press ENTER or type command to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-common 2:8.0.1401-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 19:34:33 2018
  InstallationDate: Installed on 2018-02-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
  PackageArchitecture: all
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1756418/+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 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Confirmed

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  New
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.

  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify
  --w--- 1 root root 4096 Mar 16 13:50 ungroup
  -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs
  -r--r--r-- 1 root root 4096 Mar 16 13:50 state
  drwxr-xr-x 2 root root0 Mar 16 13:50 power
  -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size
  -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name
  -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid
  -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type
  -r--r--r-- 1 root root 4096 Mar 16 13:50 bridge_state
  drwxr-xr-x 2 root root0 Mar 16 13:50 blkt
  drwxr-xr-x 3 root root0 Mar 16 13:50 net

  $ echo 'encc006' | sudo tee driver/unbind 
  encc006
  tee: driver/unbind: No such device

  $ echo 'cdev0' | sudo tee driver/unbind 
  cdev0
  tee: driver/unbind: No such device

  $ echo '0.0.c006' | sudo tee driver/unbind 
  0.0.c006
  ubuntu@s1lp14:/sys/class/net/encc006/device$ Mar 16 13:52:28 s1lp14 
sudo[8046]:   ubuntu : TTY=pts/1 ; PWD=/sys/devices/qeth/0.0.c006 ; USER=root ; 
COMMAND=/usr/bin/tee driver/unbind
  Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session opened for 
user root by ubuntu(uid=0)
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to establish connection.
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time server 
91.189.89.198:123 (ntp.ubuntu.com).
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006.2653: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to establish connection.
  Mar 16 13:52:28 s1lp14 kernel: failed to kill vid 8100/2653 for device encc006
  Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session closed for 
user root
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time 

[Touch-packages] [Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

[Dimitri John Ledkov]

** Description changed:

  When trying to add another interface for a QETH device on a s390x system
  netplan apply fails:
  
  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.
  
- even if a prior test with 'netplan --debug generate' seemed to pass:
+ It seems like rebinding of qeth devices is not allowed.
+ With qeth devices, I guess one needs to "offline & online" them...
+ Or like unbind a whole group of them, as there are three of them per 
interface.
  
- sudo netplan --debug generate
- DEBUG:command generate: running ['/lib/netplan/generate']
- ** (generate:4221): DEBUG: 06:34:45.072: Processing input file 
//etc/netplan/01-netcfg.yaml..
- ** (generate:4221): DEBUG: 06:34:45.072: starting new processing pass
- ** (generate:4221): DEBUG: 06:34:45.072: encc003: setting default backend to 1
- ** (generate:4221): DEBUG: 06:34:45.072: encc000.2653: setting default 
backend to 1
- ** (generate:4221): DEBUG: 06:34:45.072: encc003.2653: setting default 
backend to 1
- ** (generate:4221): DEBUG: 06:34:45.072: encc000: setting default backend to 1
- ** (generate:4221): DEBUG: 06:34:45.072: Generating output files..
- ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition encc003 
is not for us (backend 1)
- ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition 
encc000.2653 is not for us (backend 1)
- ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition 
encc003.2653 is not for us (backend 1)
- ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition encc000 
is not for us (backend 1)
+ ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
+ total 0
+ drwxr-xr-x 5 root root0 Mar 16 02:06 ..
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
+ drwxr-xr-x 6 root root0 Mar 16 13:44 .
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
+ lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
+ lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
+ drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
+ --w--- 1 root root 4096 Mar 16 13:44 recover
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
+ lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
+ lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
+ lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc
+ -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify
+ --w--- 1 root root 4096 Mar 16 13:50 ungroup
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 state
+ drwxr-xr-x 2 root root0 Mar 16 13:50 power
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type
+ -r--r--r-- 1 root root 4096 Mar 16 13:50 bridge_state
+ drwxr-xr-x 2 root root0 Mar 16 13:50 blkt
+ drwxr-xr-x 3 root root0 Mar 16 13:50 net
  
- After this failure the QETH device is no longer online, but was online
- prior to the apply:
+ $ echo 'encc006' | sudo tee driver/unbind 
+ encc006
+ tee: driver/unbind: No such device
  
- lszdev c003
- TYPE  ID  ON  PERS  NAMES
- qeth  0.0.c003:0.0.c004:0.0.c005  no  yes
+ $ echo 'cdev0' | sudo tee driver/unbind 
+ cdev0
+ tee: driver/unbind: No such device
  
- However, after a reboot everything is fine and the interface up and
- running.
+ $ echo '0.0.c006' | sudo tee driver/unbind 
+ 0.0.c006
+ ubuntu@s1lp14:/sys/class/net/encc006/device$ Mar 16 13:52:28 s1lp14 

[Touch-packages] [Bug 1537789] Re: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source

[Andres Rodriguez]

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.

** Changed in: maas
   Status: Triaged => Won't Fix

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

Title:
  MAAS dhcp fails to start on  up-to-date Xenial with MAAS built from
  source

Status in MAAS:
  Won't Fix
Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:

  /var/log/kern.log

  Jan 25 03:54:41 autopkgtest kernel: [  598.488307] audit: type=1400
  audit(1453712081.200:20): apparmor="DENIED" operation="capable"
  profile="/usr/sbin/dhcpd" pid=13381 comm="dhcpd" capability=0
  capname="chown"

  /var/log/syslog

  Jan 25 05:21:37 autopkgtest systemd[1]: Starting MAAS instance of ISC DHCP 
server for IPv4...
  Jan 25 05:21:37 autopkgtest systemd[1]: Started MAAS instance of ISC DHCP 
server for IPv4.
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: Can't chown new lease file: 
Operation not permitted
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: 
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: If you think you have received this 
message due to a bug rather
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: than a configuration issue please 
read the section on submitting
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: bugs on either our web page at 
www.isc.org or in the README file
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: before submitting a bug.  These 
pages explain the proper
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: process and the information we find 
helpful for debugging..
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: 
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: exiting.
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Main process 
exited, code=exited, status=1/FAILURE
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Unit entered 
failed state.
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Failed with 
result 'exit-code'.

  root@autopkgtest:~# ls -l /var/lib/maas/dhcp/dhcpd.leases
  -rw-r--r-- 1 maas maas 0 Jan 25 03:54 /var/lib/maas/dhcp/dhcpd.leases

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1537789/+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 1756372] Re: Merge 2.24.32-1 from Debian

[Hans Joachim Desserud]

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a GtkEntry control in overwrite mode rings 
t...
   772794 segfault when on unchecked XListInputDevices return value
   773587 recent-manager: Add a limit to the list's size
   776909 gtk_adjustment_clamp_page: Conditional jump or move depends on 
uninit...
   777683 SIGBUS due to gdk_x11_window_set_opacity
   778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
   778811 Enter submenus when activating their parent item
   779009 Missing property-change::accessible-description events when the 
toolt...
   779081 GtkTextView: expose API to get Pango line direction
   779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
   781020 GIMP UI vector icons are drawn way too small
   781605 GtkVolumeButton limited to 10 values
   785165 Set translation domain for parameter_string in gtk_init_with_args
   785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
   786771 Critical about mismatched GdkDisplays when opening Inspector combobox
   787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
   787195 gtk_toolbar_set_show_arrow does not show an arrow
   787410 entry: fix memory leak
   788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by 
k...

  * Translation updates:
   Hungarian
   Indonesian
   Polish
  

  gtk+2.0 (2.24.32-1) unstable; urgency=medium

* New upstream release
* debian/libgtk2.0-0.symbols: Add symbols
* Update Vcs fields for migration to https://salsa.debian.org/
* Drop patches applied in new release:
  - 0001-Don-t-use-guint32-with-XChangeProperty.patch
  - 0002-GtkMenuShell-always-activate-menu-shells.patch

   -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

  gtk+2.0 (2.24.31-5) unstable; urgency=medium

* Update Vcs fields for conversion to git
* Add debian/gbp.conf
* Bump Standards-Version to 4.1.2

   -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1756372/+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 1725749] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Till Kamppeter]

Reported upstream as

https://github.com/apple/cups/issues/5268

** Bug watch added: github.com/apple/cups/issues #5268
   https://github.com/apple/cups/issues/5268

** Also affects: cups via
   https://github.com/apple/cups/issues/5268
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  crashed immediately after starting LUbuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Oct 19 21:56:40 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HEWLETT-PACKARD-DESKJET-990C: parallel:/dev/lp0
   device for HP-LaserJet-5: socket://192.168.22.65:9100
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles:
   HEWLETT-PACKARD-DESKJET-990C: HP Deskjet 990c, hpcups 3.17.7
   PDF: Generic CUPS-PDF Printer
   HP-LaserJet-5: HP LaserJet 5 - CUPS+Gutenprint v5.2.13
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug 
drm.debug=0xe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug 
drm.debug=0xe
  SegvAnalysis:
   Segfault happened at: 0x7f57d0318954 : cmpq   
$0x0,(%rdi)
   PC (0x7f57d0318954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1725749/+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 1755192] Re: Running add-apt-repository inside docker bionic container gives No such file or directory: 'S.gpg-agent.browser'

[Brian Murray]

** Tags added: bionic rls-bb-incoming

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

Title:
  Running add-apt-repository inside docker bionic container gives No
  such file or directory: 'S.gpg-agent.browser'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This used to work for Ubuntu 14.04 and 16.04.

  ```
  Step 5/7 : RUN add-apt-repository -y ppa:kernsuite/kern-dev
   ---> Running in 4d6412c3d237
  gpg: keybox '/tmp/tmpol6z8f79/pubring.gpg' created
  gpg: /tmp/tmpol6z8f79/trustdb.gpg: trustdb created
  gpg: key 813B0DC8B7D042E7: public key "Launchpad PPA for KERN suite" imported
  gpg: Total number processed: 1
  gpg:   imported: 1
  Warning: apt-key output should not be parsed (stdout is not a terminal)
  OK
  [Errno 2] No such file or directory: 'S.gpg-agent.browser'
  ```

  Dockerfile:

  ```
  FROM ubuntu:18.04
  MAINTAINER gijsmolen...@gmail.com
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y ppa:kernsuite/kern-dev
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1755192/+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 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

[Till Kamppeter]

Reported upstream as

https://github.com/apple/cups/issues/5267

** Bug watch added: github.com/apple/cups/issues #5267
   https://github.com/apple/cups/issues/5267

** Also affects: cups via
   https://github.com/apple/cups/issues/5267
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1756160/+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 1756324] Re: No signal after upgrading on 18.04

[Brian Murray]

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

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

Title:
  No signal after upgrading on 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
  the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
  just boots to nothing, my screen display "No signal detected",
  although I can hear the drum sound. Using nomodeset works but my
  computer is set at a wrong frequency (stuck to 77Hz, even forcing via
  xrandr doesn't work). So using nomodeset  I got into i3, downloaded
  mesa drivers and tried radeon too, and rebooted. Now still shows no
  signal, but I can get into a fluent 60Hz i3, if I go to recovery mode,
  then press normal boot. The problem also with that is that GNOME
  doesn't work, when I leave i3, log onto GNOME, it shows a blackscreen
  and just sends me back to the login menu. I've noticed this error
  appeared at boot: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

  Here's xrandr output: xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  0.00* 
 1280x1024  0.00  
 1024x768   0.00  
 800x6000.00  
 640x4800.00  

  
  Thanks for any future help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756324/+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 1756389] Re: Delay startup of evolution-calendar-factory

[Jean-Baptiste Lallement]

bootchart with ev-cal-factory delayed by 1 minute.

** Attachment added: "bootchart_evcal_delayed-60s.png"
   
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+attachment/5081630/+files/bootchart_evcal_delayed-60s.png

** Tags added: rls-bb-incoming

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

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+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 1756389] [NEW] Delay startup of evolution-calendar-factory

[Jean-Baptiste Lallement]

Public bug reported:

On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

evolution-calendar-factory startup should be delayed if it cannot be
disabled completely.

The following changes to evolution-calendar-factory.service do this:
""" 
[Unit]
Description=Evolution calendar service

[Service]
Type=dbus
BusName=org.gnome.evolution.dataserver.Calendar7
ExecStartPre=/bin/sleep 60
ExecStart=/usr/lib/evolution/evolution-calendar-factory
"""

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.28.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 17:52:45 2018
InstallationDate: Installed on 2013-09-03 (1654 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution-data-server
UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic rls-bb-incoming

** Attachment added: "bootchart_nodelay.png"
   
https://bugs.launchpad.net/bugs/1756389/+attachment/5081626/+files/bootchart_nodelay.png

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

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+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 1756324] [NEW] No signal after upgrading on 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
just boots to nothing, my screen display "No signal detected", although
I can hear the drum sound. Using nomodeset works but my computer is set
at a wrong frequency (stuck to 77Hz, even forcing via xrandr doesn't
work). So using nomodeset  I got into i3, downloaded mesa drivers and
tried radeon too, and rebooted. Now still shows no signal, but I can get
into a fluent 60Hz i3, if I go to recovery mode, then press normal boot.
The problem also with that is that GNOME doesn't work, when I leave i3,
log onto GNOME, it shows a blackscreen and just sends me back to the
login menu. I've noticed this error appeared at boot: [drm:amdgpu_init
[amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

Here's xrandr output: xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080  0.00* 
   1280x1024  0.00  
   1024x768   0.00  
   800x6000.00  
   640x4800.00  


Thanks for any future help!

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


** Tags: bot-comment
-- 
No signal after upgrading on 18.04
https://bugs.launchpad.net/bugs/1756324
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

Today the fuzzy screen depicted in the attachment appears spontaneously
while using google maps.  This time with a block around the pointer,
that continued to move with the pointer.

** Attachment added: "IMG_20180316_172748_697.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5081615/+files/IMG_20180316_172748_697.jpg

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752145/+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 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

[Till Kamppeter]

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in cups package in Ubuntu:
  New

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1756160/+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 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

[Till Kamppeter]

Reported upstream as

https://github.com/apple/cups/issues/5266

** Bug watch added: github.com/apple/cups/issues #5266
   https://github.com/apple/cups/issues/5266

** Also affects: cups via
   https://github.com/apple/cups/issues/5266
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1756336/+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 1756377] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1710498, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081574/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081577/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081584/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081586/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081587/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081588/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756377/+attachment/5081589/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1710498

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 15 23:42:55 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-03-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20KGS05000
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=21b93eca-f635-4b59-b2e1-7b6a13fbe0d7 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so
   close_nointr () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS05000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET37W(1.12):bd02/27/2018:svnLENOVO:pn20KGS05000:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS05000
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756377/+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 1756375] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1710498, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081550/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081553/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081559/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081561/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081562/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081563/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756375/+attachment/5081565/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1710498

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  on login

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Mar 16 16:37:24 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-02-21 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:0671 Acer, Inc 
   Bus 001 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80M1
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=7c316ffa-779d-4eda-a8d6-f7a20492e6bb ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so
   close_nointr () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: Upgraded to bionic on 2018-02-23 (21 days ago)
  UserGroups:
   
  dmi.bios.date: 08/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C7CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 300-11IBR
  dmi.modalias: 
dmi:bvnLENOVO:bvrC7CN31WW:bd08/05/2016:svnLENOVO:pn80M1:pvrLenovoYoga300-11IBR:rvnLENOVO:rnMini:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoYoga300-11IBR:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M1
  dmi.product.version: Lenovo Yoga 300-11IBR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756375/+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 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

[Till Kamppeter]

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1756336/+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 1756372] [NEW] Merge 2.24.32-1 from Debian

[Amr Ibrahim]

Public bug reported:

Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

Overview of Changes from GTK+ 2.24.31 to 2.24.32


* Build:
 - Support Visual Studio 2017

* Bug fixes:
 136059 Ctrl-navigation works in opposite direction in right-to-left text
 165385 Win32 keyboard handling still incomplete
 358970 gtk_scale_set_digits does not cause value to be rounded if draw-value...
 468868 Popup of "appears-as-list" ComboBox does not change screen with its t...
 554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs (a...
 569581 Using the US-Intl keyboard layout causes unexpected character combina...
 618160 Documentation for gtk_combo_box_get_active_iter is unclear
 658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
 676550 Adding underlines to Label with gtk_label_set_pattern() does not work
 696624 Japanese (Korean/Chinese) XIM input mode indicator has not been worki...
 701296 gtkfixed accepts toplevel windows into its children list after gtk_wi...
 729651 Crash in GtkFileChooserButton with appears-as-list
 734946 Implement GContentType on OSX
 768722 Keyboard shortcuts for russian characters doesn't work
 769214 keyval field not filled correctly for Pause key
 772389 Appending a character to a GtkEntry control in overwrite mode rings t...
 772794 segfault when on unchecked XListInputDevices return value
 773587 recent-manager: Add a limit to the list's size
 776909 gtk_adjustment_clamp_page: Conditional jump or move depends on uninit...
 777683 SIGBUS due to gdk_x11_window_set_opacity
 778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
 778811 Enter submenus when activating their parent item
 779009 Missing property-change::accessible-description events when the toolt...
 779081 GtkTextView: expose API to get Pango line direction
 779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
 781020 GIMP UI vector icons are drawn way too small
 781605 GtkVolumeButton limited to 10 values
 785165 Set translation domain for parameter_string in gtk_init_with_args
 785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
 786771 Critical about mismatched GdkDisplays when opening Inspector combobox
 787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
 787195 gtk_toolbar_set_show_arrow does not show an arrow
 787410 entry: fix memory leak
 788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by k...

* Translation updates:
 Hungarian
 Indonesian
 Polish


gtk+2.0 (2.24.32-1) unstable; urgency=medium

  * New upstream release
  * debian/libgtk2.0-0.symbols: Add symbols
  * Update Vcs fields for migration to https://salsa.debian.org/
  * Drop patches applied in new release:
- 0001-Don-t-use-guint32-with-XChangeProperty.patch
- 0002-GtkMenuShell-always-activate-menu-shells.patch

 -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

gtk+2.0 (2.24.31-5) unstable; urgency=medium

  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump Standards-Version to 4.1.2

 -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a 

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Pioterus]

Almost year old bug still there. This is core functionality of any OS
(secure VPNs, DNS) which just does not work on Ubuntu. I don't know how
about other distros but I doubt that Ubuntu can claim to be the desktop
system with such a bug.

I can confirm that the simplest workaround is comment out dnsmasq in 
NetworkManager config (ubuntu 16.04). But there are drawbacks of course so this 
makes the system less secure/reliable  in some situations. And of course it 
took me about 5 hours to figure out what is going on. Those hours could be 
spend more productive.
P.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1756364] Re: [ffe] Livepatch integration

[Sebastien Bacher]

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

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

Title:
  [ffe] Livepatch integration

Status in software-properties package in Ubuntu:
  New

Bug description:
  One feature we want to add to the desktop for the LTS is to allow
  users to enable livepatch from the desktop.

  The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
  
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

  That's based on the gnome-online-account ubuntu sso provider which has
  been added to bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1756364/+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 1756364] [NEW] [ffe] Livepatch integration

[Sebastien Bacher]

Public bug reported:

One feature we want to add to the desktop for the LTS is to allow users
to enable livepatch from the desktop.

The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

That's based on the gnome-online-account ubuntu sso provider which has
been added to bionic.

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

** Branch linked: lp:~azzar1/software-properties/add-canonical-livepatch

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

Title:
  [ffe] Livepatch integration

Status in software-properties package in Ubuntu:
  New

Bug description:
  One feature we want to add to the desktop for the LTS is to allow
  users to enable livepatch from the desktop.

  The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
  
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

  That's based on the gnome-online-account ubuntu sso provider which has
  been added to bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1756364/+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 1755719] Re: Please sync qt5-default from debian experimental

[Simon Quigley]

5.9.5 has not been released yet, but the plan is to go to it once that
happens.

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

Title:
  Please sync qt5-default from debian experimental

Status in qtbase-opensource-src package in Ubuntu:
  Opinion

Bug description:
  I mean of course please sync all qt5 packages to the version of
  experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1755719/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Scott Moser]

See my attached log for verification of artful.

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Scott Moser]

** Attachment added: "verification log on artful"
   
https://bugs.launchpad.net/cloud-init/+bug/1734167/+attachment/5081507/+files/lp-1734167-verify-artful.txt

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

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1755719] Re: Please sync qt5-default from debian experimental

[Mirko W]

version 5.9.5 (current version in Ubuntu 18.04 is 5.9.4) would also help
since it also contains an important bug-fix for everyone who uses
textures with Qt3D (https://bugreports.qt.io/browse/QTBUG-64133)

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

Title:
  Please sync qt5-default from debian experimental

Status in qtbase-opensource-src package in Ubuntu:
  Opinion

Bug description:
  I mean of course please sync all qt5 packages to the version of
  experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1755719/+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 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

[Dimitri John Ledkov]

Ok, reading more carefully it looks like udevadm is failing, when called
by netplan.

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

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  even if a prior test with 'netplan --debug generate' seemed to pass:

  sudo netplan --debug generate
  DEBUG:command generate: running ['/lib/netplan/generate']
  ** (generate:4221): DEBUG: 06:34:45.072: Processing input file 
//etc/netplan/01-netcfg.yaml..
  ** (generate:4221): DEBUG: 06:34:45.072: starting new processing pass
  ** (generate:4221): DEBUG: 06:34:45.072: encc003: setting default backend to 1
  ** (generate:4221): DEBUG: 06:34:45.072: encc000.2653: setting default 
backend to 1
  ** (generate:4221): DEBUG: 06:34:45.072: encc003.2653: setting default 
backend to 1
  ** (generate:4221): DEBUG: 06:34:45.072: encc000: setting default backend to 1
  ** (generate:4221): DEBUG: 06:34:45.072: Generating output files..
  ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition encc003 
is not for us (backend 1)
  ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition 
encc000.2653 is not for us (backend 1)
  ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition 
encc003.2653 is not for us (backend 1)
  ** (generate:4221): DEBUG: 06:34:45.072: NetworkManager: definition encc000 
is not for us (backend 1)

  After this failure the QETH device is no longer online, but was online
  prior to the apply:

  lszdev c003
  TYPE  ID  ON  PERS  NAMES
  qeth  0.0.c003:0.0.c004:0.0.c005  no  yes

  However, after a reboot everything is fine and the interface up and
  running.

  Detailed steps (also to reproduce) are attached as well as the syslog.
  System is left as it is and can be used for further testing ...
  (contact 'jfh' on IRC)

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1756322/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

@sil2100 pymacaroons packages works fine. But can you please take care
of the other ones too. They've been waiting in the queue for quite some
time.

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1755192] Re: Running add-apt-repository inside docker bionic container gives No such file or directory: 'S.gpg-agent.browser'

[Launchpad Bug Tracker]

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

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

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

Title:
  Running add-apt-repository inside docker bionic container gives No
  such file or directory: 'S.gpg-agent.browser'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This used to work for Ubuntu 14.04 and 16.04.

  ```
  Step 5/7 : RUN add-apt-repository -y ppa:kernsuite/kern-dev
   ---> Running in 4d6412c3d237
  gpg: keybox '/tmp/tmpol6z8f79/pubring.gpg' created
  gpg: /tmp/tmpol6z8f79/trustdb.gpg: trustdb created
  gpg: key 813B0DC8B7D042E7: public key "Launchpad PPA for KERN suite" imported
  gpg: Total number processed: 1
  gpg:   imported: 1
  Warning: apt-key output should not be parsed (stdout is not a terminal)
  OK
  [Errno 2] No such file or directory: 'S.gpg-agent.browser'
  ```

  Dockerfile:

  ```
  FROM ubuntu:18.04
  MAINTAINER gijsmolen...@gmail.com
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y ppa:kernsuite/kern-dev
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1755192/+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 1755232] Re: Xorg crashes when tapping Unity system tray icons

[Jean-Noël AVILA]

Maybe something similar to what I experience. See
https://bugs.freedesktop.org/show_bug.cgi?id=105557

** Bug watch added: freedesktop.org Bugzilla #105557
   https://bugs.freedesktop.org/show_bug.cgi?id=105557

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

Title:
  Xorg crashes when tapping Unity system tray icons

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug requires some prerequisites to reproduce:

  0. Make sure you've got multitouch-enable display
  1. Start Unity+xorg session
  2. Verify that four-finger tap gesture works (shows unity app search tool)
  3. Wait some time for this gesture to stop working - this is another bug, not 
necessarily xorg one,  already known and thought to be connected with Google 
Chrome running.
  4. Once it stops working, quickly tap all icons in the Unity system tray like 
you would be pretending to play a piano (tapping them individually or slowly 
does not cause any problems).
  5. Xorg crashes immediately.

  This scenario is 100% reproducible on my setup.

  I recompiled xorg with debug info enabled and got this nice trace:

  
  [ 22705.385] (EE) 
  [ 22705.385] (EE) Backtrace: 
  [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f]  
   
  [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) 
[0x7f382f64414f]   
  [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f382f2880bb] 
  [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) 
[0x7f382f289f5d]  
  [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) 
[0x7f382f2d22bd]  
  [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) 
[0x7f382f2d9f7a]
  [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) 
[0x7f382f2de0fe]   
  [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) 
[0x7f382f2e044e]   
  [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32]
  [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) 
[0x562a3698428f]   
  [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) 
[0x562a3698ea8b]   
  [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) 
[0x562a369bc371]  
  [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] 
   
  [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) 
[0x562a3696e488] 
  [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9]
  [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3]
   
  [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] 
   
  [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7f382f2721c1]  
  [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a]   
   
  [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] 


  Looks like FreeGrab tries to free pGrab for the second time (some
  multithreading issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 12 17:03:34 2018
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2017-09-01 (192 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HES2130Q
  ProcEnviron:
   LANGUAGE=pl_PL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y 
acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 
i915.enable_guc_submission=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to artful on 2018-02-11 (29 days ago)
  dmi.bios.date: 05/23/2017
  

[Touch-packages] [Bug 1605861] Re: apt-key output should not be parsed (stdout is not a terminal)

[dino99]

Yakkety is now unsupported, and that issue is no more seen with recent
releases.

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

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

Title:
   apt-key output should not be parsed (stdout is not a terminal)

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  Got that warning logged after registering two ppas and updating them:

  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmp58u008j4/secring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmp58u008j4/pubring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: requesting key F59EAE4D from hkp 
server keyserver.ubuntu.com
  com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmp58u008j4/trustdb.gpg: 
trustdb created
  com.ubuntu.SoftwareProperties[2113]: gpg: key F59EAE4D: public key "Launchpad 
PPA for NoobsLab" imported
  com.ubuntu.SoftwareProperties[2113]: gpg: no ultimately trusted keys found
  com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1
  com.ubuntu.SoftwareProperties[2113]: gpg:   imported: 1  (RSA: 1)
  com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be 
parsed (stdout is not a terminal)
  com.ubuntu.SoftwareProperties[2113]: OK
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmpjwlat63e/secring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmpjwlat63e/pubring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: requesting key E2D0EBE9 from hkp 
server keyserver.ubuntu.com
  com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmpjwlat63e/trustdb.gpg: 
trustdb created
  com.ubuntu.SoftwareProperties[2113]: gpg: key E2D0EBE9: public key "Launchpad 
PPA for RAVEfinity Project" imported
  com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1
  com.ubuntu.SoftwareProperties[2113]: gpg:   imported: 1  (RSA: 1)
  com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be 
parsed (stdout is not a terminal)
  com.ubuntu.SoftwareProperties[2113]: OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.6.0-9.11-generic 4.6.4
  Uname: Linux 4.6.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jul 23 13:37:35 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1605861/+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 1662137] Re: 16.04 recovery shell works only for two minutes

[Francis Ginther]

** Tags added: id-5aaa925072882f79f72239f6

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

Title:
  16.04 recovery shell works only for two minutes

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

Bug description:
  Selecting "Rescue" shell from the "Advanced options" menu in grub
  enters the "friendly-recovery" service and allows to drop into a root
  shell.  After ~120 seconds, systemd sees a timeout and starts another
  "friendly-recovery" whiptail process.  This and the running shell now
  compete for tty access (input and output) thus making the shell nearly
  unusable.

  Diagnosing this, it becomes clear that in the first root shell entered
  from friendly-recovery, "systemctl list-jobs" lists the generated
  "wait for disk" tasks for the /boot partition and the swap partition
  still to be running.  Only when they run into a timeout, the next
  friendly-recovery is spawned.  I'll attach a log session for such a
  boot that has two manual "logger" entries in it:

  Feb 06 10:54:57 harry root[605]: now in root shell from friendly-recovery
  ...
  Feb 06 10:56:41 harry root[1254]: now running in parallel

  This clearly shows the timing of the startup.

  I have no idea why the "wait for disk" units run into a timeout as the
  system boots correctly in the "non-rescue" mode.  I'll further attach
  a "systemd-analyze blame" from a regular bootup to show that there is
  no trace of such a timeout to be found.

  Furthermore i do have this behaviour on a real machine and on an
  (independent) VM, so affects more than the machine the bug was
  reported from.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  6 11:02:37 2017
  InstallationDate: Installed on 2015-03-27 (681 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 
loop.max_part=63 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-12-01 (66 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: 617H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+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 1756312] Re: found by xdiagnose

[JÁNOS]

web cam doesn't work at all, google hangout videochat doesn't work too,cheese 
and GTK UVC program are crashing with my webcam.
camera driver Sunplus 561 A is good under windows xp.

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

Title:
  found by xdiagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 16 12:23:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   microdia, 2009.01: added
   v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed
   v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed
   virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed
   virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
  InstallationDate: Installed on 2018-02-28 (15 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: FUJITSU SIEMENS GA-K8RS482M
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-K8RS482M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr:
  dmi.product.name: GA-K8RS482M
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar 16 12:13:35 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756312/+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 1756312] [NEW] found by xdiagnose

[JÁNOS]

Public bug reported:

ubuntu 16.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Mar 16 12:23:55 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 microdia, 2009.01: added
 v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed
 v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed
 virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed
 virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
InstallationDate: Installed on 2018-02-28 (15 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: FUJITSU SIEMENS GA-K8RS482M
ProcEnviron:
 LANGUAGE=hu
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: GA-K8RS482M
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr:
dmi.product.name: GA-K8RS482M
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Mar 16 12:13:35 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  found by xdiagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 16 12:23:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   microdia, 2009.01: added
   v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed
   v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed
   virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed
   virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
  InstallationDate: Installed on 2018-02-28 (15 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: FUJITSU SIEMENS GA-K8RS482M
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option

[Wladimir Mutel]

I reported the same problem with more details at 
https://bugs.launchpad.net/initramfs-tools/+bug/1651170
But I am not sure that anyone is reading initramfs-tools bug reports ever.
I don't like that my initrd*.img is about 50 MB large, but who else cares, the 
storage is cheap and fast now.

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

Title:
  initramfs-tools ignores the FRAMEBUFFER option

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  initramfs-tools ignores the FRAMEBUFFER option. This means that the
  framebuffer hook will always include the drm modules, regardless of
  whether it is dealing with an encrypted system or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 24 18:06:24 2016
  InstallationDate: Installed on 2016-02-16 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
  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/1561643/+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 1651170] Re: run_scripts_optional sets 'y' value but call_scripts checks for 'optional' value

[Wladimir Mutel]

Is this misbehaviour going to be perpetuated into Ubuntu Bionic 18.04 ?

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

Title:
  run_scripts_optional sets 'y' value but call_scripts checks for
  'optional' value

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I looked into my initramfs and found there big graphics modules for hardware 
which I don't have. 
  I found a place where these modules were copied into initramfs, it was in 
/usr/share/initramfs-tools/hooks/framebuffer
  Also I found a recipe on the Internet, advising to put 'FRAMEBUFFER=n' into 
initramfs.conf to exclude optional hooks and scipts which have 
OPTION=FRAMEBUFFER in them from initramfs creation
  I tried to set this option and to update my initramfs, but did not succeed
  So I examined mkinitramfs and related scripts and found this sequence in 
/usr/share/initramfs-tools/hook-functions :

  run_scripts_optional()
  {
  call_scripts_optional=y
  run_scripts "$@"
  }
  ...
  run_scripts()
  {
  ...
  call_scripts $scriptdir
  }
  ...
  call_scripts()
  {
  ...
  for cs_x in ${runlist}; do
  ...
  if [ x"$call_scripts_optional" = "xoptional" ]; then
  option=$(sed 
'/^OPTION=/!d;$d;s/^OPTION=//;s/[[:space:]]*$//' "${initdir}/${cs_x}")
  [ -z "${option}" ] || eval test -n \"\${$option}\" -a 
\"\${$option}\" != \"n\" || continue
  fi
  ...
  done
  ...
  }

  As you see, variable 'call_scripts_optional' is set to vaue 'y' in
  run_scripts_optional function, but then it is checked for having
  'optional' value in call_scripts function

  This is observed at least in up-to-date Ubuntu Xenial and Zesty
  I will also check equivalent scripts in Debian testing/unstable and report my 
finding in a comment below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1651170/+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 1756307] Re: package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I am not familiar with this!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Mar 16 16:26:54 2018
  DuplicateSignature: package:python3:3.4.0-0ubuntu2:subprocess installed 
pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2018-03-09 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python3-defaults
  Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1756307/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Łukasz Zemczak]

@azzar1 You marked this bug as verification-failed-artful - does it mean
the pymacaroons package is broken? Usually when a package is marked as
-failed it is a sign for the SRU/AA team to remove the package from
-proposed - is this the case here? Your comment implies as if we're just
waiting for another part of the fix instead.

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1756307] [NEW] package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[rajat]

Public bug reported:

I am not familiar with this!

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-80-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Fri Mar 16 16:26:54 2018
DuplicateSignature: package:python3:3.4.0-0ubuntu2:subprocess installed 
pre-removal script returned error exit status 127
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
InstallationDate: Installed on 2018-03-09 (7 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python3-defaults
Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I am not familiar with this!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Mar 16 16:26:54 2018
  DuplicateSignature: package:python3:3.4.0-0ubuntu2:subprocess installed 
pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2018-03-09 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python3-defaults
  Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1756307/+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 1756198] Re: Intermittent HDMI sound, working with some videos/audios, failing with others

[JP S]

Adding the package info.

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

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

Title:
  Intermittent HDMI sound, working with some videos/audios, failing with
  others

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using Lubuntu 17.10 on an ACER REVO RL80 connected to my TV
  through HDMI.

  The sound output is configured via sound settings (pavucontrol) to
  HDMI ouput.

  The sound is OK with some apps, and KO with some others.

  For example in VLC, it works usually fine.
  But on chromium/youtube, the sound is HS.
  Actually, i think it's not really a per app problem, but it might depend more 
on the type of audio being played. I thought the audio was working fine on 
firefox youtube at first, but once I ran into a specific video with the audio 
HS (and I checked this video had sound). 

  When the audio is HS on a video play, if I start a video that usually
  doesn't have the problem, this video has the audio HS too.

  And reversely, if the audio is OK on a video, and if I start a video
  that usually have the problem, this time the video has its audio OK.

  Knowing this, I made a small sript to "fix" the audio of a video witht
  he problem.

  I pause the video with the audio problem, I start a sound hat usually
  doesn't have the problem, and I change the audio output back and forth
  to HDMI output again. It usually fixes audio, and I jsute need to
  resume the video with the problem BEFORE the good audio is over, and
  it's OK.

  This is my script

  mpv /path/to/whitenoise_48k.wav &
  pacmd set-card-profile 0 output:analog-stereo
  pacmd set-card-profile 0 output:hdmi-stereo

  And it's interesting to note that the same sound in 44k doesn't work
  (whitenoise_44k.wav).

  Weird stuff...

  These are the outputs of some commands, can make more if you want.

  aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 1: ALC662 rev3 Digital [ALC662 rev3 
Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0


  
  lspci -v
  00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller (rev 04)
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family High 
Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at f7e3 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel


  
  pacmd list-cards
  1 card(s) available.
  index: 0
name: 
driver: 
owner module: 22
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7e3 irq 30"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C216 Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 60, 
available: no)
output:analog-stereo: Analog Stereo Output (priority 6000, 
available: no)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(priority 6060, available: no)
output:iec958-stereo: Digital Stereo (IEC958) Output (priority 
5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (priority 5560, available: unknown)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5400, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) 
Output + Analog Stereo Input (priority 5460, available: unknown)
off: Off (priority 0, available: unknown)
active profile: 
sinks:
alsa_output.pci-_00_1b.0.hdmi-stereo/#5: Built-in Audio 
Digital Stereo (HDMI)
sources:

[Touch-packages] [Bug 1756031] Re: openssh-server doesn't accept aes256-cbc key

[ChristianEhrhardt]

AFAIK build time:
  sshkey.h:49:#define SSH_RSA_MINIMUM_MODULUS_SIZE1024

And those short keys are really considered insecure, which is the reason
they went from deprecated to no more accepted.

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

Title:
  openssh-server doesn't accept aes256-cbc key

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I am using putty connection with RSA key cached in pageant and want to
  login without password.

  Private key on windows:
  PuTTY-User-Key-File-2: ssh-rsa
  Encryption: aes256-cbc
  ...

  On ubuntu there is public key in .ssh/authorized_keys
  ssh-rsa B3Nz...JBjQ== palo@winpgnotas

  This key works well in ubuntu versions 14.04...17.10
  When I tried 18.04 beta, I am getting sshd error:
  mar 15 10:26:21 ubox sshd[5205]: error: userauth_pubkey: could not parse key: 
Invalid key length [preauth]
  and I have to provide password.

  I've found that aes256-cbc is not in the list of allowed ciphers by default, 
so I added
  Ciphers +aes256-cbc
  to /etc/ssh/sshd_config
  (and verified with nmap --script ssh2-enum-algos -sV -p 22 127.0.0.1)
  but the sshd error remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 15 10:03:14 2018
  InstallationDate: Installed on 2018-03-12 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1756031/+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 1756198] [NEW] Intermittent HDMI sound, working with some videos/audios, failing with others

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using Lubuntu 17.10 on an ACER REVO RL80 connected to my TV through
HDMI.

The sound output is configured via sound settings (pavucontrol) to HDMI
ouput.

The sound is OK with some apps, and KO with some others.

For example in VLC, it works usually fine.
But on chromium/youtube, the sound is HS.
Actually, i think it's not really a per app problem, but it might depend more 
on the type of audio being played. I thought the audio was working fine on 
firefox youtube at first, but once I ran into a specific video with the audio 
HS (and I checked this video had sound). 

When the audio is HS on a video play, if I start a video that usually
doesn't have the problem, this video has the audio HS too.

And reversely, if the audio is OK on a video, and if I start a video
that usually have the problem, this time the video has its audio OK.

Knowing this, I made a small sript to "fix" the audio of a video witht
he problem.

I pause the video with the audio problem, I start a sound hat usually
doesn't have the problem, and I change the audio output back and forth
to HDMI output again. It usually fixes audio, and I jsute need to resume
the video with the problem BEFORE the good audio is over, and it's OK.

This is my script

mpv /path/to/whitenoise_48k.wav &
pacmd set-card-profile 0 output:analog-stereo
pacmd set-card-profile 0 output:hdmi-stereo

And it's interesting to note that the same sound in 44k doesn't work
(whitenoise_44k.wav).

Weird stuff...

These are the outputs of some commands, can make more if you want.

aplay --list-devices
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC662 rev3 Digital [ALC662 rev3 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0



lspci -v
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller (rev 04)
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family High 
Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at f7e3 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel



pacmd list-cards
1 card(s) available.
index: 0
name: 
driver: 
owner module: 22
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7e3 irq 30"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C216 Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 60, 
available: no)
output:analog-stereo: Analog Stereo Output (priority 6000, 
available: no)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(priority 6060, available: no)
output:iec958-stereo: Digital Stereo (IEC958) Output (priority 
5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (priority 5560, available: unknown)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5400, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) 
Output + Analog Stereo Input (priority 5460, available: unknown)
off: Off (priority 0, available: unknown)
active profile: 
sinks:
alsa_output.pci-_00_1b.0.hdmi-stereo/#5: Built-in Audio 
Digital Stereo (HDMI)
sources:
alsa_output.pci-_00_1b.0.hdmi-stereo.monitor/#5: Monitor of 
Built-in Audio Digital Stereo (HDMI)
ports:
analog-input-mic: Microphone (priority 8700, latency offset 0 
usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: no)
properties:

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Roman Dinga]

Is there an open bug for discrete GPU switch not working? Or should I
open a new one?

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

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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Daniel van Vugt]

Fix (with the new bug ID) for mutter.

** Patch removed: "mutter_3.28.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+attachment/5080004/+files/mutter_3.28.0-1ubuntu1.debdiff

** Patch added: "mutter_3.28.0-1ubuntu1_attempt2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+attachment/5081081/+files/mutter_3.28.0-1ubuntu1_attempt2.debdiff

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1733032] Re: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed)

[Daniel van Vugt]

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

All work is now being done in bug 1686081.

** Patch removed: "mutter_3.28.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1733032/+attachment/5078941/+files/mutter_3.28.0-1ubuntu1.debdiff

** Patch removed: "gnome-control-center_3.27.92-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1733032/+attachment/5079021/+files/gnome-control-center_3.27.92-1ubuntu2.debdiff

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

Title:
  Touchpad settings don't work after upgrading to 17.10 (because
  xserver-xorg-input-synaptics is still installed)

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Since upgrading to 17.10, my mouse pointer is repeatedly and
  frequently getting moved against my will when I am typing on my laptop
  keyboard (as opposed to external keyboard) because my hand brushes
  against the touchpad or even just near its surface.

  Furthermore, I don't want tap-to-click to be enabled. I want to
  actually have to push down on the mousepad hard enough to click it to
  generate a mouse button event. I can't figure out how to disable tap-
  to-click in 17.10 either.

  I did not have these problems _at all_ in 17.04.

  I have the touchpad click method set to "Areas" and "Disable While
  Typing" enabled in gnome-tweak-tool. This does not help.

  I have these lines in the touchpad section of
  /usr/share/X11/xorg.conf.d/40-libinput.conf as well:

  Option "DisableWhileTyping" "true"
  Option "PalmDetection" "true"
  Option "Tapping" "false"

  They don't help either.

  This is a substantial regression in functionality from 17.04.

  It appears to be a problem using both Wayland and Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 21:28:05 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (182 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733032/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Daniel van Vugt]

Fix (v2) for gnome-control-center.

This includes a workaround for gdk so we're not waiting for that fix.
This does however depend on the mutter fix being present.

** Patch added: "gnome-control-center_3.27.92-1ubuntu2_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+attachment/5081079/+files/gnome-control-center_3.27.92-1ubuntu2_v2.debdiff

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1755144] Re: No audio on vlc or videos sound or video files

[John Rose]

Done the downgrade (all.txt attached showing downgrade 3.7 successful.
Tried vlc with mp3 files again and still doesn't work.

** Attachment added: "all.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+attachment/5081080/+files/all.txt

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

Just the subset you have installed right now need downgrading:

ii  pulseaudio1:8.0-0ubuntu3.8  
amd64PulseAudio sound server
ii  pulseaudio-module-bluetooth   1:8.0-0ubuntu3.8  
amd64Bluetooth module for PulseAudio 
sound server
ii  pulseaudio-module-x11 1:8.0-0ubuntu3.8  
amd64X11 module for PulseAudio sound 
server
ii  pulseaudio-utils  1:8.0-0ubuntu3.8  
amd64Command line tools for the 
PulseAudio sound server
ii  libpulse-dev:amd641:8.0-0ubuntu3.8  
amd64PulseAudio client development 
headers and libraries
ii  libpulse-mainloop-glib0:amd64 1:8.0-0ubuntu3.8  
amd64PulseAudio client libraries (glib 
support)
ii  libpulse0:amd64   1:8.0-0ubuntu3.8  
amd64PulseAudio client libraries
ii  libpulsedsp:amd64 1:8.0-0ubuntu3.8  
amd64PulseAudio OSS pre-load library

Which means my list in comment #2 was wrong, sorry.

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1605861] Re: apt-key output should not be parsed (stdout is not a terminal)

[era]

apt-key was changed in Debian Stretch to warn when you attempt to do
something like

apt-key add /dev/null

or the equivalent pipeline.  The manual page says

COMMANDS
   add filename
(...)
   Note: Instead of using this command a keyring should be placed
directly in the /etc/apt/trusted.gpg.d/ directory with a descriptive name
and either "gpg" or "asc" as file extension.

So, the right thing to do is to copy the file to the right path instead of
calling apt-key add with it.

^ I got the above snippet from the very tangentially related
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774

** Bug watch added: Debian Bug tracker #851774
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774

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

Title:
   apt-key output should not be parsed (stdout is not a terminal)

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Got that warning logged after registering two ppas and updating them:

  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmp58u008j4/secring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmp58u008j4/pubring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: requesting key F59EAE4D from hkp 
server keyserver.ubuntu.com
  com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmp58u008j4/trustdb.gpg: 
trustdb created
  com.ubuntu.SoftwareProperties[2113]: gpg: key F59EAE4D: public key "Launchpad 
PPA for NoobsLab" imported
  com.ubuntu.SoftwareProperties[2113]: gpg: no ultimately trusted keys found
  com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1
  com.ubuntu.SoftwareProperties[2113]: gpg:   imported: 1  (RSA: 1)
  com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be 
parsed (stdout is not a terminal)
  com.ubuntu.SoftwareProperties[2113]: OK
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmpjwlat63e/secring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: keyring 
`/tmp/tmpjwlat63e/pubring.gpg' created
  com.ubuntu.SoftwareProperties[2113]: gpg: requesting key E2D0EBE9 from hkp 
server keyserver.ubuntu.com
  com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmpjwlat63e/trustdb.gpg: 
trustdb created
  com.ubuntu.SoftwareProperties[2113]: gpg: key E2D0EBE9: public key "Launchpad 
PPA for RAVEfinity Project" imported
  com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1
  com.ubuntu.SoftwareProperties[2113]: gpg:   imported: 1  (RSA: 1)
  com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be 
parsed (stdout is not a terminal)
  com.ubuntu.SoftwareProperties[2113]: OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.6.0-9.11-generic 4.6.4
  Uname: Linux 4.6.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jul 23 13:37:35 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1605861/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Daniel van Vugt]

** Patch removed: "gnome-control-center_3.27.92-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+attachment/5080005/+files/gnome-control-center_3.27.92-1ubuntu2.debdiff

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1700232] Re: aa-logprof ignores dbus access

[sles]

Will it be fixed in 16.04 LTS?
Thank you!

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

Title:
  aa-logprof ignores dbus access

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? 
terminal=?

  Is not recognized by aa-logprof .
  Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+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 1755144] Re: No audio on vlc or videos sound or video files

[John Rose]

The purge & reboot made no difference. For the last instruction, did you
mean to install ALL the approx 30 deb files?

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Daniel van Vugt]

Upstream bug for GDK's touchpad detection:
https://gitlab.gnome.org/GNOME/gtk/issues/97

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

OK, next idea: You seem to have config files from the old version of
pulse still installed:

ii  libpulse0:amd64   1:8.0-0ubuntu3.8  
amd64PulseAudio client libraries
rc  libpulse0:i3861:8.0-0ubuntu3.7  
i386 PulseAudio client libraries

It's also from the wrong architecture (i386). So this means your current
version might not work properly and/or your testing of the previous
version might have been flawed since the wrong architecture was
installed at some point...

Please:

1. Purge the old config files:
   sudo dpkg -P libpulse0:i386
2. Reboot and retest.

If that didn't work then please retry installing the previous version,
being sure to install the amd64 architecture only, from here:

https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.7/+build/1375

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1755144] Re: No audio on vlc or videos sound or video files

[John Rose]

I've done all the above previously and have done all the above just now.
Still no audio on this PC for mp3 files using vlc, but audio Ok on other
very similar (both barebones Intel with same memory) PC with same
software (i.e. Ubuntu 16.04, vlc). Other (new) PC had recent install
from 16.04.3 and uses ppa for get_iplayer resulting in libav packages
(as discussed previously) being from that ppa. This PC is approx 2 years
old and had install from 16.04.1. Both PCs are fully up to date with
software.

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1755006] Re: ModemManager crashed with SIGSEGV

[INIZAN yannick]

1725164 bug page doesn't exist anymore

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

Title:
  ModemManager crashed with SIGSEGV

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Dont know.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: modemmanager 1.6.8-2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 11 19:02:30 2018
  ExecutablePath: /usr/sbin/ModemManager
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55d771dd4659:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55d771dd4659) ok
   source "%es:(%rdi)" (0x55d771e68b28) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ()
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006/+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 1755006] Re: ModemManager crashed with SIGSEGV

[Launchpad Bug Tracker]

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

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

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

Title:
  ModemManager crashed with SIGSEGV

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Dont know.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: modemmanager 1.6.8-2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 11 19:02:30 2018
  ExecutablePath: /usr/sbin/ModemManager
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55d771dd4659:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55d771dd4659) ok
   source "%es:(%rdi)" (0x55d771e68b28) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ()
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006/+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 1755006] Re: ModemManager crashed with SIGSEGV

[INIZAN yannick]

** This bug is no longer a duplicate of private bug 1725164

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

Title:
  ModemManager crashed with SIGSEGV

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Dont know.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: modemmanager 1.6.8-2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 11 19:02:30 2018
  ExecutablePath: /usr/sbin/ModemManager
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55d771dd4659:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55d771dd4659) ok
   source "%es:(%rdi)" (0x55d771e68b28) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ()
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006/+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 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

[Daniel van Vugt]

** Summary changed:

- Graphics corruption (or distortion?) in login animation to Xorg sessions
+ Graphics corruption just before login animation to Xorg sessions (Intel gen9 
GPUs only)

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in X.Org X server:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be