[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Christopher M. Penalver]

** Tags added: latest-bios-a15 regression-release

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773484] [NEW] Login screen not moved to used monitor

[Manfred Steiner]

Public bug reported:

On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
the monitor where the mouse pointer is located. On Ubuntu 18.04 login
dialog and system menues are restricted to the main monitor.

So if you have a notebook with defect lcd display you can work with it
using Ubuntu 16.04 and an external monitor, but you cannot work with
Ubuntu 18.04, because you are not able to login!

This problem was also asked on:
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 26 07:04:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2018-04-30 (25 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20AQ007TGE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET77WW (2.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ007TGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQ007TGE
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 

[Touch-packages] [Bug 1773485] [NEW] Supplement to 1772...@bugs.launchpad.net,

[Roger Davis]

Public bug reported:

Supplement to 1772...@bugs.launchpad.net,

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 25 22:06:57 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1418 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
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 May 25 22:03:00 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug 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/1773485

Title:
  Supplement to 1772...@bugs.launchpad.net,

Status in xorg package in Ubuntu:
  New

Bug description:
  Supplement to 1772...@bugs.launchpad.net,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 25 22:06:57 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1770374] Re: My login screen stays black

[Christopher M. Penalver]

Dieter Meyer, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) Regarding the kernel you are using (4.13.0-37.42-generic 4.13.13) it
appears you are manually booting this or have it pinned. Could you
please update to a supported kernel (4.15.x) and advise to the results?

3) If you disable the nvidia card in your BIOS, does this provide a
WORKAROUND?

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

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

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

Title:
  My login screen stays black

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can't login to my desktop cause my login screen is black. So I read
  on the forums that you could bypass the login screen by typing startx
  in the tty screen but that also doesn't work please could help me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 12:02:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.13.0-38-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 2nd Generation Core Processor Family 
Integrated Graphics Controller [1558:2500]
   NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0ded] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CLEVO/KAPOK Computer GF108M [GeForce GT 520M] [1558:2500]
  InstallationDate: Installed on 2018-02-27 (72 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: GIGABYTE Q1532N
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=8f567cdc-b8e0-4a0f-b10b-1104f687f111 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Q1532N
  dmi.board.vendor: GIGABYTE
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/15/2011:svnGIGABYTE:pnQ1532N:pvrN/A:rvnGIGABYTE:rnQ1532N:rvrN/A:cvnGIGABYTE:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Q1532N
  dmi.product.version: N/A
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770479] Re: No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

[Christopher M. Penalver]

gmc, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770479/comments/3
regarding this being resolved by a reinstall. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I had ubuntu 17.10 running on my dell xps 15, which worked fine for
  months. Today I made the mistake of upgrading to 18.04, and now I am
  not getting any graphics anymore with the nvidia driver.

  With the nouveau driver I do get a login screen (display manager), but
  logging in just returns me to the login screen (tried with default
  session, mate, plasma and xmonad).

  I tried installing older nvidia drivers (nvidia-384, nvidia-375,
  nvidia-361) but it made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu May 10 21:11:03 2018
  DistUpgraded: 2018-05-10 19:48:11,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-12-16 (144 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=14e82bfb-9693-4da5-b107-280aeda9478e ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (0 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  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.7.0:bd12/15/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.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Christopher M. Penalver]

Lonnie Lee Best, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) To clarify, could you please describe how your computer is connected
to monitor (e.g. using a HDMI cord connecting both, using a
dongle/adapter, etc.)?

3) Regarding the use of kernel boot parameter acpi_backlight=vendor is
this required? If you remove it, is this issue still reproducible?

4) If you remove the nvidia drivers and use nouveau, is this
reproducible?

5) As per nvidia.com the latest driver version available for your card
is 390.59. hence, to see if this is already resolved in Ubuntu, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?

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

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

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

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout),
  I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:

  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
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1771111] Re: Freezes on Thinkpad R500

[Christopher M. Penalver]

Michal, thank you for reporting this and helping make Ubuntu better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) After the freezes, are there any crash files in the /var/crash
folder?

3) How often do the freezes occur?

4) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: bios-outdated-3.20

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

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

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

Title:
  Freezes on Thinkpad R500

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Problem with black boxes on screen, freezing mouse, random freezes
  (1-2s).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 14:36:13 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
  InstallationDate: Installed on 2017-11-12 (182 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 271434G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7YET50WW (1.20 )
  dmi.board.name: 271434G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7YET50WW(1.20):bd10/30/2008:svnLENOVO:pn271434G:pvrThinkPadR500:rvnLENOVO:rn271434G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad R500
  dmi.product.name: 271434G
  dmi.product.version: ThinkPad R500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/177/+subscriptions

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

[Touch-packages] [Bug 1773167] Re: [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a single CPU core

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Confirmed

** Changed in: pulseaudio
   Importance: Unknown => Medium

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1009 F...m pulseaudio
   /dev/snd/controlC0:  user   1009 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 15
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  CurrentDesktop: LXDE
  Date: Thu May 24 16:04:13 2018
  InstallationDate: Installed on 2018-05-22 (1 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - 

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Daniel van Vugt]

** Summary changed:

- You can not see the image of the movie
+ [i915 SNB] You can not see the image of the movie in Wayland sessions

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1773167] Re: Audio is not working; pulseaudio consumes 100% of a single CPU core

[Daniel van Vugt]

Now tracking upstream in:
https://bugs.freedesktop.org/show_bug.cgi?id=100488

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

** Changed in: pulseaudio
   Importance: High => Unknown

** Changed in: pulseaudio
   Status: Invalid => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #106645 => freedesktop.org Bugzilla 
#100488

** Summary changed:

- Audio is not working; pulseaudio consumes 100% of a single CPU core
+ [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a 
single CPU core

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

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of 

[Touch-packages] [Bug 1773167] Re: Audio is not working; pulseaudio consumes 100% of a single CPU core

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Invalid

** Changed in: pulseaudio
   Importance: Unknown => High

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

Title:
  Audio is not working; pulseaudio consumes 100% of a single CPU core

Status in PulseAudio:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1009 F...m pulseaudio
   /dev/snd/controlC0:  user   1009 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 15
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  CurrentDesktop: LXDE
  Date: Thu May 24 16:04:13 2018
  InstallationDate: Installed on 2018-05-22 (1 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Steve Langasek]

I confirm that this fixes the problem for the newly rolled out Starbucks
aruba hotspots.

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Jelmer Vernooij]

python3-ldb appears to have come from an ubuntu-specific patch that got
dropped at some point.

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen

[Chris Guiver]

1) understood (I'd guessed that)

2) NO I didn't have the issues in 17.10/artful.

I didn't use xfce for 2-3 weeks post release-upgrade to 18.04/bionic
because I couldn't login (login loop xfce only).   Your (4) "there could
have been some cruft left over from the upgrade" makes me happy; as it
fits my initial trouble getting xfce running :)

3) will re-test with 30-50 minute cycles & add comment(s) here.  I had
no issues this morning from last night's 'sleep' :)  (i usually have
machine on all day; in 'sleep' overnight)

4) Thank you


** Attachment added: "limited value - yesterday's syslog.1  
(may22.0941-may25.1256 aest so +1000)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5144437/+files/syslog.1_2018-05.25.txt

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched 

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

>"No the windows boot mgr got corrupted"

Regarding strong claims like, "... got corrupted" please post
logs/evidence, advise what caused the corruption, what the configuration
or log file looks like now, and what it should look like precisely to
not be considered corrupted.

1) Can you still dual boot into Windows? If so, run the following as an 
administrator and post the full results:
bcdedit /enum

2) When you boot into Windows, do you have "Turn on fast startup"
enabled? If so, does disabling this help?

"(removed from BIOS)"

As per your partition screenshot, you have an UEFI partition (i.e. not
BIOS).

3) In Ubuntu, did you manually edit fstab entries?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Dimitri John Ledkov]

** Changed in: ldb (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ldb (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: samba (Ubuntu)
   Importance: Wishlist => Critical

** Changed in: samba (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: talloc (Ubuntu)
   Importance: Undecided => Critical

** Changed in: talloc (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: tdb (Ubuntu)
   Importance: Undecided => Critical

** Changed in: tdb (Ubuntu)
Milestone: None => ubuntu-18.10

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Dimitri John Ledkov]

Hm python3-ldb used to be there in xenial, but not anymore? What has
happened to that?

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1773087] Re: Remove python3-apport as dependency of xserver-xorg

[Nish Aravamudan]

xserver-xorg now has an apport hook. So in order of ubuntu-bug to work,
it is necessary to have python3-apport installed, per LP: #1730035.
Definitely not a bug.

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

Title:
  Remove python3-apport as dependency of xserver-xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

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

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

[Touch-packages] [Bug 1773087] Re: Remove python3-apport as dependency of xserver-xorg

[Joern Heissler]

Caused by #1730035

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

Title:
  Remove python3-apport as dependency of xserver-xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

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

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

Re: [Touch-packages] [Bug 1773033] Re: unattended upgrade no longer actions on shutdown

[Anthony G]

I have confirmed the behavior on my 18.04 laptop. Yes, it was being 
started on battery and the service status matches your post. When 
started on power, the unattended-upgrades install on shutdown, although 
the screen is blank during the action.

I have confirmed that my 16.04 laptop does not behave in the same 
manner, regardless of being started on or off battery. In either case, 
the service is started and the updates are installed on shutdown - with 
screen status updates. The 16.04 machine is running unattended-upgrades 
0.90ubuntu0.9 = which confirms the changes you mentioned.

Thank you for the information!


On 05/25/2018 04:36 PM, Balint Reczey wrote:
> In my tests i found u-u operating properly on shutdown except when the
> system was started on battery, and in that case the u-u.service did not
> start - thus did not stop on shutdown:
>
> $ service unattended-upgrades status
> ● unattended-upgrades.service - Unattended Upgrades Shutdown
> Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
> vendor preset: enabled)
> Active: inactive (dead)
> Condition: start condition failed at Fri 2018-05-25 20:18:34 UTC; 38s ago
> └─ ConditionACPower=true was not met
>   Docs: man:unattended-upgrade(8)
>
> The change to not run on battery was introduced in 0.97, right before
> Artful's release.
>
> Did you start your system on battery?
>
> ** Changed in: unattended-upgrades (Ubuntu)
> Status: New => Triaged
>
> ** Changed in: unattended-upgrades (Ubuntu)
> Importance: Undecided => Medium
>

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

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESM:${distro_codename}";
  "${distro_id}:${distro_codename}-updates";
  //  "${distro_id}:${distro_codename}-proposed";
  //  "${distro_id}:${distro_codename}-backports";
  "LP-PPA-libreoffice:${distro_codename}";
  "Canonical:${distro_codename}";
  };

  Unattended-Upgrade::Package-Blacklist {
  //  "vim";
  //  "libc6";
  //  "libc6-dev";
  //  "libc6-i686";
  };

  Unattended-Upgrade::DevRelease "false";
  Unattended-Upgrade::InstallOnShutdown "true";
  Unattended-Upgrade::Remove-Unused-Dependencies "true";


  -/etc/apt/apt.conf.d/10periodic:--
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

No the windows boot mgr got corrupted (removed from BIOS) and only
Ubuntu was available i did not format the drive. I am not too
knowledgeable to troubleshoot Ubuntu in case something happens.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

>"The issue was reproducible with only Ubuntu boot,"

To clarify, you completely deleted everything on the drive, only
installed Ubuntu on it (no dual boot) and the problem was reproducible?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

The issue was reproducible with only Ubuntu boot, the issue did not
exist with the budgie flavor of 18.04.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

To confirm, if you reinstall Ubuntu by completely deleting the entire
drive and only install Ubuntu (no dual boots, manual partitions NTFS,
etc.) is this still reproducible?

If not reproducible, it is advised to keep it this way, and fire up
Windows in a virtual machine if you must use it. Otherwise, you may be
in for a protracted debugging session of ntfs-3g, and potentially
whatever else is going wrong.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773033] Re: unattended upgrade no longer actions on shutdown

[Balint Reczey]

In my tests i found u-u operating properly on shutdown except when the
system was started on battery, and in that case the u-u.service did not
start - thus did not stop on shutdown:

$ service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
   Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Fri 2018-05-25 20:18:34 UTC; 38s ago
   └─ ConditionACPower=true was not met
 Docs: man:unattended-upgrade(8)

The change to not run on battery was introduced in 0.97, right before
Artful's release.

Did you start your system on battery?

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Triaged

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESM:${distro_codename}";
  "${distro_id}:${distro_codename}-updates";
  //  "${distro_id}:${distro_codename}-proposed";
  //  "${distro_id}:${distro_codename}-backports";
  "LP-PPA-libreoffice:${distro_codename}";
  "Canonical:${distro_codename}";
  };

  Unattended-Upgrade::Package-Blacklist {
  //  "vim";
  //  "libc6";
  //  "libc6-dev";
  //  "libc6-i686";
  };

  Unattended-Upgrade::DevRelease "false";
  Unattended-Upgrade::InstallOnShutdown "true";
  Unattended-Upgrade::Remove-Unused-Dependencies "true";


  -/etc/apt/apt.conf.d/10periodic:--
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

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

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

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

To make sure that I'm not wandering, I made an own experiment, where I
put some code in postinst which prints the variables. (I uploaded it to
the same PPA.) Please see the result in the attached file.

So, considering that we must distinguish between upgrades and pure
configuration, only testing if $2 exists is not sufficient. I still
think that the code I proposed does the right thing. ;)

** Attachment added: "postinst-variables.txt"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+attachment/5144410/+files/postinst-variables.txt

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

The system is dual boot but Ubuntu and windows, both having their
separate partitions and DATA is the large common access partition for
both operating systems. The 158.43 GB primary is ubuntu with the
previous 3.73 GB as linux swap. DATA is the dump for both OSes

** Attachment added: "disk partitions.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144411/+files/disk%20partitions.PNG

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

To clarify, regarding the drive you installed Ubuntu on, are you either
dual booting with Windows, or manually created an NTFS partition?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

This is when the system goes into emergency mode

** Attachment added: "IMG_20180525_215300112[1].jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144409/+files/IMG_20180525_215300112%5B1%5D.jpg

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

This is when the system boots to the login even though DATA.mount failed

** Attachment added: "IMG_20180525_214648275_HDR[1].jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144408/+files/IMG_20180525_214648275_HDR%5B1%5D.jpg

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

How do i upload the video of event happening with quiet splash disabled
(file size of video is 684 MB), Downscaling can bring it to 37mb but the
system does not boot into the gui and that is not the error that comes
up when quiet splash is turned off. I will run the code in the above
comment and get back to you

** Attachment added: "Issue.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144389/+files/Issue.png

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773087] Re: Remove python3-apport as dependency of xserver-xorg

[Christopher M. Penalver]

Jörn Heissler, as mentioned previously, apport (which python3-apport is a 
dependent of) is used to capture and process program crashes (e.g. xorg and 
related packages). For more on apport, please see:
https://wiki.ubuntu.com/Apport

apt-rdepends apport
Reading package lists... Done
Building dependency tree   
Reading state information... Done
apport
  Depends: gir1.2-glib-2.0 (>= 1.29.17)
  Depends: lsb-base (>= 3.0-6)
  Depends: python3
  Depends: python3-apport (>= 2.20.9-0ubuntu7)
  Depends: python3-gi
gir1.2-glib-2.0
  Depends: libgirepository-1.0-1 (>= 1.45.4)
  Depends: libglib2.0-0 (>= 2.56.1)
libgirepository-1.0-1
  Depends: libc6 (>= 2.14)
  Depends: libffi6 (>= 3.0.4)
  Depends: libglib2.0-0 (>= 2.56.1)
libc6
  Depends: libgcc1
libgcc1
  Depends: gcc-8-base (= 8-20180414-1ubuntu2)
  Depends: libc6 (>= 2.14)
gcc-8-base
libffi6
  Depends: libc6 (>= 2.14)
libglib2.0-0
  Depends: libc6 (>= 2.17)
  Depends: libffi6 (>= 3.0.4)
  Depends: libmount1 (>= 2.19.1)
  Depends: libpcre3
  Depends: libselinux1 (>= 1.32)
  Depends: zlib1g (>= 1:1.2.2)
libmount1
  Depends: libblkid1 (>= 2.17.2)
  Depends: libc6 (>= 2.25)
  Depends: libselinux1 (>= 2.6-3~)
libblkid1
  Depends: libc6 (>= 2.25)
  Depends: libuuid1 (>= 2.16)
libuuid1
  Depends: libc6 (>= 2.25)
libselinux1
  Depends: libc6 (>= 2.14)
  Depends: libpcre3
libpcre3
  Depends: libc6 (>= 2.14)
zlib1g
  Depends: libc6 (>= 2.14)
lsb-base
python3
  Depends: libpython3-stdlib (= 3.6.5-3)
  Depends: python3.6 (>= 3.6.5-2~)
  PreDepends: python3-minimal (= 3.6.5-3)
libpython3-stdlib
  Depends: libpython3.6-stdlib (>= 3.6.5-2~)
libpython3.6-stdlib
  Depends: libbz2-1.0
  Depends: libc6 (>= 2.15)
  Depends: libdb5.3
  Depends: libffi6 (>= 3.0.4)
  Depends: liblzma5 (>= 5.1.1alpha+20120614)
  Depends: libmpdec2
  Depends: libncursesw5 (>= 6)
  Depends: libpython3.6-minimal (= 3.6.5-3)
  Depends: libreadline7 (>= 7.0~beta)
  Depends: libsqlite3-0 (>= 3.5.9)
  Depends: libtinfo5 (>= 6)
  Depends: mime-support
libbz2-1.0
  Depends: libc6 (>= 2.4)
libdb5.3
  Depends: libc6 (>= 2.17)
liblzma5
  Depends: libc6 (>= 2.17)
libmpdec2
  Depends: libc6 (>= 2.14)
libncursesw5
  Depends: libc6 (>= 2.14)
  Depends: libtinfo5 (= 6.1-1ubuntu1)
libtinfo5
  Depends: libc6 (>= 2.16)
libpython3.6-minimal
  Depends: libc6 (>= 2.14)
  Depends: libssl1.1 (>= 1.1.0)
libssl1.1
  Depends: debconf (>= 0.5)
  Depends: debconf-2.0
  Depends: libc6 (>= 2.14)
debconf
  PreDepends: perl-base (>= 5.20.1-3~)
perl-base
  PreDepends: dpkg (>= 1.17.17)
  PreDepends: libc6 (>= 2.23)
dpkg
  Depends: tar (>= 1.28-1)
  PreDepends: libbz2-1.0
  PreDepends: libc6 (>= 2.14)
  PreDepends: liblzma5 (>= 5.2.2)
  PreDepends: libselinux1 (>= 2.3)
  PreDepends: libzstd1 (>= 1.3.2)
  PreDepends: zlib1g (>= 1:1.1.4)
tar
  PreDepends: libacl1 (>= 2.2.51-8)
  PreDepends: libc6 (>= 2.17)
  PreDepends: libselinux1 (>= 1.32)
libacl1
  Depends: libattr1 (>= 1:2.4.46-8)
  Depends: libc6 (>= 2.14)
libattr1
  Depends: libc6 (>= 2.4)
libzstd1
  Depends: libc6 (>= 2.14)
debconf-2.0
libreadline7
  Depends: libc6 (>= 2.15)
  Depends: libtinfo5 (>= 6)
  Depends: readline-common
readline-common
  Depends: dpkg (>= 1.15.4)
  Depends: install-info
install-info
  Depends: libc6 (>= 2.14)
  PreDepends: dpkg (>= 1.16.1)
libsqlite3-0
  Depends: libc6 (>= 2.14)
mime-support
python3.6
  Depends: libpython3.6-stdlib (= 3.6.5-3)
  Depends: mime-support
  Depends: python3.6-minimal (= 3.6.5-3)
python3.6-minimal
  Depends: libexpat1 (>= 2.1~beta3)
  Depends: libpython3.6-minimal (= 3.6.5-3)
  Depends: zlib1g (>= 1:1.2.0)
  PreDepends: libc6 (>= 2.25)
libexpat1
  Depends: libc6 (>= 2.25)
python3-minimal
  Depends: dpkg (>= 1.13.20)
  Depends: python3.6-minimal (>= 3.6.5-2~)
python3-apport
  Depends: lsb-release
  Depends: python3-apt (>= 0.7.9)
  Depends: python3-httplib2
  Depends: python3-problem-report (>= 0.94)
  Depends: python3-requests-unixsocket
  Depends: python3:any (>= 3.3.2-2~)
lsb-release
  Depends: distro-info-data
  Depends: python3:any (>= 3.4~)
distro-info-data
python3:any
python3-apt
  Depends: libapt-inst2.0 (>= 1.4~beta3)
  Depends: libapt-pkg5.0 (>= 1.4~beta3)
  Depends: libc6 (>= 2.14)
  Depends: libgcc1 (>= 1:3.0)
  Depends: libstdc++6 (>= 5.2)
  Depends: python-apt-common
  Depends: python3 (>= 3.6~)
  Depends: python3:any (>= 3.3.2-2~)
libapt-inst2.0
  Depends: libapt-pkg5.0 (>= 1.1~exp9)
  Depends: libc6 (>= 2.14)
  Depends: libgcc1 (>= 1:3.0)
  Depends: libstdc++6 (>= 5.2)
libapt-pkg5.0
  Depends: libbz2-1.0
  Depends: libc6 (>= 2.27)
  Depends: libgcc1 (>= 1:3.0)
  Depends: liblz4-1 (>= 0.0~r127)
  Depends: liblzma5 (>= 5.1.1alpha+20120614)
  Depends: libstdc++6 (>= 5.2)
  Depends: libudev1 (>= 183)
  Depends: libzstd1 (>= 1.3.2)
  Depends: zlib1g (>= 1:1.2.2.3)
liblz4-1
  Depends: libc6 (>= 2.14)
libstdc++6
  Depends: gcc-8-base (= 8-20180414-1ubuntu2)
  Depends: libc6 (>= 2.18)
  Depends: libgcc1 (>= 1:4.2)
libudev1
  Depends: libc6 (>= 2.25)
python-apt-common
python3-httplib2
  Depends: ca-certificates
  

[Touch-packages] [Bug 1771340] Re: sshd failed on config reload

[Andreas Hasenack]

Confirmed fixed in >= artful. We have two ExecReload items under [Service]:
[Service]
...
ExecReload=/usr/sbin/sshd -t
ExecReload=/bin/kill -HUP $MAINPID


** Tags added: bitesize

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

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

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

Title:
  sshd failed on config reload

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  After adding some lines to /etc/ssh/sshd_config I tried to reload the
  configuration with the command:

  ```
  sudo systemctl reload sshd
  ```

  No error message was returned. So I assumed that the sshd was running
  with the current config. But `sudo systemctl status sshd` told me that
  the service failed due to a wrong option in /etc/ssh/sshd_config.
  Please see the following output:

  ~~~
  :~$ sudo vim /etc/ssh/sshd_config
  :~$ sudo systemctl reload sshd
  :~$ sudo systemctl status sshd
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s 
ago
Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 7536 (code=exited, status=255)
  ~~~

  I would expect that a warning or error message is returned when the
  service fails while reloading it's configuration.

  A fix for this behaviour would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 15 10:18:25 2018
  InstallationDate: Installed on 2013-01-10 (1950 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago)
  mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

[Andreas Hasenack]

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

1) The boot log attached notes:
[FAILED] Failed to mount /media/DATA.
See 'systemctl status media-DATA.mount' for details.

Please execute the following command in a terminal from a failed boot and post 
the full results here:
systemctl status media-DATA.mount

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu4

---
gnome-control-center (1:3.28.1-0ubuntu4) cosmic; urgency=medium

  [ Andrea Azzarone ]
* debian/patches/git_invalid_dereferencing.patch:
- Avoid dereferencing invalid pointer (lp: #1759468)

 -- Sebastien Bacher   Fri, 25 May 2018 16:25:16
+0200

** Changed in: gnome-control-center (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1759468

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

[Mathieu Trudel-Lapierre]

Still a bug; if systemd-networkd requires a restart, then systemd-
networkd has something that it gets confused about, that we'll need to
figure out.

** Also affects: systemd (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/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu: 18.04
  systemd:   
  Installed: 237-3ubuntu10
  Candidate: 237-3ubuntu10
  netplan.io:
Installed: 0.36.1
Candidate: 0.36.1

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    addresses: [192.168.3.30/25]
    dhcp4: no
    routes:
     - to: 0.0.0.0/0
   via: 192.168.3.1
   metric: 100
   table: 101

    routing-policy:
     - from: 192.168.3.0/25
   table: 101

  ens7:
    addresses: [192.168.5.24/25]
    dhcp4: no
    gateway4: 192.168.5.1
    nameservers:
  addresses: [1.1.1.1]

  this doesn't activate a proper rule for table 101:
  0:  from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  in place of
  0:  from all lookup local
  32765:  from 192.168.3.0/25 lookup 101
  32766:  from all lookup main
  32767:  from all lookup default

  the file in /etc/systemd/network contains the correct information:
  [Match]
  Name=ens3

  [Network]
  Address=192.168.3.30/25

  [Route]
  Destination=0.0.0.0/0
  Gateway=192.168.3.1
  Metric=100
  Table=101

  [RoutingPolicyRule]
  From=192.168.3.0/25
  Table=101

  the ens3 is reachable from 3.0 but not from anywhere else

  with ifupdown on another system both interfaces would be reachable from 
everywhere on the private subnets.
  up ip route add default table 101 dev enp8s0 via 192.168.3.1
  up ip rule add from 192.168.3.0/25 lookup 101
  down ip rule del from 192.168.3.0/25
  down ip route del default table 101 via 192.168.3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Wynona Stacy Lockwood]

Fresh install of UbuntuStudio 18.04, same issue:
# grep -i uread /var/log/syslog | grep -i "May 25 12:43" | wc -l
93742

May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sys: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:class: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sound: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:card0: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:..: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:..: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:devices: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:pci:00: Ignored 
relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead::00:1b.0: Ignored 
relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sound: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:card0: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sys: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:class: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sound: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:card0: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:..: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:..: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:devices: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:pci:00: Ignored 
relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead::00:1b.0: Ignored 
relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sound: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:card0: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:run: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:1000: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:run: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:1000: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:etc: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:usr: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:lib: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:run: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:1000: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:run: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:1000: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:etc: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: Ignored relative 
path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:user: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:usr: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:lib: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:systemd: 

[Touch-packages] [Bug 1773431] [NEW] polkid uses CPU extensively, laptop becomes very hot

[Ivan Yarych]

Public bug reported:

At some point polkitd starts to consume CPU power and nothing helps to
make it eat less - only a reboot. This causes laptop to overheat and
coolers spin like crazy.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: policykit-1 0.105-20
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 25 21:28:23 2018
ExecutablePath: /usr/lib/policykit-1/polkitd
InstallationDate: Installed on 2017-01-31 (478 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: policykit-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  polkid uses CPU extensively, laptop becomes very hot

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  At some point polkitd starts to consume CPU power and nothing helps to
  make it eat less - only a reboot. This causes laptop to overheat and
  coolers spin like crazy.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: policykit-1 0.105-20
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 25 21:28:23 2018
  ExecutablePath: /usr/lib/policykit-1/polkitd
  InstallationDate: Installed on 2017-01-31 (478 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767359] Re: netplan does not work on nfsroot

[Mathieu Trudel-Lapierre]

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

This is essentially a duplicate of bug 1769682.

** This bug has been marked a duplicate of bug 1769682
   NFS-based remote root hangs when running 'netplan apply'

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

Title:
  netplan does not work on nfsroot

Status in netplan:
  In Progress
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in netplan.io package in Ubuntu:
  In Progress

Bug description:
  It seems like netplan is not working on nfsroot systems.

  Whenever a valid config.yaml is located in /etc/netplan/ the boot
  procedure gets stuck.

  However, with an empty /etc/netplan directory, the nfsroot system
  boots (fetching IP DHCP config by kernel). Then, when I store a config
  in /etc/netplan and run "netplan apply", it stucks again.

  I guess, netplan is (temporarily) taking down active interfaces when
  applying a configuration. This must never happen on nfsroot
  systems(!). I this assumption is true, this is probably a general
  mistake, in my opinion.

  Regards,
   -frank

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Launchpad Bug Tracker]

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

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Launchpad Bug Tracker]

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

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Launchpad Bug Tracker]

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

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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

Re: [Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Tomáš Klos]

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
  ii  xserver-xorg-video-ati 1:18.0.1-1 
 
  ii  

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

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

** Changed in: netplan.io (Ubuntu)
   Status: New => In Progress

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

** Summary changed:

- I get booted into recovery mode every third boot or from sleep when on battery
+ [ASUS R554LA] I get booted into recovery mode every third boot or from sleep 
when on battery

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen

[Christopher M. Penalver]

Chris Guiver:

1) Regarding hibernate not working, if you would like to pursue a fix for this, 
it is out of scope for this report. However, you may file a new report about it 
via a terminal:
ubuntu-bug linux

2) To clarify, did you have issues after sleep/resume in 17.10?

3) In regards to sleep/resume testing, when folks are vetting
sleep/resume, they typically do 30-50 consecutive sleep cycles to rule
out one offs. It wouldn't hurt to do this to see if a sleep/resume issue
may be reproduced this way.

4) With regard to root cause, a few other possibilities:
* This issue could be the fall out of a failed sleep/resume versus apps not 
working. The reproduction of this could depend on how long you have the 
computer in sleep, how long it was in use prior to sleep, what apps you have 
running prior to sleep, and/or other factors (i.e. misbehaving 
drivers/firmware).
* When you upgraded from 17.10, there could have been some cruft left over from 
the upgrade, that when caffeine was removed and re-installed, it was reset to 
default configuration.

Hence, we can keep an eye on this given you did some preliminary testing
without reproduction, and allow more testing results to be reviewed.

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 

[Touch-packages] [Bug 1773235] Re: I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

I now got an error like this after the plymouth splash screen and now the 
system just hangs up after the splash screen.
A start job is running for Hold until boot process finishes up (42m/no limit)

at the boot if i use alt+ctrl+f2,
I have only run sudo apt update && sudo apt upgrade and have installed wine 
from ubuntu database, Zotero and calibre. This issue was present from the 
initial install but increased in frequency. Please do tell me the location of 
the files you will need and i can use a linux reader on windows to get the 
files. The system goes into emergency mode or just hangs up when entering the 
command line now, I have tried dpkg using recovery mode only and it returns 
with no changes. I also had changed the Plymouth logo from the ubuntu directory 
but did not encounter issues after the change

** Attachment added: "the boot log file that was not attached"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144357/+files/boot.log

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

Title:
  I get booted into recovery mode every third boot or from sleep when on
  battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Christopher M. Penalver]

Thomas Diesenreiter, in order to allow additional upstream mainline kernel 
developers to examine the issue, at your earliest convenience, could you please 
test the latest mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Christopher M. Penalver]

Tomáš Klos, to clarify, in Ubuntu 18.04 if you use a Ubuntu (Wayland)
session is the performance as you expected?

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 

[Touch-packages] [Bug 1772222] Re: dangling symlink in /etc/rsyslog.d breaks rsyslogd

[Brian Murray]

** Tags added: regression-release

** Tags added: rls-bb-incoming rls-cc-incoming

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

Title:
  dangling symlink in /etc/rsyslog.d breaks rsyslogd

Status in rsyslog package in Ubuntu:
  New
Status in rsyslog source package in Bionic:
  New

Bug description:
  Since upgrading from artful to bionic, I noticed that
  /var/log/kern.log, etc., were not being updated on my machine.

  In comparing to another machine running a fresh install of bionic, I
  discovered that this seems to be the culprit:

  [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf 
  lrwxrwxrwx 1 root root 45 Jun 14  2017 /etc/rsyslog.d/99-conjure-up.conf -> 
/usr/share/conjure-up/conjure-up-rsyslog.conf
  [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf
  ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such 
file or directory
  [agnew(etc)] _

  Before deletion:

  [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  [agnew(etc)] _

  After deletion:

  [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf 
  [agnew(etc)] sudo service rsyslog restart

  [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  rsyslogd 30686 syslog8w   REG  253,122782   15213384 
/var/log/syslog
  rsyslogd 30686 syslog9w   REG  253,1 2065   15219687 
/var/log/auth.log
  [agnew(etc)] _

  It didn't occur to me to check the service status until writing this
  bug report, but in fact it does report the problem on startup:

  May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file 
/etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file 
or directory '/etc/rsyslog.d/99-conjure
  May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active 
actions configured. Inputs will run, but no output whatsoever is created. 
[v8.32.0 try http://www.rsyslog.com

  However, it's unlikely this warning will be discovered until it's too
  late, if ever -- consider a remote syslogging setup on a machine that
  has since been decommissioned or reinstalled -- and so it would
  probably better for rsyslogd to cope with dangling symlinks.  Indeed,
  given the age of the symlink, this is a regression from artful or
  earlier.

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

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

[Touch-packages] [Bug 1773235] Re: I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

Unfortunately, the screenshots provided do not show the root cause of
the problem.

Could you please take a recording via your phone of a failed boot from
start to finish?

Also, you didn't answer question 2).

** Tags added: latest-bios-504

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

Title:
  I get booted into recovery mode every third boot or from sleep when on
  battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Christopher M. Penalver]

** Tags added: bios-outdated-f.65

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
  ii  xserver-xorg-video-ati 1:18.0.1-1

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

Ok. Please note that I never tested a *first* install of keyboard-
configuration (hard to do due to dependencies). Besides upgrade I tested
reinstall and "dpkg-reconfigure keyboard-configuration". Especially in
the latter case it's obviously important that all the postinst code does
run.

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

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

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

[Touch-packages] [Bug 1771539] Re: Xorg crash

[Christopher M. Penalver]

Mario Costa:

Your BIOS is outdated as per HP -> https://support.hp.com/us-
en/drivers/selfservice/hp-elitebook-840-g1-notebook-pc/5405360

Also, you didn't respond to question 2).

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  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: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy

[Ubuntu Foundations Team Bug Bot]

The attachment "goa.debdiff" seems to be a debdiff.  The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff.  If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

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

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

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

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

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  Fix Released
Status in vlan package in Ubuntu:
  Fix Released
Status in ifupdown source package in Trusty:
  Fix Released
Status in vlan source package in Trusty:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Released
Status in vlan source package in Xenial:
  Fix Released
Status in ifupdown source package in Artful:
  Fix Released
Status in vlan source package in Artful:
  Fix Released
Status in ifupdown source package in Bionic:
  Fix Released
Status in vlan source package in Bionic:
  Fix Released
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [impact]

  in bug 1573272, the vlan pkg was changed to perform a full ifup inside
  its if-pre-up.d/vlan script.  This allowed correct ordering of ifup
  for a vlan and its raw-device, as previously there was a race
  condition between them (see that bug for details).

  However, this causes hangs during ifup with certain specific configs.
  The reasons are given starting in comment 13.

  The result is a regression for those using the specific ifupdown
  configs; when they try to reboot and/or ifup -a, it will hang trying
  to bring up their network, preventing boot from finishing (or hanging
  before the network is fully configured).

  [test case]

  upgrade to the latest vlan package and configure the system with an
  affected ifupdown config, then reboot.  The reboot will hang while
  trying to bring the network up.

  see the original description below for an example ifupdown config to
  reproduce this, although there are other possible configs that
  will/may trigger this regression.

  [regression potential]

  The fix for this moves the creation of the vlan(s) corresponding to a
  physical raw-device 'hotplug' event out of the udev processing path
  for the raw-device, and into an ifup post script for the raw-device
  ifup.  If this is not done correctly, then any interfaces that are
  hotplugged, and have vlans configured on them, may fail to correctly
  create/configure their vlan(s).

  This change does remove the direct call to ifup from the if-pre-up.d
  (or if-up.d) scripts, so there should not be any regression potential
  for more ifup deadlocks.

  [other info]

  this required both ifupdown and vlan to be patched.  vlan was patched
  to remove the problematic call to ifup from the vlan pre-up script,
  and add a call to create the vlan interface(s) from a new post-up
  script, as well as adding a parameter to vlan-network-interface script
  to handle the call from udev itself differently than a call from
  elsewhere (such as the if-up.d/vlan script).  this works for bootup
  and ifup/ifup -a, but fails for device hotplug because of a bug in
  ifupdown that prevents calling ifquery from an ifup script; that has
  been patched upstream already, and is the only ifupdown change needed
  here.

  
  [original description]

  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
    └─run-parts,1501 /etc/network/if-pre-up.d
    └─bridge,1502 /etc/network/if-pre-up.d/bridge
    └─bridge,1508 /etc/network/if-pre-up.d/bridge
    └─vlan,1511 /etc/network/if-pre-up.d/vlan
    └─ifup,1532 eth0

  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
    address 192.168.10.65
    netmask 255.255.255.192
    gateway 192.168.10.66

  auto eth0.11
    address 192.168.11.1
    netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
    bridge_ports eth0.1134
    bridge_stp off
    bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

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

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

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

It shouldn't be like that. I just now did an experiment with a new empty
package and I only saw $2 having the version number for upgrades - on
first install $2 was empty. Anyway, I'll take your changes, tweak them a
little bit and sponsor if they seem to work as expected.

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

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

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

[Touch-packages] [Bug 1770725] Re: You can not see the image of the movie

[Cristian Aravena Romero]

Hello Daniel van Vugt,

I am using totem as a player.
* totem 3.26.0-0ubuntu6 

Regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770725] Re: You can not see the image of the movie

[Cristian Aravena Romero]

Hello Daniel van Vugt,

The problem occurs with Wayland, in Xorg with Totem if you can watch the
movie.

Regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770725] Re: You can not see the image of the movie

[Cristian Aravena Romero]

** Attachment added: "lspci_-k.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5144287/+files/lspci_-k.txt

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

"This is why I added
cloud-init to affected packages -- cloud-init should not be second-
guessing the network layer and attempting to do renames / to run"

There is no second guessing.  In the case where we have no network
config, there is no renaming; we accept whatever name is given.

If the config passed to cloud-init includes a name for an interface, then
cloud-init applies that name; this is the MAAS scenario;

Given the unreliable nature of udev w.r.t naming (see this very bug)
The *only* way for cloud-init to ensure that a directive to name an interface
matches the config (also note cloud-init accepts network config in
various formats
not just netplan) is to handle naming if requested directly, precisely
due to this bug.

If we fix systemd-udevd to allow renames of interfaces reliably that helps
most cases where udevd runs.  For the remaining cases where udev doesn't run,
containers for example, cloud-init will still need to use iproute2 to
set an interface
name if requested.


On Fri, May 25, 2018 at 8:55 AM, Mathieu Trudel-Lapierre
 wrote:
> netplan changes are available in git:
>
> Daniel's patch to write udev rules (SRU material):
> https://github.com/CanonicalLtd/netplan/commit/b0c51bfa8ba8b898a9feaed9cd7d8790d147d35d
>
> Daniel's patch + dropping replug code + rework 'netplan apply' (code for 
> cosmic); in progress for upload to cosmic:
> https://github.com/CanonicalLtd/netplan/tree/live-rename
>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: 

[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy

[Andrea Azzarone]

Please find attached the proposed debdiff.

** Patch added: "goa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+attachment/5144284/+files/goa.debdiff

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

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

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

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

On Fri, May 25, 2018 at 9:09 AM, Mathieu Trudel-Lapierre
 wrote:
> I'm not completely sure where the code lives in cloud-init; it looks a
> bit like what's in:
>
> cloudinit/net/netplan.py
>
> But the code does read as though it should not be running 'udevadm test-
> builtin net_setup_link'. However, deploying a system with MAAS shows a
> /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file, which contains
> data referring to the network interfaces:
>
> network:
>   config:
>   - id: ens6
> mac_address: 52:54:00:31:27:2c
> mtu: 1500
> name: ens6
> subnets:
> - address: 10.3.99.13/24
>   gateway: 10.3.99.1
>   type: static
> type: physical
>   version: 1
>
> With that file in place, any netplan config renaming the interface to
> something other than ens6 will see the interface being renamed *again*
> back to ens6, when that file is removed, this behavior does not appear.

Cloud-init only renders network config once per-instance.  If a user
wanted to modify this to something else (and we fix udev to handle
.link file name changes) then there won't be any additional renames.
Even without the change, cloud-init isn't going to call udevadm test-builtin
more than once per-instance.


>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

On Fri, May 25, 2018 at 8:48 AM, Mathieu Trudel-Lapierre
 wrote:
> My recommended course of action for cosmic:
>
>  - drop udevadm (net_setup_link) call from cloud-init

This will still be needed in the case that we have a network config with names.
Cloud-init runs after udev coldplug, so any .link files would have to already be
present.  We're generating a network config post coldplug, but pre networking.

Now, if after we netplan generate, if links could be applied or if
networkd kicks udev
to rename interfaces, that's fine.  But it doesn't do that today.

>  - drop set-name "renaming" from cloud-init / maas

I've already replied, but this is required for instances where udev
doesn't run but
network config has been provided.

>  - drop replug code in netplan; replace with proper .link code,
possibly call to net_setup_link.

+1

>  - maybe write udev rule for renaming in netplan (think belt and
suspenders)

? Instead of the .link files?

>  - make sure .link files are written correctly by netplan for renaming
>  - patch systemd to not second-guess renaming from .link files

+1

>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope 

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

My recommended course of action for SRUs:

 - write udev .rules files from netplan to enforce renaming
 - drop udevadm (net_setup_link) call from cloud-init

The above should be sufficient and non-intrusive enough for SRU. The
tasks for cosmic are additional changes to clean up the behavior for the
future.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

I'm not completely sure where the code lives in cloud-init; it looks a
bit like what's in:

cloudinit/net/netplan.py

But the code does read as though it should not be running 'udevadm test-
builtin net_setup_link'. However, deploying a system with MAAS shows a
/etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file, which contains
data referring to the network interfaces:

network:
  config:
  - id: ens6
mac_address: 52:54:00:31:27:2c
mtu: 1500
name: ens6
subnets:
- address: 10.3.99.13/24
  gateway: 10.3.99.1
  type: static
type: physical
  version: 1

With that file in place, any netplan config renaming the interface to
something other than ens6 will see the interface being renamed *again*
back to ens6, when that file is removed, this behavior does not appear.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

** Patch added: "draft systemd patch to skip should_rename(), adds extra debug 
info"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1770082/+attachment/5144272/+files/debug.patch

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

My recommended course of action for cosmic:

 - drop udevadm (net_setup_link) call from cloud-init
 - drop set-name "renaming" from cloud-init / maas
 - drop replug code in netplan; replace with proper .link code, possibly call 
to net_setup_link.
 - maybe write udev rule for renaming in netplan (think belt and suspenders)
 - make sure .link files are written correctly by netplan for renaming
 - patch systemd to not second-guess renaming from .link files

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

netplan changes are available in git:

Daniel's patch to write udev rules (SRU material):
https://github.com/CanonicalLtd/netplan/commit/b0c51bfa8ba8b898a9feaed9cd7d8790d147d35d

Daniel's patch + dropping replug code + rework 'netplan apply' (code for 
cosmic); in progress for upload to cosmic:
https://github.com/CanonicalLtd/netplan/tree/live-rename

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Dimitri John Ledkov]

Hm I think I am confused on how this feature is supposed to work.

I've increased the swapfile size to cover my RAM and then some. However,
initramfs doesn't configure resume= nor resume_offset= thus after
hibernation, resume is not at all attempted. Should I specify
resume=/dev/vda1 or some such?

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan
   Status: Incomplete => Confirmed

** Changed in: cloud-init (Ubuntu)
   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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

There are a couple of pieces in play here.

One aspect is that we don't really want to write the .link files for
systemd-networkd to /lib or get anything from /run into the initrd --
that defeats the purpose of netplan's config being dynamic.

The second aspect is that depending on how the systems are deployed
(MAAS? cloud images? openstack? VM? hardware?) changes the behavior a
bit. Some USB-based network interfaces are simply "unaffected" and
rename just fine at boot. Other systems may be renaming the interfaces,
but seeing cloud-init re-change the name *back* to the previous value
(this has been observed for MAAS-deployed systems). This is why I added
cloud-init to affected packages -- cloud-init should not be second-
guessing the network layer and attempting to do renames / to run
udevadm, except *maybe* at first boot/when the instance data is created.
I believe it should just leave it alone completely, and let
netplan/systemd/NM deal with the interfaces themselves (if anything
needs to be poked, it's arguably a bug in the backend).

Another issue is that systemd is also second-guessing configuration. If
we set things to be renamed, we do want them to be renamed. Now, this is
a bit more up to discussion upstream, but I do think systemd should
always rename if configuration tells it to (via .link files or udev
rules -- .link files are "cleaner", easier to write). Users renaming
their interfaces manually via 'ip link dev X name Y' are doing so on
their own, and the change would not be persistent across a reboot --
renaming in configuration is expected to work normally.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 

[Touch-packages] [Bug 1773370] Re: package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[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 ncurses in Ubuntu.
https://bugs.launchpad.net/bugs/1773370

Title:
  package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in ncurses package in Ubuntu:
  New

Bug description:
  just installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libncurses5:amd64 6.1-1ubuntu1.18.04
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 24 18:05:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libgpm2 1.20.7-5
   libtinfo5 6.1-1ubuntu1.18.04
  DuplicateSignature:
   package:libncurses5:amd64:6.1-1ubuntu1.18.04
   Unpacking libncurses5:i386 (6.1-1ubuntu1.18.04) over (6.1-1ubuntu1) ...
   dpkg: error processing package libncurses5:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-05-11 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ncurses
  Title: package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773370] [NEW] package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Russell Durrenberger]

Public bug reported:

just installing updates

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libncurses5:amd64 6.1-1ubuntu1.18.04
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Thu May 24 18:05:02 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 libgpm2 1.20.7-5
 libtinfo5 6.1-1ubuntu1.18.04
DuplicateSignature:
 package:libncurses5:amd64:6.1-1ubuntu1.18.04
 Unpacking libncurses5:i386 (6.1-1ubuntu1.18.04) over (6.1-1ubuntu1) ...
 dpkg: error processing package libncurses5:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-05-11 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ncurses
Title: package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in ncurses package in Ubuntu:
  New

Bug description:
  just installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libncurses5:amd64 6.1-1ubuntu1.18.04
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 24 18:05:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libgpm2 1.20.7-5
   libtinfo5 6.1-1ubuntu1.18.04
  DuplicateSignature:
   package:libncurses5:amd64:6.1-1ubuntu1.18.04
   Unpacking libncurses5:i386 (6.1-1ubuntu1.18.04) over (6.1-1ubuntu1) ...
   dpkg: error processing package libncurses5:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-05-11 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ncurses
  Title: package libncurses5:amd64 6.1-1ubuntu1.18.04 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy

[Andrea Azzarone]

** Tags added: rls-bb-incoming

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

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

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

[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

[Bumble57]

@Philipp Hufnagl

Thanks a lot worked also for me perfect running 18.10 on Tuxedo Laptop.
Just created the  file, 
added the
lines and saved it. Restart and anything works fine.

Thanks!
Christian

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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

[Touch-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Expired

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Expired
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  I am running 15.10 development version fully up to date, I installed it a few 
days ago and I have an issue with newly installed applications not appearing in 
the dash when I search for them, they can be started via console but the 
icons/launchers of newly installed applications will only appear in the dash 
after session is restarted.

  [Test case]
  1. Install a new applicaiton (using apt-get or the software center)
  2. Make sure the application is listed in the Unity Dash

  [Possible Regressions]
  Unity fails to list all the applications, not just the newly installed ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)Z

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

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

[Touch-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Expired

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

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

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

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

Hi Christopher,

ad 1: 17.10
ad 2: I cannot check that, sorry. My boot partition is so small (only 256mb, 
happened when I first installed ubuntu on this machine in 2013 for whatever 
reason), so i have to uninstall the older kernels immediately after updating in 
order to be able to install updates.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Julian Andres Klode]

Ran the dist-upgrade:

with bionic, bionic-updates:

Unpacking bluez (5.48-0ubuntu3) over (5.37-0ubuntu5.1) ...   
systemctl: error while loading shared libraries: libcryptsetup.so.12: cannot 
open shared object file: No such file or directory


with bionic, bionic-updates, bionic-proposed (pinned to only allow src:systemd 
packages) it works fine. Well, it hangs in my container, but that might be a 
container thingy.


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

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

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

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

[Touch-packages] [Bug 677743]

[Douglas Greenstein]

http://favourite.neovolo.org
Doug Greenstein

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

Title:
  [Realtek ALC662 rev1] Playback problem Rhythm box will not play. there
  is no sound. I may have erased some necessary sub programs while I was
  trying to get real player to work.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I'm a novice to computers and Linux. Have the latest version of Ubuntu
  which I down-loaded a few days ago. The Rhythm box player was working
  fine when I first used it. As I said I added some GStreamer components
  which than caused the Rhythm box not to work and then I undid them.
  The real player still doesn't work. I really didn't know what I was
  doing!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
  Uname: Linux 2.6.35-22-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1641 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,103c2a99,00100101'
 Controls  : 18
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbfec000 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Nov 19 23:25:32 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 NVidia HDA-Intel - HDA NVidia
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC662 rev1] Playback problem
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.15
  dmi.board.name: Narra6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 6.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.15:bd11/06/2009:svnHP-Pavilion:pnAY643AA-ABAs5310f:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: AY643AA-ABA s5310f
  dmi.sys.vendor: HP-Pavilion

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

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

[Touch-packages] [Bug 1773157] Re: procps outdated network options, old syncookies, new ecn update please.

[Simon Iremonger]

(fwiw, fq_codel queuing is now being turned-on in bionic (at least) by systemd, 
confusingly!).
https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47
Possibly, turning on ECN might more likely happen there first, but I would like 
the procps updated for those using upstart or otherwise).   This seems to be 
the last piece of bufferbloat puzzle (see LP bug #1436945 ).

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

Title:
  procps outdated network options, old syncookies, new ecn update
  please.

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu version of procps carries it's own  /etc/sysctl.d/10
  -network-security.conf  file explicitly that appears not to be part of
  debian procps version.

  
  Firstly, the section about "# Turn on SYN-flood protections." (came from LP 
#57091 ) is now entirely outdated, upstream kernel has long since turned on 
syncookies by default, so setting this flag explicitly in 
10-network-security.conf is entirely redundant likely since before ubuntu-14.04 
.
  I would like the ubuntu-maintainer to remove that section entirely in cosmic 
onwards.

  [I am going to report debian the similarly outdated syncookies
  comments in sysctl.conf itself].

  
  Secondly, I propose a new 10-network-tuning.conf with:-
  ==
  # Allow ECN for outgoing connections.  Starting with 4.2, there is an adaptive
  # fallback [enabled by default tcp_ecn_fallback option] preventing connection
  # loss even with ecn enabled, also ecn-intolerance is increasingly very rare.
  net.ipv4.tcp_ecn=1
  ==

  I know there is a (small) chance of issues/regressions with ECN
  enabled by default on outgoing but I'm quite sure the issue is very
  rare, like others notice [ref: 1 and 2 below].  Apple's selective
  enablements etc. show this works just as much as my own use for years
  and many similar reports.

  ECN actually being used for outgoing connections really helps with
  latency-reduction with modern routers (both core and edge) using
  queuing disciplines fq_codel or otherwise, able to mark rather than
  drop packets on ECN-enabled flows [helps latency and realtime
  applications].  Now we are just past LTS release is in my view the
  'right time' to finally enable ECN [and obviously easy to revert!].
  If this is disputed, in ANY case I strongly suggest at the very least
  a commented-out ECN section should be included, but 'defaults
  matter'!.

  I was going to suggest a non-default section about
  net.core.default_qdisc [ LP #1436945 ] but this appears to have been
  fixed upstream similarly.

  [1] 
https://www.ietf.org/proceedings/98/slides/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00.pdf
  [2] http://seclists.org/nanog/2015/Jun/675

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Trent Lloyd]

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

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1772537] Re: Wrong combining sequence in Compose for the Finnish locale

[Miikka-Markus Alhonen]

I filed the report upstream at:
https://bugs.freedesktop.org/show_bug.cgi?id=106649

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

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

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in libx11 package in Ubuntu:
  Triaged

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Dimitri John Ledkov]

Using 237-3ubuntu10.1, with 8.8.8.8 as DNS server, the resolutions of 
nonexistant.ubuntu.com and secure.ubuntu.com both are retried with following 
messages in the journal:
systemd-resolved[1434]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

With 237-3ubuntu10, a similar message only appeared for
"secure.ubuntu.com" NXDOMAIN query, but not for the
nonexistant.ubuntu.com.


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

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1768615] xserver.devices.txt

[Tomáš Klos]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144210/+files/xserver.devices.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1 

[Touch-packages] [Bug 1768615] xdpyinfo.txt

[Tomáš Klos]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144209/+files/xdpyinfo.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] XorgLogOld.txt

[Tomáš Klos]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144207/+files/XorgLogOld.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] Xrandr.txt

[Tomáš Klos]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1768615/+attachment/5144208/+files/Xrandr.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] XorgLog.txt

[Tomáš Klos]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144206/+files/XorgLog.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 

[Touch-packages] [Bug 1768615] ProcModules.txt

[Tomáš Klos]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144204/+files/ProcModules.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1 

[Touch-packages] [Bug 1768615] UdevDb.txt

[Tomáš Klos]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1768615/+attachment/5144205/+files/UdevDb.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] ProcEnviron.txt

[Tomáš Klos]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144202/+files/ProcEnviron.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1 

[Touch-packages] [Bug 1768615] DpkgLog.txt

[Tomáš Klos]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144197/+files/DpkgLog.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 

[Touch-packages] [Bug 1768615] ProcCpuinfoMinimal.txt

[Tomáš Klos]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144201/+files/ProcCpuinfoMinimal.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] ProcCpuinfo.txt

[Tomáš Klos]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144200/+files/ProcCpuinfo.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1 

[Touch-packages] [Bug 1768615] ProcInterrupts.txt

[Tomáš Klos]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1768615/+attachment/5144203/+files/ProcInterrupts.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   

[Touch-packages] [Bug 1768615] Lspci.txt

[Tomáš Klos]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1768615/+attachment/5144198/+files/Lspci.txt

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1