[Touch-packages] [Bug 1773516] Re: Right click not working on Lenovo touchpad

[Christopher M. Penalver]

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

1) To clarify, how are you attempting to right click, tapping two
fingers on the clickpad, clicking the bottom right area of the clickpad?

2) If you boot into a kernel from 17.10 does right clicking work again?

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

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

** Summary changed:

- Right click not working on Lenovo touchpad
+ [Lenovo Yoga 300-11IBY] Right click not working

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  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

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

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

[Touch-packages] [Bug 1773516] Re: Right click not working on Lenovo touchpad

[Christopher M. Penalver]

** Tags added: latest-bios-c0cn31ww

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  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

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

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

[Touch-packages] [Bug 1773531] Re: graphics driver incssat728onsisten

[Christopher M. Penalver]

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

1) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

If after HWE stack updating this issue is still reproducible:

2) Could you please provide a screenshot of the issue?

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

** Tags added: bios-outdated-a07

** 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/1773531

Title:
  graphics driver incssat728onsisten

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  VGA driver is inconsistent. Most of the probable boot up goes with
  flickering and failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 26 14:42:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 1440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0K138P
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1440
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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

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

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

[Touch-packages] [Bug 1773544] Re: some bug you should see

[Christopher M. Penalver]

Mário Luiz Mendes de Araujo Junior, thank you for taking the time to
report this and helping to make Ubuntu better. Unfortunately, this
report didn't include enough information. You may find it helpful to
read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem,
2. The behavior you expected, and
3. The behavior you actually encountered (in as much detail as possible).

Thank you for your help.

** Tags added: bios-outdated-1.2.7

** 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/1773544

Title:
  some bug you should see

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  some bug you should see

  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..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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
  CompositorRunning: None
  Date: Sat May 26 11:34:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2018-05-20 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7c6c9274-21e1-4431-a45a-58d29ca5b059 ro acpi=off quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0P2WW4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/16/2017:svnDellInc.:pnInspiron7559:pvr1.2.3:rvnDellInc.:rn0P2WW4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
   
   
   ERROR: Error querying connected displays on GPU 0 (Missing Extension).
  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.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
  xserver.bootTime: Sun May 20 22:26:41 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Touch-packages] [Bug 1773575] Re: dual vga

[Christopher M. Penalver]

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

1) Regarding your Bug Description:
>"i tried to update the drivers in one way or another..."

This is not enough information. Could you please advise what you did
precisely, in a keyboard click-for-click fashion?

2) Are there any crash files in the /var/crash folder?

3) As per your logs, you install unsupported software (PPA) and have
installed the nvidia proprietary drivers when you don't have a nvidia
card installed. Hence, after removing all PPAs and the nvidia drivers,
and rebooting does this allow you to use the GUI?

** Tags added: latest-bios-a14

** 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/1773575

Title:
  dual vga

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C46Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue May 22 09:07:33 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 927 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: Login screen not moved to used monitor

[Christopher M. Penalver]

Manfred Steiner:

To advise, this report will only be scoped to one issue. With this in mind, in 
this report you have noted the following disparate problems:
1) As per your Bug Description, going from 16.04 to 18.04, where the monitor 
the login screen and system bar shows up on changed from where the cursor the 
monitor is on while booting up to the main monitor.
2) As per comment #3: "but does not help the first time, when no configuration 
was done".
3) As per comment #3: (or it falls back to the starting situation).
4) As per comment #3, going from 16.04 to 18.04, the monitor connected through 
the i-tec adapter is not automatically detected, requiring you to have the 
connect the i-tec adapter while the displays dialog is open.
5) As per comment #3: "A second minor problem when using this adapter is a 
mouse flickering effect."

Of the 5 disparate issues above, which one issue did you want this
report to focus on?

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

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

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: Login screen not moved to used monitor

[Manfred Steiner]

Question 1) Monitor is plugged in on standard VGA connector (15 pin
D-Sub). I guess it does not matter which monitor type. I have done it
with a Ilyama ProLite G2773HS and a Samsung Syncmaster S24B350 monitor.

As soon as the monitors are configured, for example the external monitor
as replacement for the built in LCD-display of a notebook, the system
detects this configuration next time automatically and is switching to
the proper monitor configuration, also for the login-screen. This
behavior is fine, but does not help the first time, when no
configuration was done (or it falls back to the starting situation).

Question 2) I am using the P/N: U3DUALADA (barcode D16-00352296).

Question 3) As HDMI monitor I am using the Samsung Syncmaster S24B35

Question 4) Using the i-tec adapter for the additional Samsung
Syncmaster S24B350 monitor was working without any problems on Ubuntu
16.04. On Ubuntu 18.04 monitor configuration is not automatically
detected. As work-arround I open the configuration->devices->displays
dialog. If this dialog is open and I reconnect the i-tec adapter, the
system offers now configuration possibilities. This must be done every
time the adpater is connected to the system. A second minor problem when
using this adapter is a mouse flickering effect. When mouse icon
changes, it mouse icon disappears completely for a short time. When
disconnecting the adapter system finds back to the default monitor
situation without problems.

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

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

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

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

[Touch-packages] [Bug 1168892] Re: Special characters like "&" are well posted but not seen on the Friends application

[Launchpad Bug Tracker]

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

** Changed in: friends-app (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Special characters like "&" are well posted but not seen on the
  Friends application

Status in Friends:
  Invalid
Status in friends-app package in Ubuntu:
  Expired

Bug description:
  Hello,

  I know Friends is just in the early beginning of development and that
  you work actively on it, so it's normal that lots of features from
  Gwibber are missing (like managing on Friends window someone's
  timeline, (un)-subscribe, having links automatically reduced with
  ur1.ca or others, perhaps multi-columns etc...), they will come one by
  one in the next weeks, so I won't report bugs from that.

  But there are some "problems" that are real bugs. Here is one :

  When I add a special character like "&" (symbol for "and") in the
  compose message window for Identica, no problem in the writing, it
  shows well and is counted as 1.

  But after message has been sent, on Friends interface the "&" and all
  the characters after it don't appear on the message, this one is not
  complete.

  It's only a problem of viewing in Friends, because on Identica the
  whole message is well posted without error (see screenshot with the 3
  steps).

  Thanks !

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

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

[Touch-packages] [Bug 1743553] Re: [Typo] Missing word in Zesty Man Page for e4defrag

[David Britton]

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

** No longer affects: ubuntu-manpage-repository

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

Title:
  [Typo] Missing word in Zesty Man Page for e4defrag

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Location: First sentence, second paragraph, Notes section.
  http://manpages.ubuntu.com/manpages/zesty/man8/e4defrag.8.html

  Original: "It safe to run e4defrag on a file  while  it  is  actively
  in  use  by another  application."

  Text should state "It is safe to run..."

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

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

[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Marc Peña]

I would like to test this configuration in my laptop with a slow
rotational disk + a small SSD:
https://raid6.com.au/posts/fs_ext4_external_journal_caveats/

But, if I understood correctly, I need to configure journal_async_commit
for it to be reliable, and that option automatically enables
journal_checksum, that it's not available in the current e2fsprogs
version that ubuntu 16.04 has...am I missing something?

I also think that what Simon comments about the SRU is quite sensible,
but if getting a SRU is too hard, would it make sense to open a ticket
requesting a backport from bionic to xenial?

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

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

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

[Touch-packages] [Bug 1773590] Re: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other in

[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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1773590

Title:
  package libperl5.26 5.26.1-6 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz',
  which is different from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  no install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  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: Sat May 26 23:50:50 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-vprxfh/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-05-19 (6 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: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773590] [NEW] package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other

[Boyington]

Public bug reported:

no install

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6
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: Sat May 26 23:50:50 2018
DuplicateSignature:
 package:libperl5.26:5.26.1-6
 Unpacking libperl5.26:i386 (5.26.1-6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-vprxfh/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
InstallationDate: Installed on 2018-05-19 (6 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: perl
Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libperl5.26 5.26.1-6 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz',
  which is different from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  no install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  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: Sat May 26 23:50:50 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-vprxfh/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-05-19 (6 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: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1596248] Re: [Dell XPS 13 9343] Touchpad stops working occasionally

[Christopher M. Penalver]

Kevin Dalley, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:

1) To clarify, you regarding your self-compiled xserver-xorg-input-
synaptics, is that considered a WORKAROUND to the scope of this report?
If so, could you please provide the steps precisely you used in this
report (not provide a URL)?

2) Regarding your Bug Description "Occasionally, my cursor stops
following my mouse movements.":

2a) How often is occasionally, once a minute, once a day, etc.?

2b) Does this issue happen when using an external USB mouse?

2c) Is this issue influenced by how many fingers you have on the
touchpad, where on the touchpad you touch, what gesture you are using,
etc.?

3) 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?

** Summary changed:

- Touchpad stops working occasionally
+ [Dell XPS 13 9343] Touchpad stops working occasionally

** Tags added: latest-bios-a15

** 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/1596248

Title:
  [Dell XPS 13 9343] Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  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.:bvrA07:bd11/11/2015: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.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 

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

[Frank Winklmeier]

Sure, no problem. Separate bug for 16.04 created:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1773581

-- 
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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Christopher M. Penalver]

Kevin Dalley:

1) To advise, you will not want to manually attach crash reports. This
is due to how they may contain sensitive information you would not want
to release publicly.

2) Regarding those crash reports, in order to process them automatically and in 
a privacy respectful way, it is best to execute the following via a terminal on 
each crash report:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is replaced with the actual file name.

3) Regarding i915.i915_enable_rc6=1 could you please advise to:
* Why you were using it to begin with?
* Now that you removed it, do you have more/less/same issues?

4) To rule out left over update cruft and self-compiled programs, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?

** Attachment removed: 
"/var/crash/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144845/+files/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash

** Attachment removed: "/var/crash/_usr_sbin_unity-greeter.119.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144823/+files/_usr_sbin_unity-greeter.119.crash

** Attachment removed: "/var/crash/_usr_bin_xfce4-power-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144822/+files/_usr_bin_xfce4-power-manager.1000.crash

** Attachment removed: "/var/crash/_usr_bin_plasmashell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144821/+files/_usr_bin_plasmashell.1000.crash

** Attachment removed: "/var/crash/_usr_bin_kwin_wayland.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144820/+files/_usr_bin_kwin_wayland.1000.crash

** Attachment removed: "/var/crash/_usr_bin_ksplashqml.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144819/+files/_usr_bin_ksplashqml.1000.crash

** Description changed:

  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
+ 
+ WORKAROUND: Use GNOME Flashback (Metacity).
  
  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]
+  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
+  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: 

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

[Christopher M. Penalver]

Frank Winklmeier, it will help immensely if you use the computer the problem is 
reproducible with, and provide necessary debugging logs by filing a new report 
with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
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 1773575] [NEW] dual vga

[mustafa]

Public bug reported:

i have a laptop dell which has two vga one from intel and the other one
is amd. i tried to update the drivers in one way or another every thing
stoped and i can not use the gui anymore

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.1:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat May 26 22:00:13 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev 
ff) (prog-if ff)
InstallationDate: Installed on 2018-01-10 (136 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Inspiron 5521
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
dmi.bios.date: 07/31/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0C46Y8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A14
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 5521
dmi.product.version: A14
dmi.sys.vendor: Dell Inc.
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 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue May 22 09:07:33 2018
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 927 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages 
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/1773575

Title:
  dual vga

Status in xorg package in Ubuntu:
  New

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  

[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility

[Tritonio]

I run into this with Linux Mint 18.3 MATE. The workaround mentioned in
the description at the top works for me as well.

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

Title:
  Error formatting disk using disk utility

Status in DarGUI:
  New
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  You can work around this bug in gnome-disk-utility using these steps:

  * After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.

  * Delete the partition ("minus" icon)

  * Create a new partition

  [Test Case]

  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat 

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Jesse McNichol]

Similar problem for me. Dell E6530, Ubuntu 18.04

Downgraded to 4.13 headers as suggested above, disabled bluetooth in
BIOS as suggested by others. Neither workaround helped. Computer still
producing excess heat and systemd-udevd climbs to nearly 100% CPU usage
gradually from startup.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

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

[Kevin Dalley]

Thanks for your suggestions.

I just installed:
gnome-session-flashback

Working:
Gnome Flashback (Metacity)

not working:
Gnome Flashback (Compiz)


And a new item in /var/crash:

** Attachment added: 
"/var/crash/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144845/+files/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash

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

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Since filing this bug, I have been successfully using lxdm as a worked
around, with lxde

Recently, after I open this bug, I built my own version of

xserver-xorg-input-synaptics

following the instructions here:
https://askubuntu.com/questions/462135/touchpad-issue-jumping-cursor-while-typing-ubuntu-14-04-syndaemon-dont-help

That solved the problem with using the touchpad, but did not affect
lightdm.

I have some other programs I built myself, digikam, for example.
I suspect that none of the others are at fault, but I'm not positive.

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

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 1770374] Re: My login screen stays black

[Christopher M. Penalver]

Dieter Meyer, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770374/comments/3
regarding this being resolved with 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: Incomplete => 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/1770374

Title:
  My login screen stays black

Status in xorg package in Ubuntu:
  Invalid

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Since filing this bug, I have been successfully using lxdm as a worked
around, with lxde

Recently, after I open this bug, I built my own version of

xserver-xorg-input-synaptics

following the instructions here:
https://askubuntu.com/questions/462135/touchpad-issue-jumping-cursor-while-typing-ubuntu-14-04-syndaemon-dont-help

That solved the problem with using the touchpad, but did not affect
lightdm.

I have some other programs I built myself, digikam, for example.
I suspect that none of the others are at fault, but I'm not positive.

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

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 1773556] Re: systemd does not work with escaped paths

[Nyyr]

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773556/+attachment/5144824/+files/SystemdFailedUnits.txt

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

Title:
  systemd does not work with escaped paths

Status in systemd package in Ubuntu:
  New

Bug description:
  Cannot start systemd service using paths with spaces:

  systemd unit file content:
  [Unit]
  Description=LocalView UPS monitoring service

  [Service]
  Type=forking
  WorkingDirectory=/usr-Socomec\x20UPS-LocalView
  ExecStart=/usr-Socomec\x20UPS-LocalView-StartApp.sh

  [Install]
  WantedBy=multi-user.target

  Although systemd-escape converts "/usr/Socomec UPS/LocalView" path to 
usr-Socomec\x20UPS-LocalView,
  systemd complains it is not an absolute path when the '/' in front of it is 
missing in the unit file:

  systemd[1]: /etc/systemd/system/localview.service:6: Working directory
  path 'usr-Socomec\x20UPS-LocalView' is not absolute.

  The same applies for ExecStart entry.

  When the syntax check was satisfied I tried to run the service:

  systemd[11574]: localview.service: Changing to the requested working 
directory failed: No such file or directory
  systemd[11574]: localview.service: Failed at step CHDIR spawning /usr-Socomec 
UPS-LocalView-StartApp.sh: No such file or directory

  # ll "/usr/Socomec UPS/LocalView/StartApp.sh"
  -rwx--x--x 1 root root 220 kvě 26 17:27 '/usr/Socomec 
UPS/LocalView/StartApp.sh'*

  Unescaped path in the unit file obviously does not work either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May 26 18:53:31 2018
  InstallationDate: Installed on 2018-05-25 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cc5a6c33-5b50-42bf-adc9-d3f8e8dd328e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11e
  dmi.board.name: EP45-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11e:bd09/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1773556] Re: systemd does not work with escaped paths

[Nyyr]

** Attachment removed: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773556/+attachment/5144807/+files/SystemdFailedUnits.txt

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

Title:
  systemd does not work with escaped paths

Status in systemd package in Ubuntu:
  New

Bug description:
  Cannot start systemd service using paths with spaces:

  systemd unit file content:
  [Unit]
  Description=LocalView UPS monitoring service

  [Service]
  Type=forking
  WorkingDirectory=/usr-Socomec\x20UPS-LocalView
  ExecStart=/usr-Socomec\x20UPS-LocalView-StartApp.sh

  [Install]
  WantedBy=multi-user.target

  Although systemd-escape converts "/usr/Socomec UPS/LocalView" path to 
usr-Socomec\x20UPS-LocalView,
  systemd complains it is not an absolute path when the '/' in front of it is 
missing in the unit file:

  systemd[1]: /etc/systemd/system/localview.service:6: Working directory
  path 'usr-Socomec\x20UPS-LocalView' is not absolute.

  The same applies for ExecStart entry.

  When the syntax check was satisfied I tried to run the service:

  systemd[11574]: localview.service: Changing to the requested working 
directory failed: No such file or directory
  systemd[11574]: localview.service: Failed at step CHDIR spawning /usr-Socomec 
UPS-LocalView-StartApp.sh: No such file or directory

  # ll "/usr/Socomec UPS/LocalView/StartApp.sh"
  -rwx--x--x 1 root root 220 kvě 26 17:27 '/usr/Socomec 
UPS/LocalView/StartApp.sh'*

  Unescaped path in the unit file obviously does not work either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May 26 18:53:31 2018
  InstallationDate: Installed on 2018-05-25 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cc5a6c33-5b50-42bf-adc9-d3f8e8dd328e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11e
  dmi.board.name: EP45-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11e:bd09/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

[aleandro]

Bug is still present in ubuntu 18.04.

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions

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

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

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_xfce4-power-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144822/+files/_usr_bin_xfce4-power-manager.1000.crash

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

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_plasmashell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144821/+files/_usr_bin_plasmashell.1000.crash

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

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_sbin_unity-greeter.119.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144823/+files/_usr_sbin_unity-greeter.119.crash

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

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

** Attachment added: "/var/crash/_usr_bin_kwin_wayland.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144820/+files/_usr_bin_kwin_wayland.1000.crash

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

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 1770306] Re: X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

After removing:

i915.i915_enable_rc6=1

I still have problems.

I'll attach a few files from /var/crash


** Attachment added: "From /var/crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144819/+files/_usr_bin_ksplashqml.1000.crash

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

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 1773517] Re: lightdm takes too long to show up

[Launchpad Bug Tracker]

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

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

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

Title:
  lightdm takes too long to show up

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04.4 with multiarch support. When I start the
  laptop it boots well till it reaches the lightdm screen. When the
  login text appears, screen goes black about 1.5-2 minutes then lightdm
  screen shows up. I have three users, I noticed that each user takes 25
  seconds timeout to complete the process.

  journalctl -b0 _SYSTEMD_UNIT=lightdm.service
  
  -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 
MSK. --
  May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1001: Timeout was reached
  May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1000: Timeout was reached
  May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User64055: Timeout was reached
  May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error 
getting user list from org.freedesktop.Accounts: Timeout was reached
  May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" was met by user ""
  May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened 
for user  by (uid=0)

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

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

[Touch-packages] [Bug 1773556] [NEW] systemd does not work with escaped paths

[Nyyr]

Public bug reported:

Cannot start systemd service using paths with spaces:

systemd unit file content:
[Unit]
Description=LocalView UPS monitoring service

[Service]
Type=forking
WorkingDirectory=/usr-Socomec\x20UPS-LocalView
ExecStart=/usr-Socomec\x20UPS-LocalView-StartApp.sh

[Install]
WantedBy=multi-user.target

Although systemd-escape converts "/usr/Socomec UPS/LocalView" path to 
usr-Socomec\x20UPS-LocalView,
systemd complains it is not an absolute path when the '/' in front of it is 
missing in the unit file:

systemd[1]: /etc/systemd/system/localview.service:6: Working directory
path 'usr-Socomec\x20UPS-LocalView' is not absolute.

The same applies for ExecStart entry.

When the syntax check was satisfied I tried to run the service:

systemd[11574]: localview.service: Changing to the requested working directory 
failed: No such file or directory
systemd[11574]: localview.service: Failed at step CHDIR spawning /usr-Socomec 
UPS-LocalView-StartApp.sh: No such file or directory

# ll "/usr/Socomec UPS/LocalView/StartApp.sh"
-rwx--x--x 1 root root 220 kvě 26 17:27 '/usr/Socomec 
UPS/LocalView/StartApp.sh'*

Unescaped path in the unit file obviously does not work either.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat May 26 18:53:31 2018
InstallationDate: Installed on 2018-05-25 (1 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cc5a6c33-5b50-42bf-adc9-d3f8e8dd328e ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11e
dmi.board.name: EP45-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11e:bd09/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug bionic

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

Title:
  systemd does not work with escaped paths

Status in systemd package in Ubuntu:
  New

Bug description:
  Cannot start systemd service using paths with spaces:

  systemd unit file content:
  [Unit]
  Description=LocalView UPS monitoring service

  [Service]
  Type=forking
  WorkingDirectory=/usr-Socomec\x20UPS-LocalView
  ExecStart=/usr-Socomec\x20UPS-LocalView-StartApp.sh

  [Install]
  WantedBy=multi-user.target

  Although systemd-escape converts "/usr/Socomec UPS/LocalView" path to 
usr-Socomec\x20UPS-LocalView,
  systemd complains it is not an absolute path when the '/' in front of it is 
missing in the unit file:

  systemd[1]: /etc/systemd/system/localview.service:6: Working directory
  path 'usr-Socomec\x20UPS-LocalView' is not absolute.

  The same applies for ExecStart entry.

  When the syntax check was satisfied I tried to run the service:

  systemd[11574]: localview.service: Changing to the requested working 
directory failed: No such file or directory
  systemd[11574]: localview.service: Failed at step CHDIR spawning /usr-Socomec 
UPS-LocalView-StartApp.sh: No such file or directory

  # ll "/usr/Socomec UPS/LocalView/StartApp.sh"
  -rwx--x--x 1 root root 220 kvě 26 17:27 '/usr/Socomec 
UPS/LocalView/StartApp.sh'*

  Unescaped path in the unit file obviously does not work either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May 26 18:53:31 2018
  InstallationDate: Installed on 2018-05-25 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cc5a6c33-5b50-42bf-adc9-d3f8e8dd328e ro quiet splash vt.handoff=1
 

[Touch-packages] [Bug 1773515] Re: apparmour fails after removal of snapd

[daniel CURTIS]

Hello Dale.

It seems, that I've had the same/similar problem with AppArmor and
'usr.lib.snapd.snap-confine.real' profile [1]. The strange thing was,
that I couldn't change the enforcement mode for any profile! For example
Firefox etc.

Please edit this profile and check if this line is commented. If it
isn't then You can do this by adding '#' etc.:

- include "/var/lib/snapd/apparmor/snap-confine"
+ #include "/var/lib/snapd/apparmor/snap-confine"

Next, reboot system or reload AppArmor service. In my case, commenting
an include '/var/lib/snapd/apparmor/snap-confine.d' line, fixed this
issue, which seems to be similar to your problem. However, it should be
fixed via 'snapd' package update but I don't remember if there was such
an update. Anyway, I hope it will help You.

Thanks, best regards.
_
[1] https://lists.ubuntu.com/archives/apparmor/2017-November/011330.html

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

Title:
  apparmour fails after removal of snapd

Status in apparmor package in Ubuntu:
  New

Bug description:
  $ sudo systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 2850 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 2850 (code=exited, status=123)

  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]:...fail!
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  May 26 10:36:35 ThisOne systemd[1]: Failed to start AppArmor initialization.

  $ sudo apt-get install apparmor-easyprof 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  apparmor-easyprof is already the newest version (2.12-4ubuntu5).
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

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

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

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

[Touch-packages] [Bug 1773549] [NEW] Pulse audio does not remember default sink

[Alfred Krohmer]

Public bug reported:

It seems like pulseaudio is picking the wrong audio sink as a default in
different scenarios.

On my computer I have the default onboard Intel HDA audio as well as a
USB headset. On the network, there is one pulse instance advertising
itself.

I always set the onboard audio as the default audio sink. However, after
every reboot or resume or `pulseaudio -k`, the wrong sink is picked (and
the one I set previously is *not* picked).

When I enable discovery of remote pulse instances, sometimes the one on
my network is picked as default, but sometimes my headset is picked
instead of the onboard sink. Then again, if I disable discovery
sometimes the onboard sink gets picked as default. There seems to be no
clear pattern on when it selects what.

I have even entered the following in /etc/pulse/default.pa:

set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
set-default-source 
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

But this doesn't have any effect at all.

I also noticed that *sometimes*, pulse updates the file at
`~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to point
to the correct audio sink that I selected in `pavucontrol`, but not
always. Even if I write to that file manually to select a default sink,
the file gets overwritten by pulse on the next start with the default
sink that it chose.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  devkid 3487 F pulseaudio
 /dev/snd/controlC2:  devkid 3487 F pulseaudio
 /dev/snd/pcmC0D0p:   devkid 3487 F...m pulseaudio
 /dev/snd/controlC0:  devkid 3487 F pulseaudio
CurrentDesktop: MATE
Date: Sat May 26 17:07:55 2018
ExecutablePath: /usr/bin/pulseaudio
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G43 (MS-7758)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7758
dmi.product.version: 1.0
dmi.sys.vendor: MSI
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2018-05-26T17:01:12.271701

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems like pulseaudio is picking the wrong audio sink as a default
  in different scenarios.

  On my computer I have the default onboard Intel HDA audio as well as a
  USB headset. On the network, there is one pulse instance advertising
  itself.

  I always set the onboard audio as the default audio sink. However,
  after every reboot or resume or `pulseaudio -k`, the wrong sink is
  picked (and the one I set previously is *not* picked).

  When I enable discovery of remote pulse instances, sometimes the one
  on my network is picked as default, but sometimes my headset is picked
  instead of the onboard sink. Then again, if I disable discovery
  sometimes the onboard sink gets picked as default. There seems to be
  no clear pattern on when it selects what.

  I have even entered the following in /etc/pulse/default.pa:

  set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
  set-default-source 
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

  But this doesn't have any effect at all.

  I also noticed that *sometimes*, pulse updates the file at
  `~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to
  point to the correct audio sink that I selected in `pavucontrol`, but
  not always. Even if I write to that file manually to select a default
  sink, the file gets overwritten by pulse on the next start with the
  default sink that it chose.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  

[Touch-packages] [Bug 1773548] Re: package libgcc1 (not installed) failed to install/upgrade: pre-dependency problem - not installing libgcc1:i386

[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 gccgo-4.9 in Ubuntu.
https://bugs.launchpad.net/bugs/1773548

Title:
  package libgcc1 (not installed) failed to install/upgrade: pre-
  dependency problem - not installing libgcc1:i386

Status in gccgo-4.9 package in Ubuntu:
  New

Bug description:
  libgcc1   not able to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgcc1 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  Architecture: i386
  Date: Sat May 26 20:17:34 2018
  DuplicateSignature: package:libgcc1:(not installed):pre-dependency problem - 
not installing libgcc1:i386
  ErrorMessage: pre-dependency problem - not installing libgcc1:i386
  InstallationDate: Installed on 2018-05-22 (3 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  RelatedPackageVersions:
   dpkg N/A
   apt  N/A
  SourcePackage: gccgo-4.9
  Title: package libgcc1 (not installed) failed to install/upgrade: 
pre-dependency problem - not installing libgcc1:i386
  UpgradeStatus: Upgraded to trusty on 2018-05-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1773548/+subscriptions

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

[Touch-packages] [Bug 1773548] [NEW] package libgcc1 (not installed) failed to install/upgrade: pre-dependency problem - not installing libgcc1:i386

[anshul rajput]

Public bug reported:

libgcc1   not able to install

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgcc1 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
Architecture: i386
Date: Sat May 26 20:17:34 2018
DuplicateSignature: package:libgcc1:(not installed):pre-dependency problem - 
not installing libgcc1:i386
ErrorMessage: pre-dependency problem - not installing libgcc1:i386
InstallationDate: Installed on 2018-05-22 (3 days ago)
InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
RelatedPackageVersions:
 dpkg N/A
 apt  N/A
SourcePackage: gccgo-4.9
Title: package libgcc1 (not installed) failed to install/upgrade: 
pre-dependency problem - not installing libgcc1:i386
UpgradeStatus: Upgraded to trusty on 2018-05-25 (1 days ago)

** Affects: gccgo-4.9 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package dist-upgrade i386 trusty

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

Title:
  package libgcc1 (not installed) failed to install/upgrade: pre-
  dependency problem - not installing libgcc1:i386

Status in gccgo-4.9 package in Ubuntu:
  New

Bug description:
  libgcc1   not able to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgcc1 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  Architecture: i386
  Date: Sat May 26 20:17:34 2018
  DuplicateSignature: package:libgcc1:(not installed):pre-dependency problem - 
not installing libgcc1:i386
  ErrorMessage: pre-dependency problem - not installing libgcc1:i386
  InstallationDate: Installed on 2018-05-22 (3 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  RelatedPackageVersions:
   dpkg N/A
   apt  N/A
  SourcePackage: gccgo-4.9
  Title: package libgcc1 (not installed) failed to install/upgrade: 
pre-dependency problem - not installing libgcc1:i386
  UpgradeStatus: Upgraded to trusty on 2018-05-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1773548/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Frank Winklmeier]

I am seeing the exact same problem on a Samsung NP900X3G after the most
recent kernel update for Ubuntu 16.04. It works fine on 4.13.0-41 but
with 4.13.0-43 I am seeing the same horizontal lines as Thomas. Maybe
this helps to find where the problem got introduced.

-- 
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 1773544] [NEW] some bug you should see

[Mário Luiz Mendes de Araujo Junior]

Public bug reported:

some bug you should see

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..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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
CompositorRunning: None
Date: Sat May 26 11:34:06 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 530 [1028:0706]
   Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
InstallationDate: Installed on 2018-05-20 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7559
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7c6c9274-21e1-4431-a45a-58d29ca5b059 ro acpi=off quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0P2WW4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/16/2017:svnDellInc.:pnInspiron7559:pvr1.2.3:rvnDellInc.:rn0P2WW4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7559
dmi.product.version: 1.2.3
dmi.sys.vendor: Dell Inc.
nvidia-settings:
 ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
 
 
 ERROR: Error querying connected displays on GPU 0 (Missing Extension).
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.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
xserver.bootTime: Sun May 20 22:26:41 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

** 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/1773544

Title:
  some bug you should see

Status in xorg package in Ubuntu:
  New

Bug description:
  some bug you should see

  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..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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
  CompositorRunning: None
  Date: Sat May 26 11:34:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2018-05-20 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

[dualshock3nerd]

A whole year later I'm still affected by this bug with Kubuntu 18.04.
No volume notification shows up in kde but audio playback still skips about 
once or twice in in a couple of minutes like headphones just got plugged in and 
then immediately taken out.
No headphones were plugged in at any time by the way.

Workaround in comment #20 still works.

My sound card:
(lspci) Audio device: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller (rev 04)
(aplay -L) HDA Intel PCH, ALC898 Analog

I never used Windows on this machine so I can't rule out the possibility
that this is actually a hardware problem.

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

Title:
  Volume notification keeps popping up constantly (the notify-OSD bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1773531] [NEW] graphics driver incssat728onsisten

[sathish]

Public bug reported:

VGA driver is inconsistent. Most of the probable boot up goes with
flickering and failed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat May 26 14:42:11 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
InstallationDate: Installed on 2018-05-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Inspiron 1440
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0K138P
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1440
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 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

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


** Tags: amd64 apport-bug compiz-0.9 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/1773531

Title:
  graphics driver incssat728onsisten

Status in xorg package in Ubuntu:
  New

Bug description:
  VGA driver is inconsistent. Most of the probable boot up goes with
  flickering and failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 26 14:42:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 1440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0K138P
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1440
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Matt Caswell]

This issue still seems to be a problem in 18.04.

If found a solution:
https://askubuntu.com/questions/1040539/how-do-i-get-ufw-to-start-on-boot/1040584

I edited /lib/systemd/system/ufw.service as follows:

$ diff -u ufw.service.orig ufw.service
--- ufw.service.orig2018-05-26 13:45:48.696356561 +0100
+++ ufw.service 2018-05-26 14:17:22.030681670 +0100
@@ -2,7 +2,7 @@
 Description=Uncomplicated firewall
 Documentation=man:ufw(8)
 DefaultDependencies=no
-Before=network.target
+After=network-pre.target

 [Service]
 Type=oneshot

According to this page

https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

the network-pre.target has this purpose:

"It's primary purpose is for usage with firewall services that want to
establish a firewall before any network interface is up"

Making the above change solves the problem so that ufw does seem to
start up after boot. Is it a bug that ufw.service is not setup this way
to start with?

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

Title:
  ufw does not start automatically at boot

Status in ufw package in Ubuntu:
  New

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab

[Glenn J. Schworak]

I am experiencing the exact same issue with a fresh install of Ubuntu
18.04. Five other machines on the same network with the same NFS mount
are not experiencing the issue. Three are 18.04 but were upgraded from
14.04 or 16.04 and the other two are on 16.04 and were upgraded from
12.04 and will soon be upgraded to 18.04.

I have reinstalled 18.04 from scratch twice on the new box and each time
the same issue happens. The NFS fails to mount using /etc/fstab.

The temporary fix is to use the crontab to mount shortly after boot.

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

Title:
  NFS share does not mount on boot using fstab

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen?

  I want an NFS share to be mounted on startup using

  
  192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ 
/media/captainplanet/banane/ nfs rw 0 0

  What happened instead?

  It does not mount on startup. Systemd waits 91sec instead and finally
  starts after failing.

  I can successfully mount the NFS share with

  sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575
  /media/captainplanet/banane/

  When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS
  share manually before shutdown fixes the second problem.

  
  Do you need more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  2 23:10:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DM003XUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JFET44WW(1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DM003XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DM003XUK
  dmi.product.version: ThinkPad S3 Yoga 14
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1039599] Re: package libxslt1.1 1.1.26-8ubuntu1 [modified: usr/share/doc/libxslt1.1/changelog.Debian.gz] failed to install/upgrade: libxslt1.1:amd64 1.1.26-8ubuntu1 cannot be con

[Mattia Rizzolo]

There used to be some multiarch issues that have since been fixed,
closing.

** Changed in: libxslt (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package libxslt1.1 1.1.26-8ubuntu1 [modified:
  usr/share/doc/libxslt1.1/changelog.Debian.gz] failed to
  install/upgrade: libxslt1.1:amd64 1.1.26-8ubuntu1 cannot be configured
  because libxslt1.1

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  It installed both the 32 bit and the 64 bit version of the file and
  now it gives me an error when I try to run sudo apt-get -f install

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libxslt1.1 1.1.26-8ubuntu1 [modified: 
usr/share/doc/libxslt1.1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  AptOrdering:
   libxslt1.1: Configure
   libxslt1.1: Configure
  Architecture: amd64
  Date: Tue Aug 21 09:27:39 2012
  DpkgTerminalLog:
   dpkg: error processing libxslt1.1 (--configure):
libxslt1.1:amd64 1.1.26-8ubuntu1 cannot be configured because 
libxslt1.1:i386 is in a different version (1.1.26-8ubuntu1.1)
  ErrorMessage: libxslt1.1:amd64 1.1.26-8ubuntu1 cannot be configured because 
libxslt1.1
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
  SourcePackage: libxslt
  Title: package libxslt1.1 1.1.26-8ubuntu1 [modified: 
usr/share/doc/libxslt1.1/changelog.Debian.gz] failed to install/upgrade: 
libxslt1.1:amd64 1.1.26-8ubuntu1 cannot be configured because libxslt1.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 661649] Re: package libxslt1.1 1.1.26-1ubuntu1 failed to install/upgrade: ErrorMessage: pakken libxslt1.1 er installert og satt opp fra før

[Mattia Rizzolo]

Sorry nobody had a chance at looking at this old bug.

both 10.04 and 10.10 are out of support for a long time, and I'm
positive the package installs/upgrades just fine on newer releases.

closing

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

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

Title:
  package libxslt1.1 1.1.26-1ubuntu1 failed to install/upgrade:
  ErrorMessage: pakken libxslt1.1 er installert og satt opp fra før

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  Upgrading to 10.10

  ProblemType: Package
  DistroRelease: Ubuntu 10.10
  Package: libxslt1.1 1.1.26-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Sat Oct 16 11:24:16 2010
  ErrorMessage: ErrorMessage: pakken libxslt1.1 er installert og satt opp fra 
før
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
(20100429.4)
  SourcePackage: libxslt
  Title: package libxslt1.1 1.1.26-1ubuntu1 failed to install/upgrade: 
ErrorMessage: pakken libxslt1.1 er installert og satt opp fra før

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

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

[Touch-packages] [Bug 1773526] [NEW] all kernels bug

[Zakharov Evgeniy]

Public bug reported:

Linux 4.16.12-041612-generic #201805251538 SMP Fri May 25 15:40:25 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

DELL INSPIRION 5547 i5-4210u
hybrid graph intel + amd
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT 
[Radeon R7 M260/M265 / M340/M360 / M440/M445]

any one can help?
at boot on all distributives and on all lasts kernels i see this two errors


1)ipmi:dmi: invalid offset 0(im not have any ipmi interface and installed 
software)
2)amdgpu: [powerplay] VBIOS did not find boot engine(this on all kernels)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
Uname: Linux 4.16.12-041612-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat May 26 14:38:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: kubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
   Subsystem: Dell Radeon R7 M260/M265 [1028:0640]
MachineType: Dell Inc. Inspiron 5547
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.12-041612-generic 
root=UUID=084e8cd8-bcda-4dd7-9cd3-24aae91aa541 ro quiet splash radeon.dpm=1 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 08KNCD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn08KNCD:rvrA00:cvnDellInc.:ct8:cvrA11:
dmi.product.family: 00
dmi.product.name: Inspiron 5547
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.92+git1805251830.c1f2d9~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805260730.79fe00~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805260730.79fe00~oibaf~b
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: linux-kernel-headers (Ubuntu)
 Importance: Undecided
 Status: New


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

** Package changed: xorg (Ubuntu) => linux-kernel-headers (Ubuntu)

** Summary changed:

- kernel bug
+ all kernels 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/1773526

Title:
  all kernels bug

Status in linux-kernel-headers package in Ubuntu:
  New

Bug description:
  Linux 4.16.12-041612-generic #201805251538 SMP Fri May 25 15:40:25 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  DELL INSPIRION 5547 i5-4210u
  hybrid graph intel + amd
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT 
[Radeon R7 M260/M265 / M340/M360 / M440/M445]

  any one can help?
  at boot on all distributives and on all lasts kernels i see this two errors

  
  1)ipmi:dmi: invalid offset 0(im not have any ipmi interface and installed 
software)
  2)amdgpu: [powerplay] VBIOS did not find boot engine(this on all kernels)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  Uname: Linux 4.16.12-041612-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat May 26 14:38:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: kubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
 Subsystem: Dell Radeon R7 M260/M265 [1028:0640]
  MachineType: Dell Inc. Inspiron 5547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.12-041612-generic 
root=UUID=084e8cd8-bcda-4dd7-9cd3-24aae91aa541 ro quiet splash radeon.dpm=1 
vt.handoff=1
  

[Touch-packages] [Bug 996791] Re: Xubuntu 12.04 extremely slow login

[kenn]

I am running Ubuntu 16.04.04, I am suffering from the same bug. I issued a new 
bug here https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517
I tried the patch at #17 but it's not applicable to new code, I don't know how 
to remove accountservice check.

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

Title:
  Xubuntu 12.04 extremely slow login

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  The core issue is that /usr/lib/accountsservice/accounts-daemon
  doesn't accept dbus messages on boot.

  The symptom to this problem is that, after successfulling entering
  your login information, the system takes about 85 seconds to boot.
  The real issue occuring is that /usr/lib/accountsservice/accounts-
  daemon isn't being started correctly by ligthdm.  The accounts-daemon
  wont accept dbus requests, and so the dbus timeout is hit during boot.

  Before I start, here is a run down on my machine/setup:
  Intel I7.
  Xubuntu 12.04.
  Encrypted home drive.
  Running compiz.

  Enabling the log files on lightdm, the follow warnings are displayed (Notice 
the times):
  [+11.58s] DEBUG: Greeter quit
  [+36.60s] WARNING: Could not call SetXSession: Timeout was reached
  [+61.63s] WARNING: Could not call FindUserByName: Timeout was reached
  [+61.63s] DEBUG: Dropping privileges to uid 1000
  [+61.63s] DEBUG: Restoring privileges
  [+86.65s] WARNING: Could not call FindUserByName: Timeout was reached

  If the /usr/lib/accountsservices/accounts-daemon is restarted, after
  the lightdm login screen is displayed, but before a login, then xfce
  will start immediately.  Otherwise boot times take about 87 seconds.

  Also, it was found that the program d-feet, is unable to retrive valid
  methods from /usr/lib/accountsservices/accounts-daemon before it is
  restarted.  After the deamon is restarted, all dbus methods are
  visuable and communicate correctly.

  For descussion on the problem, and a temporary fix, see the following thread:
  http://ubuntuforums.org/showthread.php?t=1970326

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

-- 
Mailing list: https://launchpad.net/~touch-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: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Daniel van Vugt]

5. Tell us what "can not see the image" means. Does that mean the window
is black? Can you send a photo?

-- 
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:
  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: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Daniel van Vugt]

Please also:

1. Send us output from running 'vainfo' on your machine.

2. Send us a description of the type of file that you can't play.

3. Send us output from running 'dpkg -l'

4. Try 'mpv' instead of 'totem'.

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

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

-- 
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:
  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 1773516] [NEW] Right click not working on Lenovo touchpad

[Phill]

Public bug reported:

The right click is not working on Lenovo Yoga touch pad after upgrade to
18.04, worked minutes before on 17.10.

I think it works on the Think Pad out-of-the-box (after upgrade from
17.10), if that helps.

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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat May 26 10:34:57 2018
DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
InstallationDate: Installed on 2018-01-18 (128 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 80M0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C0CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Mini
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J33995WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 300-11IBY
dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
dmi.product.family: IDEAPAD
dmi.product.name: 80M0
dmi.product.version: Lenovo YOGA 300-11IBY
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/1773516

Title:
  Right click not working on Lenovo touchpad

Status in xorg package in Ubuntu:
  New

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 

[Touch-packages] [Bug 1773517] [NEW] lightdm takes too long to show up

[kenn]

Public bug reported:

I am running Ubuntu 16.04.4 with multiarch support. When I start the
laptop it boots well till it reaches the lightdm screen. When the login
text appears, screen goes black about 1.5-2 minutes then lightdm screen
shows up. I have three users, I noticed that each user takes 25 seconds
timeout to complete the process.

journalctl -b0 _SYSTEMD_UNIT=lightdm.service

-- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 
MSK. --
May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1001: Timeout was reached
May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1000: Timeout was reached
May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User64055: Timeout was reached
May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error 
getting user list from org.freedesktop.Accounts: Timeout was reached
May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" was met by user ""
May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened 
for user  by (uid=0)

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

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

Title:
  lightdm takes too long to show up

Status in lightdm package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 16.04.4 with multiarch support. When I start the
  laptop it boots well till it reaches the lightdm screen. When the
  login text appears, screen goes black about 1.5-2 minutes then lightdm
  screen shows up. I have three users, I noticed that each user takes 25
  seconds timeout to complete the process.

  journalctl -b0 _SYSTEMD_UNIT=lightdm.service
  
  -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 
MSK. --
  May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1001: Timeout was reached
  May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1000: Timeout was reached
  May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User64055: Timeout was reached
  May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error 
getting user list from org.freedesktop.Accounts: Timeout was reached
  May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" was met by user ""
  May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened 
for user  by (uid=0)

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

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

[Touch-packages] [Bug 1773515] [NEW] apparmour fails after removal of snapd

[Dale]

Public bug reported:

$ sudo systemctl status apparmor
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s ago
 Docs: man:apparmor(7)
   http://wiki.apparmor.net/
  Process: 2850 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
 Main PID: 2850 (code=exited, status=123)

May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
May 26 10:36:35 ThisOne apparmor[2850]:...fail!
May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Failed with result 
'exit-code'.
May 26 10:36:35 ThisOne systemd[1]: Failed to start AppArmor initialization.

$ sudo apt-get install apparmor-easyprof 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
apparmor-easyprof is already the newest version (2.12-4ubuntu5).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

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

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

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

Title:
  apparmour fails after removal of snapd

Status in apparmor package in Ubuntu:
  New

Bug description:
  $ sudo systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 2850 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 2850 (code=exited, status=123)

  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]:...fail!
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  May 26 10:36:35 ThisOne systemd[1]: Failed to start AppArmor initialization.

  $ sudo apt-get install apparmor-easyprof 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  apparmor-easyprof is already the newest version (2.12-4ubuntu5).
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

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

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

-- 
Mailing list: https://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 1770374] Re: My login screen stays black

[Dieter Meyer]

And I moved all my data I needed via the terminal onto a external drive

On Sat, May 26, 2018, 11:25 Dieter Meyer  wrote:

> Hi Christopher thanks for the feedback but unfortunately I already
> uninstalled and reinstalled Ubuntu because this is my primary personal
> computer I needed a quick fix
>
> Sorry for the inconvenience
>
> Dieter Meyer
>
> On Sat, May 26, 2018, 07:05 Christopher M. Penalver <
> christopher.m.penal...@gmail.com> wrote:
>
>> 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 subscribed to the bug
>> report.
>> 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
>>
>

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

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

[Dieter Meyer]

Hi Christopher thanks for the feedback but unfortunately I already
uninstalled and reinstalled Ubuntu because this is my primary personal
computer I needed a quick fix

Sorry for the inconvenience

Dieter Meyer

On Sat, May 26, 2018, 07:05 Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> 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 subscribed to the bug
> report.
> 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
>

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

[Touch-packages] [Bug 1773511] [NEW] apt-get commands prints huge value of days while package update

[Pushpendra Kumar]

Public bug reported:

Below is the output of the command "sudo apt-get update" on my system:
[pushpi@PUSHPI-PC ~]sudo apt-get update 
Hit:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:3 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]   
Hit:4 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease   
Get:5 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[100 kB]
Get:6 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 
[62.3 kB]
Get:7 http://in.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 
[90.1 kB]
Get:8 http://in.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[37.2 kB]
Get:9 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 
Metadata [28.5 kB]
Get:10 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[72.2 kB]
Get:11 http://in.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 
Icons [9,836 B]
Get:12 http://in.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 
Icons [15.2 kB]
Get:13 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en 
[25.9 kB]
Get:14 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages [62.0 kB]
Get:15 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 
Metadata [204 B]
Get:16 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages 
[16.4 kB]
Get:17 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages [16.4 kB]
Get:18 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [62.0 kB]
Get:19 http://security.ubuntu.com/ubuntu bionic-security/universe 
Translation-en [8,216 B]
Get:20 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 
Metadata [2,456 B]
Get:21 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [27.2 kB]
Get:22 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 
Metadata [116 kB]
Get:23 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 
Icons [120 kB]
Get:24 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 
Icons [187 kB]
Fetched 1,226 kB in 213503982334601d 1h 30min 29s (0 B/s) 

Here number of days printed by command are: 213503982334601d . Which is
wrong it just took few seconds.

Not sure if it's real bug or it's my system clock which drifted across
update ???

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.1
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
CurrentDesktop: ubuntu:GNOME
Date: Sat May 26 14:46:11 2018
InstallationDate: Installed on 2018-04-15 (40 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  apt-get commands prints huge value of days while package update

Status in apt package in Ubuntu:
  New

Bug description:
  Below is the output of the command "sudo apt-get update" on my system:
  [pushpi@PUSHPI-PC ~]sudo apt-get update 
  Hit:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease
  Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Get:3 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]  
 
  Hit:4 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease  
 
  Get:5 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[100 kB]
  Get:6 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 
[62.3 kB]
  Get:7 http://in.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 
[90.1 kB]
  Get:8 http://in.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[37.2 kB]
  Get:9 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 
Metadata [28.5 kB]
  Get:10 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[72.2 kB]
  Get:11 http://in.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 
Icons [9,836 B]
  Get:12 http://in.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 
Icons [15.2 kB]
  Get:13 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en 
[25.9 kB]
  Get:14 http://in.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages [62.0 kB]
  Get:15 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 
Metadata [204 B]
  Get:16 http://security.ubuntu.com/ubuntu bionic-security/universe i386 
Packages [16.4 kB]
  Get:17 

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

[Christopher M. Penalver]

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

1) Regarding the VGA monitor, as per the sticker of the monitor itself
(not from the Bug Description, or the result of a terminal command),
could you please provide the full manufacturer and model?

2) Regarding the i-tec USB 3.0 Display Adapter could you please advise
to the full part number (ex. U3DUAL4KHDMI)?

3) Regarding the HDMI monitor, could you please provide the full
manufacturer and model?

4) If you unplug the i-tec device, and only use the VGA monitor, is this
detected in Settings > Devices > Displays? An alternative application to
this is arandr to rule out some app specific issue.

** 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/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

[Christopher M. Penalver]

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

1) Regarding non-default kernel boot parameter i915.i915_enable_rc6=1 is
this required? If you remove it, how does it affect this issue?

2) After you login, are there crash files in the /var/crash folder?

3) To confirm, if you install gnome-session-flashback and login to it
does this provide a WORKAROUND?

4) Do you have any self-compiled/unsupported software installed?

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  Incomplete

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] Re: Login screen not moved to used monitor

[Christopher M. Penalver]

** Tags added: bios-outdated-2.48 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/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 
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

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

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

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Christopher M. Penalver]

Roger Davis, could you please answer all the question previously asked
directly here in this report (not make duplicate reports or apport-
collect to this one)?

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  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.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 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:
  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
  

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

[Christopher M. Penalver]

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

** This bug has been marked a duplicate of bug 1772386
   message - Low Graphics mode - about 2/3 of startups - not all

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

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

-- 
Mailing list: https://launchpad.net/~touch-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, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/comments/4
regarding this being fixed by reinstalling. 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: Incomplete => 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/1771062

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

Status in xorg package in Ubuntu:
  Invalid

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:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/+subscriptions

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

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

[Lonnie Lee Best]

A clean install of 16.04 has fixed this issue for me.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/+subscriptions

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

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ Christian Ehrhardt ]

Thanks Stefan, updating the tags per former comment.

** 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 netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1767283

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Fix Committed
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * This worked in former relases, so from a LTS->LTS upgraders POV it is 
 an upgrade regression
   * The impact is that local source (-s) can no more be used as before
   * The fix is backporting the fix that we made in Debian (but without all 
 the noise of the arg parsing rewrite for SRU simplicity)

  [Test Case]

   * Run with local source port, like your local SSH for example:
   $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null

  [Regression Potential]

   * the Minimized change (compared to the big change that versions going 
 forward got) should be safe as it just allows a case that was formerly 
 forbidden in arg-parsing. Never the less there could be a regression if 
 one of those combinations causes an issue when ran where it formerly 
 just was denied on arg parse. Think a script that since Bionic fails 
 (due to this bug) but once enabled will "work" and DUE TO THAT might 
 then trigger actions that are an issue.
 Never the less, since currently in Bionic this just fails, I'd assume 
 the this is a rather theoretical risk - and being a regression to 
 former releases we should fix it to make LTS->LTS upgraders suffer 
 less.

  [Other Info]
   
   * n/a


  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  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
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions

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