[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread asi
Look for "dmsetup udevcomplete" call in udev rules. This is the sync point when 
libdevmapper continues. This must be the last call in udev chain rules related 
to device-mapper devices.
(Run cryptsetup with --debug and you will see that sync point.)

Sometimes it is hidden by the fact that libdevampper could fallback to
device internal nodes creation because it verifies that udev nodes were
created (the old way used when you compile it without udev support).

Just saying how upstream is designed to work.

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1781908] Re: upgrade

2018-09-14 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  upgrade

Status in mesa package in Ubuntu:
  Expired

Bug description:
  system doesn' work since last upgrade at 09th july 2018

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul 16 13:05:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] 
(prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. RS740 [Radeon 2100] [105b:0e22]
  InstallationDate: Installed on 2015-10-24 (995 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=368c9809-b472-47a9-9a0a-edf51a6218f8 ro plymouth:debug quiet splash 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A74ML 3.0/A74ML-K 3.0
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  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.:bvr080014:bd04/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA74ML3.0/A74ML-K3.0:rvr1.0: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.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul 16 15:01:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Keyboard KEYBOARD, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

2018-09-14 Thread Jeremy Bicha
https://launchpad.net/ubuntu/+source/pygobject/3.30.1-1

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

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in pygobject package in Ubuntu:
  Fix Released

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1787474/+subscriptions

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


[Touch-packages] [Bug 1792644] [NEW] If snapd is not working it can take down systemd

2018-09-14 Thread Henry Wertz
Public bug reported:

I'll start out with saying, this bug is probably priority "invalid" due
to my non-stock configuration (this 18.04.1 install is on an Acer
Chromebook 13, so it has a held back kernel and Xorg for the lovely
nvidia drivers it came with.) But I figure I'll file anyway since the
problem is rather serious if it arises on your particular system, and
the workaround/fix is easy once you figure out what the heck is
happening.

So, snapd has errored out since I updated to 18.04 due to my held back
kernel (snap packages are using xz compression, and this kernel has no
xz support...)  I found within the last day or so that my machine would
not boot to graphical environment, just to text login with no networking
up and several missing services (ntp and a few others.)  journalctl -xe
showed failures due to "file not found" on files like tr, cut, modprobe,
cat, that should definitely be found.  PATH problems!  Ultimately, I
found /usr/lib/systemd/system-environment-generators/snapd-env-generator
(which appears -- not sure since it's a binary instead of a shell script
-- to be intended to just add "/snap/bin" to the PATH.)I moved this
out of the folder, on reboot everything worked fine. Then I went ahead
and uninstalled snapd.

I suspect systemd is "too smart for it's own good", and instead of
providing it's own environment variables then letting items in
/usr/lib/systemd/system-environment-generators/ modify the environment
(as docs say), instead systemd either decided "snapd-env-generator" is
setting a PATH so systemd doesn't have to (resulting in PATH of
":/snap/bin") or systemd "rolled back" that PATH when snapd service
failed, resetting PATH to empty instead of the default PATH value.

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

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

Title:
  If snapd is not working it can take down systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  I'll start out with saying, this bug is probably priority "invalid"
  due to my non-stock configuration (this 18.04.1 install is on an Acer
  Chromebook 13, so it has a held back kernel and Xorg for the lovely
  nvidia drivers it came with.) But I figure I'll file anyway since the
  problem is rather serious if it arises on your particular system, and
  the workaround/fix is easy once you figure out what the heck is
  happening.

  So, snapd has errored out since I updated to 18.04 due to my held back
  kernel (snap packages are using xz compression, and this kernel has no
  xz support...)  I found within the last day or so that my machine
  would not boot to graphical environment, just to text login with no
  networking up and several missing services (ntp and a few others.)
  journalctl -xe showed failures due to "file not found" on files like
  tr, cut, modprobe, cat, that should definitely be found.  PATH
  problems!  Ultimately, I found /usr/lib/systemd/system-environment-
  generators/snapd-env-generator (which appears -- not sure since it's a
  binary instead of a shell script -- to be intended to just add
  "/snap/bin" to the PATH.)I moved this out of the folder, on reboot
  everything worked fine. Then I went ahead and uninstalled snapd.

  I suspect systemd is "too smart for it's own good", and instead of
  providing it's own environment variables then letting items in
  /usr/lib/systemd/system-environment-generators/ modify the environment
  (as docs say), instead systemd either decided "snapd-env-generator" is
  setting a PATH so systemd doesn't have to (resulting in PATH of
  ":/snap/bin") or systemd "rolled back" that PATH when snapd service
  failed, resetting PATH to empty instead of the default PATH value.

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

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


[Touch-packages] [Bug 1792643] [NEW] apport does not upload wayland or gnome-shell crash data

2018-09-14 Thread Frank Feuerbacher
Public bug reported:

 uname -a

Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

 lsb_release -rd 
Description:Ubuntu 18.04.1 LTS
Release:18.04

In trying to upload .crash data for bug 1789962 "gnome-shell segfaults
in Wayland when display is turned off while Kodi running" I determined
that apport-cli and friends were never able to upload the .crash files.
The URL where they should appear is:
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

Earlier, I did upload the .crash files directly and was told by the
defect reviewer that:

_usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols)
_usr_bin_gnome-shell.1000.crash: Stack trace is missing


 You can see the other bug for details, here is the last comment that I added 
(so far):

I deleted all entries in /var/crash and /var/lib/whoopsie.
I recreated the problem

ls -l /var/crash

total 92136
-rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 
_usr_bin_gnome-shell.1000.crash
-rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 _usr_bin_Xwayland.1000.crash
-rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 
_usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash

fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash

*** Error: Invalid problem report

No such file or directory

Press any key to continue...

fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (40.6 MB)
  E: Examine locally
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/E/V/K/I/C):
S

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
< Deleted lots and lots of ellipsis >


echo $?
0
total 4
ls -l /var/lib/whoopsie
-rw--- 1 root root 128 Sep 13 18:39 whoopsie-id

sudo cat /var/lib/whoopsie/whoopsie-id

39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

Checked the URL:
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

No entries since 08/11. None for wayland, gnome-shell or Kodi.
I checked for over 5 minutes.


So perhaps something is going bad on my end, but I just don't know what
or how to  debug.

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

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

Title:
  apport does not upload wayland or gnome-shell crash data

Status in apport package in Ubuntu:
  New

Bug description:
   uname -a

  Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

   lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  In trying to upload .crash data for bug 1789962 "gnome-shell segfaults
  in Wayland when display is turned off while Kodi running" I determined
  that apport-cli and friends were never able to upload the .crash
  files. The URL where they should appear is:
  
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  Earlier, I did upload the .crash files directly and was told by the
  defect reviewer that:

  _usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols)
  _usr_bin_gnome-shell.1000.crash: Stack trace is missing

  
   You can see the other bug for details, here is the last comment that I added 
(so far):

  I deleted all entries in /var/crash and /var/lib/whoopsie.
  I recreated the problem

  ls -l /var/crash

  total 92136
  -rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 
_usr_bin_gnome-shell.1000.crash
  -rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 
_usr_bin_Xwayland.1000.crash
  -rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 
_usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash

  fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash

  *** Error: Invalid problem report

  No such file or directory

  Press any key to continue...

  fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-09-14 Thread Martin Wildam
I wanted to try the
  update-crypto-policies --set LEGACY
but I am using Ubuntu 18.04.1 and I could not find an equivalent command.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server

2018-09-14 Thread Scott Moser
** Changed in: maas (Ubuntu Bionic)
   Status: New => Invalid

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

Title:
  Failure when using ssh with a locale that is not configured on the
  server

Status in base-files package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Invalid
Status in base-files source package in Bionic:
  Fix Released
Status in maas source package in Bionic:
  Invalid

Bug description:
  [impact]
  The setup:

  1) The user has LC_ALL set to a locale on their machine (or some other LC_* 
variable but it's usually LC_ALL).
  2) This locale does not exist on an Ubuntu server.
  3) The user sshes into the server.

  ssh (at least with the settings that are default on Debian and Ubuntu
  and Fedora) send the value of LC_ALL to the remote server, where the
  default settings on Ubuntu allow this to be set in the environment of
  the process it launches.

  Because we are now in a situation where LC_ALL is set to a value that
  is not valid for the system, various undesirable things happen,
  including ugly messages from cloud-init and perl complaining every
  time a perl process starts and the bug that the original description
  below describes.

  [test case]
  Configure the setup as described above. Ssh into the server and run "perl < 
/dev/null" and check for warnings.

  [regression potential]
  This adds a step to the startup of every login shell, which obviously is not 
entirely trivial. However, the new executable being invoked is very simple and 
even if it fails, the startup of the shell should not be inhibited.

  
  [original description]

  
  If LC_ALL is not set (which seems to be the default on a few server 
installations I've done now), mid way through installing, you get this 
backtrace and then the installation just hangs.  You can ctrl-c out of it but 
the package is left half configured.

  Traceback (most recent call last):
    File "/usr/bin/django-admin", line 5, in 
  management.execute_from_command_line()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 443, in execute_from_command_line
  utility.execute()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 382, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 196, in run_from_argv
  self.execute(*args, **options.__dict__)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 
90, in handle_noargs
  syncdb.Command().execute(**options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", 
line 57, in handle_noargs
  cursor = connection.cursor()
    File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", 
line 308, in cursor
  cursor = util.CursorWrapper(self._cursor(), self)
    File 
"/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py",
 line 177, in _cursor
  self.connection = Database.connect(**conn_params)
    File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in 
connect
  connection_factory=connection_factory, async=async)
  psycopg2.OperationalError: FATAL:  password authentication failed for user 
"maas"
  FATAL:  password authentication failed for user "maas"

  Related bugs:
   * bug 969462: [postgres] fails to start after install if invalid locale is 
set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions

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


[Touch-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-09-14 Thread Ludovic Rousseau
According to https://serverfault.com/questions/715064/failed-to-issue-
method-call-unit-failed-to-load-no-such-file-or-directory or
https://bugzilla.redhat.com/show_bug.cgi?id=955379 the error message you
have "Failed to issue method call: No such file or directory" comes from
systemd.

pcscd version 1.8.10 is from Ubuntu 14.04, an old Ubuntu version.
Are you trying to upgrade to Ubuntu 16.04? 18.04? something else?

** Bug watch added: Red Hat Bugzilla #955379
   https://bugzilla.redhat.com/show_bug.cgi?id=955379

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

Title:
  package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: pcscd 1.8.10-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  AptOrdering:
   pcscd: Install
   pcscd: Configure
  Architecture: amd64
  Date: Fri Jun 23 12:21:31 2017
  DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-28 (177 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pcsc-lite
  Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+subscriptions

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


[Touch-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-09-14 Thread Ludovic Rousseau
Diego, Kurt, Do you also have the problem if you do:
sudo apt install --reinstall pcscd

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

Title:
  package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: pcscd 1.8.10-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  AptOrdering:
   pcscd: Install
   pcscd: Configure
  Architecture: amd64
  Date: Fri Jun 23 12:21:31 2017
  DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-28 (177 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pcsc-lite
  Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+subscriptions

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread Dmitrii Shcherbakov
asi,

I would rule out the lack of rules because on both xenial and bionic we
have LVM udev rules with the following line that is supposed to create a
LUKS UUID-based symlink:`

ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in?h=ubuntu/xenial
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in?h=ubuntu/bionic

The above test have shown that the symlink gets created on bionic.

For xenial it seems to be the same but this test is different in terms
of CPU load present on a machine (there is no load in my tests now in
comparison to the situations based on which we filed this bug):

uname -a
Linux maas-vhost6 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

grep -RP ID_FS_UUID_ENC /lib/udev/rules.d/
/lib/udev/rules.d/60-persistent-storage-dm.rules:ENV{ID_FS_USAGE}=="filesystem|other|crypto",
 ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
/lib/udev/rules.d/60-persistent-storage.rules:ENV{ID_FS_USAGE}=="filesystem|other|crypto",
 ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
/lib/udev/rules.d/69-bcache.rules:ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
/lib/udev/rules.d/69-lvm-metad.rules:ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-id/lvm-pv-uuid-$env{ID_FS_UUID_ENC}"
/lib/udev/rules.d/63-md-raid-arrays.rules:ENV{ID_FS_USAGE}=="filesystem|other|crypto",
 ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

lsblk 
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:0064G  0 disk 
`-sda18:1064G  0 part /
sdb   8:16   0 8G  0 disk 
sdc   8:32   0 102.4M  0 disk 
sdd   8:48   0 102.4M  0 disk 
sde   8:64   0 102.4M  0 disk 
vda 253:00 102.4M  0 disk 
vdb 253:16   0 102.4M  0 disk 
nvme0n1 259:0020G  0 disk 
nvme1n1 259:1020G  0 disk 


tree /dev/disk/by-uuid/
/dev/disk/by-uuid/
└── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1

0 directories, 1 file

sudo cryptsetup luksFormat /dev/sdb

WARNING!

This will overwrite data on /dev/sdb irrevocably.

Are you sure? (Type uppercase yes): YES
Enter passphrase: 
Verify passphrase: 


ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/
/dev/disk/by-uuid/
├── 42bf3808-9987-454f-be27-5d6c9b9c5c12 -> ../../sdb
└── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1

0 directories, 2 files


sudo cryptsetup luksDump /dev/sdb | grep UUID
UUID:   42bf3808-9987-454f-be27-5d6c9b9c5c12

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

To manage notifications about this bug go to:

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-09-14 Thread John Pucciarelli
Any updates on this? I ran into this issue after upgrading from 16.04 to
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/1748839

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread asi
If you have properly installed device-mapper udev rules, cryptsetup is
internally synchronized to all symlinks and nodes creation (it should
never return only when udev is finished, that's why libdevmapper
internally uses semaphores and cookies per device).

Calling udev settle is just workaround for broken udev rules (or the
order of rules), you should never need that here...

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread Dmitrii Shcherbakov
As a hint on reproducing it, it may be a problem on xenial only (which
we used for that deployment) for clean devices.

On a bionic VM it seems like the symlink is created but it's not clear
if luksFormat returns before that symlink gets created or after - this
is the important part because the automation tries to use that symlink
right after `cryptsetup luksFormat ` exits.

tree /sys/class/block
https://paste.ubuntu.com/p/vhjjzdytH7/

uname -a
Linux maas-vhost6 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/
/dev/disk/by-uuid/
└── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1

0 directories, 1 file
ubuntu@maas-vhost6:~$ lsblk 
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:0064G  0 disk 
└─sda18:1064G  0 part /
sdb   8:16   0 8G  0 disk 
sdc   8:32   0 102.4M  0 disk 
sdd   8:48   0 102.4M  0 disk 
sde   8:64   0 102.4M  0 disk 
vda 252:00 102.4M  0 disk 
vdb 252:16   0 102.4M  0 disk 
nvme0n1 259:0020G  0 disk 
nvme1n1 259:1020G  0 disk 
ubuntu@maas-vhost6:~$ sudo cryptsetup luksFormat /dev/sdb 

WARNING!

This will overwrite data on /dev/sdb irrevocably.

Are you sure? (Type uppercase yes): YES
Enter passphrase for /dev/sdb: 
Verify passphrase: 

ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/
/dev/disk/by-uuid/
├── a82ddfe0-7de8-4c6c-aaca-a074f000b746 -> ../../sdb
└── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1

0 directories, 2 files


sudo cryptsetup luksFormat /dev/sdb 

WARNING!

This will overwrite data on /dev/sdb irrevocably.

Are you sure? (Type uppercase yes): YES
Enter passphrase for /dev/sdb: 
Verify passphrase: 


ubuntu@maas-vhost6:~$ sudo cryptsetup luksDump /dev/sdb | grep UUID
UUID:   21bacaf0-9eea-4809-9b1c-6f4d7e614f5b


ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/
/dev/disk/by-uuid/
├── 21bacaf0-9eea-4809-9b1c-6f4d7e614f5b -> ../../sdb
└── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1

0 directories, 2 files

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2018-09-14 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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


[Touch-packages] [Bug 1789950] Re: [Bluetooth speaker BSP08WBT, playback] No bluetooth playback possible after resuming from suspend

2018-09-14 Thread indigocat
This has been happening randomly; yesterday, the speaker worked again.

For now, this report can be closed.

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

Title:
  [Bluetooth speaker BSP08WBT, playback] No bluetooth playback possible
  after resuming from suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  # What happens:
  After resuming from suspend, audio playback to bluetooth speaker isn't 
possible, only the machine's internal speakers work.

  Bluetooth speaker is a selectable option as output, but audio is not
  routed to bluetooth speaker, playback defaults to internal speakers
  even if bluetooth speaker is selected.

  #What should happen:
  When choosing the bluetooth speaker as audio output device, audio should be 
immediately routed to bluetooth speaker.

  #Troubleshoting:
  Already tried `pulseaudio --kill; pulseaudio --start`, `sudo hciconfig hci0 
reset`, and `sudo service udev restart`. Problem persists.

  I'm using kernel 4.4.0-134-generic.
  Cannot use kernel 4.15+ on this machine (older Lenovo T410s), as performance 
drops impressively, due to sub-optimal disk i/o in comparison to 4.4, at least 
on this machine.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dmayr 13648 F pulseaudio
   /dev/snd/controlC0:  dmayr 13648 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Thu Aug 30 13:36:38 2018
  InstallationDate: Installed on 2017-09-24 (340 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: BSP08WBT
  Symptom_Type: None of the above
  Title: [BSP08WBT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924BV6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924BV6:pvrThinkPadT410s:rvnLENOVO:rn2924BV6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2924BV6
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1094235] Re: package libc6 2.15-0ubuntu10.2 failed to install/upgrade: './usr/share/doc/libc6/changelog.Debian.gz' is different from the same file on the system

2018-09-14 Thread indigocat
Not affected by the bug anymore, upgraded to 16.04.

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

Title:
  package libc6 2.15-0ubuntu10.2 failed to install/upgrade:
  './usr/share/doc/libc6/changelog.Debian.gz' is different from the same
  file on the system

Status in eglibc package in Ubuntu:
  New

Bug description:
  apt-get install -f

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libc6 2.15-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15.1
  Architecture: amd64
  Date: Fri Dec 28 08:24:20 2012
  DpkgTerminalLog:
   Preparando para reemplazar libc6 2.15-0ubuntu10.2 (usando 
.../libc6_2.15-0ubuntu10.3_amd64.deb) ...
   Desempaquetando el reemplazo de libc6 ...
   dpkg: error al procesar 
/var/cache/apt/archives/libc6_2.15-0ubuntu10.3_amd64.deb (--unpack):
'./usr/share/doc/libc6/changelog.Debian.gz' is different from the same file 
on the system
  ErrorMessage: './usr/share/doc/libc6/changelog.Debian.gz' is different from 
the same file on the system
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.15-0ubuntu10.2 failed to install/upgrade: 
'./usr/share/doc/libc6/changelog.Debian.gz' is different from the same file on 
the system
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1610591] Re: Video acceleration regression for Radeon Xpress 200M (r300) in xorg-lts-xenial & xorg-lts-wily

2018-09-14 Thread indigocat
Not using 14.04 anymore.

This can be closed if not affecting anybody else.

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

Title:
  Video acceleration regression for Radeon Xpress 200M (r300) in xorg-
  lts-xenial & xorg-lts-wily

Status in xserver-xorg-driver-ati:
  Unknown
Status in mesa package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Xenial (kernel 4.4 and
  xserver-xorg-video-radeon-lts-xenial), system boots up fine and
  responsively, but screen is laggy; there is a tremendous performance
  regression in comparison to xorg-lts-vivid. Lots of video tearing that
  did not occur when using xserver-xorg-video-radeon-lts-vivid.

  System is an older Pentium laptop (Packard Bell EasyNote) with a Radeon 
Xpress 200M chip (r300 driver). Video acceleration was working with DRI2 under 
the Vivid stack (kernel 3.19-64-lowlatency + 
xserver-xorg-video-radeon-lts-vivid).
  I also tried upgrading to the Wily kernel (4.2.0-lowlatency), and video 
acceleration works fine with the Vivid xorg.

  I reported this in launchpad previously, and it was dismissed as "invalid" 
since Wily is EOL.
  The problem, however, persists in the Xenial stack, so I'm reporting it here.

  Attached are the respective Xorg.0 logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1610591/+subscriptions

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread James Page
tl;dr you don't need vaultlocker to reproduce this issue :-)

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

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread James Page
Dimitri

vaultlocker is a helper tool for managing dmcrypt/LUKS keys in Vault.

vaultlocker provides commands to format a block devices using an
encryption key, and to unlock a block device previously encrypted by
vaultlocker (along with some systemd unit configurations to perform this
action on reboots).

Currently vaultlocker performs targetted rescan and settle udevadm
operations post luksFormat to wait for appropriate /dev entries to be
created; I consider this a workaround as it would be generally nicer if
this was actually performed as part of the luksFormat operation in
cryptsetup - once the format operation completes, block devices would be
ready for use without any need to udevadm trigger/settle in other
tooling.

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

2018-09-14 Thread Didier Roche
Are you sure this is due to the above patch, can you try without it?

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-09-14 Thread Martin Wildam
** Attachment added: "Connection attempt second wifi with PEAP"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+attachment/5188874/+files/wlan-connection-attempt-20180914b.log

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-09-14 Thread Martin Wildam
Kernel log for the previous attempts.

** Attachment added: "Kernel log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+attachment/5188875/+files/wlan-connection-attempt-20180914.log

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-09-14 Thread Martin Wildam
Dell Precision 7520, I also cannot connect to WPA2/PEAP WIFI. Here are
my logs - I tried to connect to two slightly different configured wifi
networks using that PEAP (I never heard of that before).

** Attachment added: "Connection attempt first wifi with PEAP"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+attachment/5188873/+files/wlan-connection-attempt-20180914a.log

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Thomas Ward
Nginx properly builds with pcre2

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-09-14 Thread Kurt Woitke
I have this same problem as well - and have had this problem for a few
months. Every time the update fails it takes me here.

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

Title:
  package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: pcscd 1.8.10-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  AptOrdering:
   pcscd: Install
   pcscd: Configure
  Architecture: amd64
  Date: Fri Jun 23 12:21:31 2017
  DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-28 (177 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pcsc-lite
  Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+subscriptions

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Thomas Ward
** Description changed:

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:
  
  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.
  
  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh
+ 
+ --
+ 
+ For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
+ poorly named (according to jbicha).

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  New
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Jeremy Bicha
Debian's clamav has already switched.

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  New
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

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

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


[Touch-packages] [Bug 1792578] Re: tracker-store crashed with SIGSEGV

2018-09-14 Thread Cristian Aravena Romero
** Information type changed from Private to Public

** Description changed:

  Hello,
  
  I do not know how it happened
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
+ 
+ 
+ 
+ https://gitlab.gnome.org/GNOME/tracker/issues/39
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: tracker 2.0.3-3
  Uname: Linux 4.18.7-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 14 08:51:24 2018
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2017-10-13 (335 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/tracker/tracker-store
  SegvAnalysis:
-  Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx)
-  PC (0x7ff7ad4aa0d7) ok
-  source "%rcx" ok
-  destination "0x30(%rdx)" (0x0030) not located in a known VMA region 
(needed writable region)!
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx)
+  PC (0x7ff7ad4aa0d7) ok
+  source "%rcx" ok
+  destination "0x30(%rdx)" (0x0030) not located in a known VMA region 
(needed writable region)!
+  Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
-  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
-  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
-  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
-  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
  Title: tracker-store crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

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

Title:
  tracker-store crashed with SIGSEGV

Status in tracker package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know how it happened

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  

  https://gitlab.gnome.org/GNOME/tracker/issues/39

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: tracker 2.0.3-3
  Uname: Linux 4.18.7-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 14 08:51:24 2018
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2017-10-13 (335 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/tracker/tracker-store
  SegvAnalysis:
   Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx)
   PC (0x7ff7ad4aa0d7) ok
   source "%rcx" ok
   destination "0x30(%rdx)" (0x0030) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
   () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
   () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
   () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
   () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
  Title: tracker-store crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Jeremy Bicha
Debian's php7.3 has already switched

** Changed in: php7.2 (Ubuntu)
   Status: New => Triaged

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  New
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Jeremy Bicha
Debian's git has already switched

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  New
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

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

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


[Touch-packages] [Bug 1792579] [NEW] Network Disconnecting Intermittantly

2018-09-14 Thread Kent Lion
Public bug reported:

On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet)
connection disconnects randomly. Everything was fine before the upgrade
from Xenial LTS. It's not yet reproducible (by me). There are no error
messages associated with it, the indicator plugin doesn't turn grey, and
I've noticed no pattern to when it occurs. The only way I know it is has
occurred is when something that uses the (Samba) network times out or
stops doing anything. If I click the indicator plugin and select "wired
connection 1", it reconnects immediately, But at some later time the
same thing may happen again; it could be after a few minutes or many
hours. This happens on another, the AMD machine I use as a file server,
too, so it looks like a bug in Bionic Beaver, not a software package.

 lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

I suppose the bug could have something to do with the compatibility of
Samba and 18.04 LTS, because after the upgrade, everything in /etc/fstab
that used the credentials option stopped working, but that's part of
another bug already reported by others but not yet solved.

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

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

Title:
  Network Disconnecting Intermittantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet)
  connection disconnects randomly. Everything was fine before the
  upgrade from Xenial LTS. It's not yet reproducible (by me). There are
  no error messages associated with it, the indicator plugin doesn't
  turn grey, and I've noticed no pattern to when it occurs. The only way
  I know it is has occurred is when something that uses the (Samba)
  network times out or stops doing anything. If I click the indicator
  plugin and select "wired connection 1", it reconnects immediately, But
  at some later time the same thing may happen again; it could be after
  a few minutes or many hours. This happens on another, the AMD machine
  I use as a file server, too, so it looks like a bug in Bionic Beaver,
  not a software package.

   lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  I suppose the bug could have something to do with the compatibility of
  Samba and 18.04 LTS, because after the upgrade, everything in
  /etc/fstab that used the credentials option stopped working, but
  that's part of another bug already reported by others but not yet
  solved.

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

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


[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

2018-09-14 Thread Julian Andres Klode
Matthias Haag (mahaag) wrote 1 hour ago:
> We also recognized this issue on two laptops and downloaded one package which 
> should be updated with wget manually:
[...]
> => Every time a different content!

So apt successfully detected the failed content, therefore there is no
bug in apt here.

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

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing all files in
  /var/lib/apt/lists and update again" but it doesn't work. Don't know
  how to resolve it.

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

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


[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

2018-09-14 Thread amano
https://4.bp.blogspot.com/-CKw5ikw4WNo/WWo7WrezseI/KC4/CPbs48OQj0A2hMNY5_Ivu6iTaRzClDYMQCLcBGAs/s1600/07%2BGNOME%2BTerminal.jpg

This is a gnome-terminal screenshot from Fedora 26. There everything
seems ok. Can we drop the Debian patch above to see if that fixes the
issue?

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

2018-09-14 Thread amano
Is this an upstream issue (does Fedora show that behavior as well?) or
the outcome of a Debian patch? There is at least one which is scrollbar
related:

+ Add scrollbar-background-theming.patch:
  - Draw background under the scrollbar that matches the actual terminal
background color. This allows proper theming.

https://lists.canonical.com/archives/cosmic-
changes/2018-September/009594.html

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1774739] Re: Running Qt apps inside a 18.04 container crashes

2018-09-14 Thread Timo Jyrinki
https://bugreports.qt.io/browse/QTBUG-70447 notes that a newer Docker
fixes it.

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

Title:
  Running Qt apps inside a 18.04 container crashes

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

Bug description:
  What happened:
  1) Install a container system (eg Docker, LXD) - I'm using Docker
  2) Create a container which is Ubuntu 18.04
  3) Install a Qt app, eg qtcreator, inside the container
  4) Run the container so that it shows the hosts X11 socket
  5) Notice that the application fails to start

  What I expected to happen:
  At step 5 for the application to start.

  Note that the same steps work fine for Ubuntu 16.04 and 17.10 - and if
  it matters my host is 17.10.

  Here is a stacktrace of the crash
  https://pastebin.ubuntu.com/p/WKKGmxqqSx/

  Here is a Dockerfile that reproduces the issue
  https://pastebin.ubuntu.com/p/nzmJRfPYVc/ to use this make a
  Dockerfile in an empty folder with the pastebin contents, then simply
  run the following commands in that folder

  $ sudo apt install docker.io
  $ sudo docker build -t qtbug .
  $ sudo docker run --rm -ti -e DISPLAY --net=host --cap-add=SYS_PTRACE 
--security-opt seccomp=unconfined qtbug

  This should enter you into the gdb session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1774739/+subscriptions

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


[Touch-packages] [Bug 1792552] Re: Qt doesn't cope with EPERM returned from statx(2)

2018-09-14 Thread Timo Jyrinki
The upstream response might be similar to
https://bugreports.qt.io/browse/QTBUG-70447 's "Please update your
container manager's whitelist of syscalls."

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

Title:
  Qt doesn't cope with EPERM returned from statx(2)

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

Bug description:
  The statx(2) system call is a relatively new addition and has not seen
  widespread use. As such the seccomp filer used by snapd to confine
  application processes does not currently permit it. While addressing
  the bug in snapd is in progress we wanted to contribute a fix to the
  package so that all snaps built with Qt from the Ubuntu archive will
  automatically benefit and behave correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+subscriptions

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


[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-14 Thread Francis Ginther
** Tags added: id-5b9a8473a5864f4a45e1c7b6

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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


[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

2018-09-14 Thread Matthias Haag
This issue seems to be related to https://bugs.launchpad.net/dell-
sputnik/+bug/1729674

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing all files in
  /var/lib/apt/lists and update again" but it doesn't work. Don't know
  how to resolve it.

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

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


[Touch-packages] [Bug 1792552] Re: Qt doesn't cope with EPERM returned from statx(2)

2018-09-14 Thread Ubuntu Foundations Team Bug Bot
The attachment "Debdiff fixing the statx(2) under snap confinement (v2)"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Qt doesn't cope with EPERM returned from statx(2)

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

Bug description:
  The statx(2) system call is a relatively new addition and has not seen
  widespread use. As such the seccomp filer used by snapd to confine
  application processes does not currently permit it. While addressing
  the bug in snapd is in progress we wanted to contribute a fix to the
  package so that all snaps built with Qt from the Ubuntu archive will
  automatically benefit and behave correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+subscriptions

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


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

2018-09-14 Thread Nicorac
I've tried some workarounds:
- kernel parameter "net.ifnames=0" on kernel commandline: NOT WORKING
- ebtables: NOT WORKING
- add "@reboot /usr/sbin/netplan apply" to root cron: NOT WORKING

The following works on my side:

* create a new unit file: /etc/systemd/system/netplan-workaround.service

[Unit]
After=syslog.service

[Service]
ExecStart=/usr/sbin/netplan apply

[Install]
WantedBy=default.target


* enable and start it
# systemctl enable netplan-workaround.service
# systemctl start netplan-workaround.service

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

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

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

  [Link]
  Name=myiface3

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

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

  The device is not renamed.

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

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

  === Original Bug ==

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1792552] Re: Qt doesn't cope with EPERM returned from statx(2)

2018-09-14 Thread Zygmunt Krynicki
** Patch removed: "Debdiff fixing the statx(2) under snap confinement"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+attachment/5188741/+files/fix-statx-in-snaps.debdiff

** Patch added: "Debdiff fixing the statx(2) under snap confinement (v2)"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+attachment/5188745/+files/fix-statx-in-snaps.debdiff

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

Title:
  Qt doesn't cope with EPERM returned from statx(2)

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

Bug description:
  The statx(2) system call is a relatively new addition and has not seen
  widespread use. As such the seccomp filer used by snapd to confine
  application processes does not currently permit it. While addressing
  the bug in snapd is in progress we wanted to contribute a fix to the
  package so that all snaps built with Qt from the Ubuntu archive will
  automatically benefit and behave correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+subscriptions

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


[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

2018-09-14 Thread Matthias Haag
We also recognized this issue on two laptops and downloaded one package
which should be updated with wget manually:

$ md5sum firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb*
1577ff1303d995196bf47362feef7e5f  firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb
ca062374dadbe009bda1bc4ae49d29cb  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.1
216ff072772aad7c442158d341cc0882  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.2

=> Every time a different content!

So I changed the network cable from the Thunderbolt dock to the internal
network adapter and now it works:

$ md5sum firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb*
1577ff1303d995196bf47362feef7e5f  firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb
ca062374dadbe009bda1bc4ae49d29cb  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.1
216ff072772aad7c442158d341cc0882  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.2
13a869e979b64bb8d0fefb0f8966b063  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.3
13a869e979b64bb8d0fefb0f8966b063  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.4
13a869e979b64bb8d0fefb0f8966b063  
firefox_62.0+build2-0ubuntu0.18.04.4_amd64.deb.5

We are using kernel 4.15.0-34-generic with Dell Precision 7530 and TB18
dock. The wget finishes with exit code 0 and the size of the file is
always the same.

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

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing 

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-14 Thread Dark Dragon
I booted up a live disk with Ubuntu 17.04 (Unity) and it shows the same
behavior.

** Description changed:

- Since Ubuntu switched to Gnome, display scaling does not work correctly.
- This is because my external monitor is detected as 7" although it is
- 32". All applications which use Qt auto scaling have huge controls!
+ My external monitor is detected as 7" although it is 32". All
+ applications which use Qt auto scaling have huge controls!
  
  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt
  auto scaling. I think the solution should be to fix the size detection
  instead.
+ 
+ It seems not related to the display server, compositor or window manager
+ since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04
+ (Mutter, Gnome). I tried it with both Wayland and X (on Wayland).
  
  Further, it seems not related to graphics driver, since I personally use
  the open source driver with my internal Intel card, whereas someone else
  uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).
  
  If it is in the wrong category, please move it / add the corresponding
  packages.
  
  If you need any further information to tackle the problem, just tell me!
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

** Attachment added: "xrandr output for external display on 17.04"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188747/+files/xrandr.log

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

2018-09-14 Thread Timo Aaltonen
sssd builds fine with libpcre2-dev

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  New
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  New
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

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

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


[Touch-packages] [Bug 1792511] Re: Unable to create a PPPoE connection in Ubuntu 18.04 LTS

2018-09-14 Thread A Raghuram
I am not sure if issue is caused by network-manager or netplan or gnome-
shell or two/all of them combined.

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

Title:
  Unable to create a PPPoE connection in Ubuntu 18.04 LTS

Status in network-manager package in Ubuntu:
  New

Bug description:
  My ISP provides PPPoE connection with username, password and service
  name and binds my MAC Address.  Since I have connected my router to
  the WAN, the MAC Address of the router has been bound in their server
  by them.  Whereas the IP Address and Gateway are set to be
  automatically obtained, and DNS addresses are manually given.  My
  Desktop has been connected to the router and the network is working
  fine.

  However, for the purpose of troubleshooting the network when it goes
  down, I need to connect directly to the computer.  Therefore, I need
  to know how to configure a wired PPPoE connection directly in my
  computer, which has only one NIC.  The network settings GUI does not
  allow setting up one.

  Please guide me how to -

  i)   configure a PPPoE connection
  ii)  specify the username, password and service name, and
  iii) clone my router's MAC address to my desktop

  to be able to connect to the internet.The GUI provided in Ubuntu
  18.04 Bionic Beaver (which is what I am using) does not provide for
  creating a PPPoE connection.  The GUI should also allow use of a
  cloned MAC address for the PPPoE connection.

  After referring to various community posts, I tried the following
  command (though I am not quite conversant with Linux commands) :

  nmcli connection add con-name "..." type pppoe username ... password
  ... service ... parent (iface name of the NIC) autoconnect no ifname
  "*" save yes

  The pppoe connection gets created but vanishes from the "Settings ->
  Network" GUI under "Wired" category after some time and some times
  gets listed under "Bluetooth" category (under Network Settings) before
  vanishing.

  Also, neither the command nor the GUI, allows me to specify a cloned
  MAC address to the connection created using the above command.

  Please get this issue addressed at the earliest.

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

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


[Touch-packages] [Bug 1792552] [NEW] Qt doesn't cope with EPERM returned from statx(2)

2018-09-14 Thread Zygmunt Krynicki
Public bug reported:

The statx(2) system call is a relatively new addition and has not seen
widespread use. As such the seccomp filer used by snapd to confine
application processes does not currently permit it. While addressing the
bug in snapd is in progress we wanted to contribute a fix to the package
so that all snaps built with Qt from the Ubuntu archive will
automatically benefit and behave correctly.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: snapd

** Patch added: "Debdiff fixing the statx(2) under snap confinement"
   
https://bugs.launchpad.net/bugs/1792552/+attachment/5188741/+files/fix-statx-in-snaps.debdiff

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

Title:
  Qt doesn't cope with EPERM returned from statx(2)

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

Bug description:
  The statx(2) system call is a relatively new addition and has not seen
  widespread use. As such the seccomp filer used by snapd to confine
  application processes does not currently permit it. While addressing
  the bug in snapd is in progress we wanted to contribute a fix to the
  package so that all snaps built with Qt from the Ubuntu archive will
  automatically benefit and behave correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+subscriptions

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


[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-14 Thread Dark Dragon
Same result when I connect via DP->HDMI adapter

** Attachment added: "xrandr output for external display on adapter"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188740/+files/xrandr.log

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu switched to Gnome, display scaling does not work
  correctly. This is because my external monitor is detected as 7"
  although it is 32". All applications which use Qt auto scaling have
  huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

2018-09-14 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted gcc-8 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gcc-8/8.2.0-1ubuntu2~18.04 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: gcc-8 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed
Status in gcc-8 source package in Bionic:
  Fix Committed

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

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

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


[Touch-packages] [Bug 1792544] [NEW] demotion of pcre3 in favor of pcre2

2018-09-14 Thread Matthias Klose
Public bug reported:

demotion of pcre3 in favor of pcre2. These packages need analysis what
needs to be done for the demotion of pcre3:

Packages which are ready to build with pcre2 should be marked as
'Triaged', packages which are not ready should be marked as
'Incomplete'.

aide
apache2
apr-util
clamav
exim4
freeradius
git
glib2.0
grep
haproxy
libpam-mount
libselinux
nginx
nmap
php7.2
postfix
python-pyscss
quagga
rasqal
slang2
sssd
wget
zsh

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

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

** Affects: apr-util (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: libpam-mount (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Affects: pcre3 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: php7.2 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: python-pyscss (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

** Also affects: apr-util (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: libpam-mount (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: php7.2 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Description changed:

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:
+ 
+ Packages which are ready to build with pcre2 should be marked as
+ 'Triaged', packages which are not ready should be marked as
+ 'Incomplete'.
  
  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New

[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

2018-09-14 Thread Łukasz Zemczak
This bug is already fixed in the latest version present in bionic-
security - marking as verified.

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

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

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


[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

2018-09-14 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted gcc-7 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gcc-7/7.3.0-27ubuntu1~18.04 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: gcc-7 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

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

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


[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

2018-09-14 Thread Łukasz Zemczak
Please ignore above comment (#5), sent it into the wrong bug.

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

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

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


[Touch-packages] [Bug 1792370] Re: Broken links to libmircookie packages

2018-09-14 Thread Michał Sawicz
Looks like a way to avoid HTTP cookies being sent/retrieved?

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

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

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


[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2018-09-14 Thread Sæmundur Óskar Haraldsson
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

Issue came back after latest update

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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


[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2018-09-14 Thread Robert Hrovat
I have the same problem on at least 6 computers with 18.04.1 now.

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions

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


[Touch-packages] [Bug 1763993] Re: bug

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- bug
+ [radeon] graphics are very poor

** Tags added: radeon

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

Title:
  [radeon] graphics are very poor

Status in Ubuntu:
  Won't Fix

Bug description:
  graphics are very poor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 15 00:27:21 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS690 [Radeon X1200] [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. GA-MA69VM-S2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=857c15e8-651e-45d0-a401-07e1fcf2c863 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: GA-MA69VM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd12/29/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA69VM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.90+git1802210630.009634~oibaf~a
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1802241930.f0b397~oibaf~a
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1802241930.f0b397~oibaf~a
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.10.99+git1802211933.f777e9~oibaf~a
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1802181857.757955~oibaf~a
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1712110734.048baf~oibaf~a
  xserver.bootTime: Sat Apr 14 22:50:25 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSONiX USB Device KEYBOARD, id 8
   inputSONiX USB Device MOUSE, id 9
   inputSONiX USB Device KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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


[Touch-packages] [Bug 1764381] Re: Ubuntu showing up only on right third of the screen

2018-09-14 Thread Daniel van Vugt
** Summary changed:

- startup failure
+ Ubuntu showing up only on right third of the screen

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

** Summary changed:

- Ubuntu showing up only on right third of the screen
+ [i915] Ubuntu showing up only on right third of the screen

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

Title:
  [i915] Ubuntu showing up only on right third of the screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu showing up only on right third of the screen. Going to sleep
  mode and putting in ubuntu password the only way to show the whole
  screen and getting started with ubuntu 16.04 LTS 32bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 16 12:50:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated 
Graphics Controller [1025:015b]
 Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [1025:015b]
  InstallationDate: Installed on 2018-01-16 (89 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: Acer AOA150
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=be9b3832-9952-4cd9-9a95-6e297eef977c ro splash drm.debug=0xe quiet 
plymouth:debug vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3310
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Apr 16 12:47:57 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4546 
   vendor AUO
  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-server/+bug/1764381/+subscriptions

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


[Touch-packages] [Bug 1764087] Status changed to Confirmed

2018-09-14 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (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/1764087

Title:
  Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly
  works with 4.13.0-37)

Status in X.Org X server:
  Won't Fix
Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions

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


[Touch-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

2018-09-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Wrongly boots into low graphics mode
+ Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works 
with 4.13.0-37)

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

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

Title:
  Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly
  works with 4.13.0-37)

Status in X.Org X server:
  Won't Fix
Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions

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


[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2018-09-14 Thread Steffen Neumann
And then I changed the file below and now have a working connection:

sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u 
./77-mm-huawei-net-port-types.rules 
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
diff -u -r1.1 ./77-mm-huawei-net-port-types.rules
--- ./77-mm-huawei-net-port-types.rules 2018/09/06 05:09:56 1.1
+++ ./77-mm-huawei-net-port-types.rules 2018/09/06 05:37:49
@@ -24,4 +24,7 @@
 # Airtel branded E3372h-607, using huawei-cdc-ncm driver but with unresponsive 
cdc-wdm port
 ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506", 
ENV{ID_MM_HUAWEI_NDISDUP_SUPPORTED}="1"
 
+# https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981
+ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", ATTR{bNumConfigurations}=="3", 
ATTR{bConfigurationValue}!="3" ATTR{bConfigurationValue}="3"
+
 LABEL="mm_huawei_port_types_end"

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Touch-packages] [Bug 1766073] Re: boot up hangs on a blank scrIeen

2018-09-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356

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


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

** This bug has been marked a duplicate of bug 1727356
   Login screen never appears on early generation Intel GPUs (Core2 and Atom 
etc)

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

Title:
  boot up hangs on a blank scrIeen

Status in mutter package in Ubuntu:
  New

Bug description:
  I have had booting problems shortly after upgrading to V. 17. I can
  get the machine to boot using F2. Once I get the desktop, everything
  works fine.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 22 07:08:17 2018
  DistUpgraded: 2018-04-04 22:30:53,199 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:011e]
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:011e]
  InstallationDate: Installed on 2016-08-02 (627 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Acer Aspire 5720
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=e4631648-f8d1-4d71-af95-43fe3ed0cef7 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-04-05 (17 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Nettiling
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnAcer:bvrV1.21:bd11/09/2007:svnAcer:pnAspire5720:pvrV1.21:rvnAcer:rnNettiling:rvrV1.21:cvnAcer:ct1:cvrV1.21:
  dmi.product.family: None
  dmi.product.name: Aspire 5720
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Apr 22 07:06:00 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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


[Touch-packages] [Bug 1766307] Re: Crash low-graphics mode

2018-09-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1766307

Title:
  Crash low-graphics mode

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since friday, 4/20/2018, when I did an upgrade in Ubuntu, I receive an
  error message:

  The system is running in low-graphics mode

  Your screen, graphics cards, and input device settings could not
  be detected correctly. You will need to configure these yourself.

  Then, using tab key, I press OK, then I choose try the default, and
  everything works fine after this. But this is very annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 23 13:54:49 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.13.0-38-generic, x86_64: installed
   nvidia-304, 304.135, 4.13.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:7788]
  InstallationDate: Installed on 2017-09-14 (221 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 003: ID 04b3:310c IBM Corp. Wheel Mouse
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7788
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=2f8e3cb0-6af1-44b7-b3fa-ea29171c708d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31 (G3) (MS-7788)
  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.3:bd01/18/2012:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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: Mon Apr 23 12:51:59 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-server/+bug/1766307/+subscriptions

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


[Touch-packages] [Bug 1764437] Re: x

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  x

Status in Ubuntu:
  Incomplete

Bug description:
  x

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 16 23:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=7f424bd3-4785-4184-ab31-dd3870c7c934 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 07911020561620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Apr 16 15:51:23 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1764523] Re: xorg

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  xorg

Status in Ubuntu:
  Incomplete

Bug description:
  display problems

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Mon Apr 16 16:46:13 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (58 days ago)

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

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


[Touch-packages] [Bug 1766332] Re: need help

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  need help

Status in Ubuntu:
  Incomplete

Bug description:
  my graphics not working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Tue Apr 24 00:24:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed
   nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3808]
  InstallationDate: Installed on 2018-04-17 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 174f:14e9 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=ec0e44e0-f209-4a9f-908f-c907644c99a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D5CN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paris 5A8
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 300-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN31WW:bd12/03/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80Q7
  dmi.product.version: Lenovo ideapad 300-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  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: Mon Apr 23 23:56:44 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1767771] Re: internal error message on startup

2018-09-14 Thread Daniel van Vugt
Can you tell us what the error message is?

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

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

Title:
  internal error message on startup

Status in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 xenial (x86-64)
  Cinnamon version 3.6.7
  Linux kernel - 4.13.0-39-generic
  Lenovo thinkpad T420 / Core i5-2520M CPU
  Graphics card - Intel Corp 2nd Gen Core Processor Fam Integrated Graphics 
Controller

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 29 10:43:43 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
  InstallationDate: Installed on 2017-06-30 (302 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 423662G
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=a3269a13-d9f6-4ccf-aca1-ad5804e52a97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 423662G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn423662G:pvrThinkPadT420:rvnLENOVO:rn423662G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 423662G
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  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: Sun Apr 29 10:41:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1767732] Re: bug repport

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  bug repport

Status in Ubuntu:
  Incomplete

Bug description:
  the disq startup creator doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl 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.16
  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
  Date: Sat Apr 28 23:20:19 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ca]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca]
  InstallationDate: Installed on 2017-12-07 (142 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=40721ece-0225-44a9-bd94-badcd83aa0e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HVRTT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  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.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

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

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


[Touch-packages] [Bug 1767734] Re: bug repport

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  bug repport

Status in Ubuntu:
  Incomplete

Bug description:
  i don't know maybe the nvidia driver package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl 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.16
  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
  Date: Sat Apr 28 23:27:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ca]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca]
  InstallationDate: Installed on 2017-12-07 (142 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=40721ece-0225-44a9-bd94-badcd83aa0e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HVRTT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  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.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

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

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


[Touch-packages] [Bug 1766638] Re: graphical

2018-09-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: Confirmed => 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/1766638

Title:
  graphical

Status in Ubuntu:
  Incomplete

Bug description:
  problem during boot process

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 24 17:14:29 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics Controller 
[1043:817a]
  InstallationDate: Installed on 2016-06-15 (677 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTek Computer INC. P5GZ-MX
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=083e9287-55a1-422d-86ba-6839368c9db8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5GZ-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd11/30/2006:svnASUSTekComputerINC.:pnP5GZ-MX:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GZ-MX:rvrRev1.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.name: P5GZ-MX
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTek Computer INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 24 17:10:36 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, 
id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1825 
   vendor FUS
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1767095] Re: intel vga

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  intel vga

Status in Ubuntu:
  Incomplete

Bug description:
  intel vga 
  00:02.0 vga compatible controller: intel corporation haswell-ult integrated 
graphics controller (rev 0b)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 26 10:49:19 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.13.0-38-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2212]
 Subsystem: Hewlett-Packard Company GF117M [GeForce 610M/710M/810M/820M / 
GT 620M/625M/630M/720M] [103c:2212]
  InstallationDate: Installed on 2018-04-18 (7 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=d91e6cc6-a7c9-46f9-8754-9fe5402454f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Apr 26 09:46:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1768224] Re: Xorg freeze

2018-09-14 Thread Daniel van Vugt
** Tags added: nvidia

** Tags added: black-screen

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

** Summary changed:

- Xorg freeze
+ [nvidia] Black screen on login, then freeze

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

Title:
  [nvidia] Black screen on login, then freeze

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I log into my system I'm stuck at a black screen for a while. After 
waiting about a minute gnome shell is loaded but as mainly frozen.
  I guess it is an xorg problem, but I'm not at all sure about that. 
  It could also be a gnome-shell issue.
  That happens since I updated from 17.10 to 18.04

  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
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.106  Tue Jan  9 15:10:23 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 12:51:44 2018
  DistUpgraded: 2018-04-28 10:42:27,070 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.106, 4.13.0-39-generic, x86_64: installed
   nvidia-340, 340.106, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. G84 [GeForce 8600 GT] [1043:8272]
  InstallationDate: Installed on 2017-11-12 (169 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=415d35f2-1450-4bc4-9156-fd8579229063 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (3 days ago)
  dmi.bios.date: 12/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd12/16/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1769058] Re: Xorg freeze

2018-09-14 Thread Daniel van Vugt
Looks like a suspend-resume problem, judging by the kernel log.

Please let us know if after updating this system whether the bug is
still happening.

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1769058

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have upgraded ubuntu form 17.10 to 18.04, but after login in Gnome or 
Ubuntu desktop environment, UI is not responding. No mouse no keyboard, every 
thing is frozen, even i can't logout from screen. i have to manually turnoff 
the laptop.
  Currently i am using deepin desktop environment.
  Please do the needful.

  Thanks

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Deepin
  Date: Fri May  4 12:02:20 2018
  DistUpgraded: 2018-04-28 03:31:09,905 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5002]
  InstallationDate: Installed on 2017-03-30 (399 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20140
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=871acc38-6b5a-4871-8105-c9af13662669 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (6 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1ET73WW(1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20140
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1ET73WW(1.16):bd04/10/2013:svnLENOVO:pn20140:pvrLenovoB480:rvnLENOVO:rn20140:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: Lenovo B480
  dmi.product.name: 20140
  dmi.product.version: Lenovo B480
  dmi.sys.vendor: LENOVO
  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/linux/+bug/1769058/+subscriptions

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


[Touch-packages] [Bug 1769270] Re: Xorg freeze

2018-09-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1769270

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   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 quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23472P2
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23472P2
  dmi.product.version: ThinkPad T430
  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-server/+bug/1769270/+subscriptions

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


[Touch-packages] [Bug 1769091] Re: Xorg freeze on login

2018-09-14 Thread Daniel van Vugt
This sounds like one of the bugs we fixed earlier in the year.

Please update the system and tell us if the bug still occurs.

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

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => 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/1769091

Title:
  Xorg freeze on login

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  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-server/+bug/1769091/+subscriptions

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


[Touch-packages] [Bug 1769395] Re: screen fade out

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  screen fade out

Status in Ubuntu:
  Incomplete

Bug description:
  screen fade out

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 22:44:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505b]
  InstallationDate: Installed on 2018-04-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 003: ID 5986:2109 Acer, Inc 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20H1006MTX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fcf40ca-beff-4360-9559-5c878a16f54b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0DET83W (1.83 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20H1006MTX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0DET83W(1.83):bd06/09/2017:svnLENOVO:pn20H1006MTX:pvrThinkPadE470:rvnLENOVO:rn20H1006MTX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E470
  dmi.product.name: 20H1006MTX
  dmi.product.version: ThinkPad E470
  dmi.sys.vendor: LENOVO
  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
  xserver.bootTime: Sat May  5 22:36:58 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1769341] Re: Can't find HDMI

2018-09-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1769341

Title:
  Can't find HDMI

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The machine cannot find the HDMI port of the computer. It was working
  fine in version 17.10, but not after upgrading to 18.04. When looking
  at the graphics part of inxi, it is reporting that modesetting has
  failed.

  command: inxi -G

  Graphics:  Card: Intel HD Graphics 520
 Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.0-rc5

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 14:27:56 2018
  DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1094]
  InstallationDate: Installed on 2017-10-31 (186 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0489:e0a3 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=98508690-a9ad-4456-9e28-f3d867db01e9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-575
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 31 16:01:19 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1768408] Re: Desktop content

2018-09-14 Thread Daniel van Vugt
Can you please provide a video of the problem, or more detailed steps to
reproduce it?

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (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/1768408

Title:
  Desktop content

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  By dragging a desktop content into a folder on the system, the desktop
  gets stuck and only comes back with the system reboot

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 01:10:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a]
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 820 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.21
  dmi.board.name: 225A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.5B
  dmi.chassis.asset.tag: 5CG6257W70
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G2
  dmi.product.version: A3009D510303
  dmi.sys.vendor: Hewlett-Packard
  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 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/gnome-shell/+bug/1768408/+subscriptions

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


[Touch-packages] [Bug 1769500] Re: will not update

2018-09-14 Thread Daniel van Vugt
Can you please paste a copy of the command and/or error? A screenshot or
text...

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

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

Title:
  will not update

Status in Ubuntu:
  Incomplete

Bug description:
  will not update. Gives error msg public key 8BAF9A6F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May  6 15:07:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6250] [103c:3577]
  InstallationDate: Installed on 2017-11-26 (161 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=ed27f603-858e-45f5-9ba1-0b1789b36c0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068C11000320491620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May  5 13:58:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1769727] Re: Black Screen on Wake

2018-09-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (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/1769727

Title:
  Black Screen on Wake

Status in linux package in Ubuntu:
  New

Bug description:
  Mate 18.04 (64bit)
  MacbookAir 1,1
  Intel i915

  Blackscreen after every resume. All other features work. Just no
  backlight.

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon May  7 13:05:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a2]
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a2]
  InstallationDate: Installed on 2018-05-06 (1 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Apple Inc. MacBookAir1,1
  ProcEnviron:
   LANGUAGE=en_CA
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA11.88Z.00BB.B03.0803171226
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C8CC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C8CC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA11.88Z.00BB.B03.0803171226:bd03/17/08:svnAppleInc.:pnMacBookAir1,1:pvr1.0:rvnAppleInc.:rnMac-F42C8CC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C8CC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBookAir1,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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 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/linux/+bug/1769727/+subscriptions

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


[Touch-packages] [Bug 1769615] Re: pc no stop

2018-09-14 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  pc no stop

Status in Ubuntu:
  Incomplete

Bug description:
  mon pc ne veut pas s'arrêter  
  Merci

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon May  7 12:14:55 2018
  DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] 
[174b:2150]
  InstallationDate: Installed on 2016-12-17 (505 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Packard Bell imedia S3210
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: P01-B2
  dmi.board.name: WMCP78M
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.family: Packard Bell Desktop
  dmi.product.name: imedia S3210
  dmi.sys.vendor: Packard Bell
  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
  xserver.bootTime: Mon May  7 12:12:39 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB RECEIVER MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1769822] Re: VGA Resolution Detect with KVM

2018-09-14 Thread Daniel van Vugt
The problem here would be that the KVM device is blocking your monitor
from sending EDID information, which contains the supported resolutions.

I'm not sure if we can offer any software workarounds for this...

** Package changed: xorg (Ubuntu) => xorg-server (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/1769822

Title:
  VGA Resolution Detect with KVM

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Detects fine with direct connect, but when through kvm (works fine
  with windows) will not detect proper resolution.

  Log files should show:

  1. Boot with KVM attached.

  2. Plug monitor direct to motherboard (bypass) - old resolution for
  instant, then change to proper resolution.

  3. Swap back to monitor with KVM - Ok for instant, then blank and back
  to low resolution.

  KVM model is kvm 41ua - purchased from ebay.

  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 00:13:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H55M-USB3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b4d352ff-c19b-4f83-b0e6-94d042477b7f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: H55M-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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-server/+bug/1769822/+subscriptions

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


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

2018-09-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

** Changed in: xorg-server (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/1769824

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  System was idle at the time.  It displayed the background wall paper,
  but did NOT display the login screen.  I had to go to console, and
  restart lightdm.

  Wayno

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon May  7 23:16:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1312]
  InstallationDate: Installed on 2018-04-27 (10 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: HP-Pavilion KJ385AA-ABA a6433w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5c74d40b-8d0a-4abd-b32e-fca693b36f98 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.43
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnKJ385AA-ABAa6433w:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: KJ385AA-ABA a6433w
  dmi.sys.vendor: HP-Pavilion
  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-server/+bug/1769824/+subscriptions

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


[Touch-packages] [Bug 1792511] Re: Unable to create a PPPoE connection in Ubuntu 18.04 LTS

2018-09-14 Thread Paul White
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Unable to create a PPPoE connection in Ubuntu 18.04 LTS

Status in network-manager package in Ubuntu:
  New

Bug description:
  My ISP provides PPPoE connection with username, password and service
  name and binds my MAC Address.  Since I have connected my router to
  the WAN, the MAC Address of the router has been bound in their server
  by them.  Whereas the IP Address and Gateway are set to be
  automatically obtained, and DNS addresses are manually given.  My
  Desktop has been connected to the router and the network is working
  fine.

  However, for the purpose of troubleshooting the network when it goes
  down, I need to connect directly to the computer.  Therefore, I need
  to know how to configure a wired PPPoE connection directly in my
  computer, which has only one NIC.  The network settings GUI does not
  allow setting up one.

  Please guide me how to -

  i)   configure a PPPoE connection
  ii)  specify the username, password and service name, and
  iii) clone my router's MAC address to my desktop

  to be able to connect to the internet.The GUI provided in Ubuntu
  18.04 Bionic Beaver (which is what I am using) does not provide for
  creating a PPPoE connection.  The GUI should also allow use of a
  cloned MAC address for the PPPoE connection.

  After referring to various community posts, I tried the following
  command (though I am not quite conversant with Linux commands) :

  nmcli connection add con-name "..." type pppoe username ... password
  ... service ... parent (iface name of the NIC) autoconnect no ifname
  "*" save yes

  The pppoe connection gets created but vanishes from the "Settings ->
  Network" GUI under "Wired" category after some time and some times
  gets listed under "Bluetooth" category (under Network Settings) before
  vanishing.

  Also, neither the command nor the GUI, allows me to specify a cloned
  MAC address to the connection created using the above command.

  Please get this issue addressed at the earliest.

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

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


[Touch-packages] [Bug 1792520] Re: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error

2018-09-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package keyboard-configuration 1.178ubuntu2.7 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  appears on every system start

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.7
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Wed Sep 12 18:53:47 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 10
  InstallationDate: Installed on 2018-07-18 (57 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Keyboard:
   XKBLAYOUT="us,ru"
   XKBVARIANT=","
   BACKSPACE="guess"
   XKBMODEL="pc105"
   XKBOPTIONS="grp_led:scroll"
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.7 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1792520] [NEW] package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro

2018-09-14 Thread Illia Ovcharenko
Public bug reported:

appears on every system start

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: keyboard-configuration 1.178ubuntu2.7
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Wed Sep 12 18:53:47 2018
ErrorMessage: installed keyboard-configuration package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2018-07-18 (57 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Keyboard:
 XKBLAYOUT="us,ru"
 XKBVARIANT=","
 BACKSPACE="guess"
 XKBMODEL="pc105"
 XKBOPTIONS="grp_led:scroll"
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: console-setup
Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: 
installed keyboard-configuration package post-installation script subprocess 
returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package keyboard-configuration 1.178ubuntu2.7 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  appears on every system start

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.7
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Wed Sep 12 18:53:47 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 10
  InstallationDate: Installed on 2018-07-18 (57 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Keyboard:
   XKBLAYOUT="us,ru"
   XKBVARIANT=","
   BACKSPACE="guess"
   XKBMODEL="pc105"
   XKBOPTIONS="grp_led:scroll"
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.7 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1792511] [NEW] Unable to create a PPPoE connection in Ubuntu 18.04 LTS

2018-09-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My ISP provides PPPoE connection with username, password and service
name and binds my MAC Address.  Since I have connected my router to the
WAN, the MAC Address of the router has been bound in their server by
them.  Whereas the IP Address and Gateway are set to be automatically
obtained, and DNS addresses are manually given.  My Desktop has been
connected to the router and the network is working fine.

However, for the purpose of troubleshooting the network when it goes
down, I need to connect directly to the computer.  Therefore, I need to
know how to configure a wired PPPoE connection directly in my computer,
which has only one NIC.  The network settings GUI does not allow setting
up one.

Please guide me how to -

i)   configure a PPPoE connection
ii)  specify the username, password and service name, and
iii) clone my router's MAC address to my desktop

to be able to connect to the internet.The GUI provided in Ubuntu
18.04 Bionic Beaver (which is what I am using) does not provide for
creating a PPPoE connection.  The GUI should also allow use of a cloned
MAC address for the PPPoE connection.

After referring to various community posts, I tried the following
command (though I am not quite conversant with Linux commands) :

nmcli connection add con-name "..." type pppoe username ... password ...
service ... parent (iface name of the NIC) autoconnect no ifname "*"
save yes

The pppoe connection gets created but vanishes from the "Settings ->
Network" GUI under "Wired" category after some time and some times gets
listed under "Bluetooth" category (under Network Settings) before
vanishing.

Also, neither the command nor the GUI, allows me to specify a cloned MAC
address to the connection created using the above command.

Please get this issue addressed at the earliest.

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

-- 
Unable to create a PPPoE connection in Ubuntu 18.04 LTS
https://bugs.launchpad.net/bugs/1792511
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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


[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-09-14 Thread maria
www.belkinroutersupportnumber.com/

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and valid_lft
  fields for the interested network interface.

  Please note that if the ip address setting are the 

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-09-14 Thread maria
Follow this instruction hope so you can solve your issue,

Setup a DHCP server for the lease of about some minutes.
Boot the board and wait to forget an IP from DHCP server.
Before the lease expires, set a reservation for a different IP address.

If anyone using Belkin router or any other router facing any problem regarding 
this get help from this  Belkin 
Support Number
 it really provides the best solution.

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface 

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-09-14 Thread maria
Follow this instruction hope so you can solve your issue,

Setup a DHCP server for the lease of about some minutes.
Boot the board and wait to forget an IP from DHCP server.
Before the lease expires, set a reservation for a different IP address.

If anyone using Belkin router or any other router facing any problem regarding 
this get help from this www.belkinroutersupportnumber.com/
 it really provides the best solution.

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network 

[Touch-packages] [Bug 1791324] Re: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@598:run_argv:run_crashes:run_crash

2018-09-14 Thread Didier Roche
Ok, so the current fix in UNAPPROVED will prevent that at least ;)

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

Title:
  /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
  gtk@598:run_argv:run_crashes:run_crash

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

Bug description:
  [Impact]
   * The Ubuntu Error Tracker has been receiving reports about a problem 
regarding apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee
   * The theory is that those crashes are trigger by reports generated (but not 
send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, 
and thus, the new apport, when reporting, is crashing.
   * We now ignore if the key isn't present and just consider the answer as 
"false", which is a no-op.

  [Test Case]
   * Install apport 2.20.9-0ubuntu7.1
   * Generate a crash but don't report it.
   * Upgrade to apport apport 2.20.9-0ubuntu7.3
   * Report this crash.
     -> No apport crash should be triggered

  [Regression Potential]
   * We are doing a python2 compatible try/except to ignore the KeyError which 
was the regression. It doesn't seem it can trigger other regressions.

  ---

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

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

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


[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2018-09-14 Thread Treviño
A friend of mine also got this on upgrade (he's not skilled so was quite
critical to him):

Whole error on further upgrades were (sorry for italian locale):

I seguenti pacchetti NUOVI saranno installati:
  libmsgpackc2 tmate
0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati.
1 non completamente installati o rimossi.
È necessario scaricare 0 B/259 kB di archivi.
Dopo quest'operazione, verranno occupati 652 kB di spazio su disco.
Continuare? [S/n] s
(Lettura del database... 402540 file e directory attualmente installati.)
Rimozione di systemd-shim (9-1bzr4ubuntu1)...
Rimozione di "deviazione di 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd da 
systemd-shim"
dpkg-divert: errore: la rinomina comprende il sovrascrivere 
"/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service" con
   il file 
"/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd", 
non consentito
dpkg: errore nell'elaborare il pacchetto systemd-shim (--remove):
 installed systemd-shim package post-removal script subprocess returned error 
exit status 2
Si sono verificati degli errori nell'elaborazione:
 systemd-shim
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd-shim package in Ubuntu:
  Incomplete
Status in systemd source package in Bionic:
  Confirmed
Status in systemd-shim source package in Bionic:
  Confirmed

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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