[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Shih-Yuan Lee
Could you also provide `lspci -nnk > lspci.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/1748812

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

2018-02-11 Thread Daniel van Vugt
WORKAROUND (1):

Install these two together:
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libgl1-mesa-glx_17.2.4-0ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libglapi-mesa_17.2.4-0ubuntu2_amd64.deb

WORKAROUND (2):

sudo apt remove gstreamer1.0-vaapi

WORKAROUND (3):

Log in to "Ubuntu on Wayland" instead of "Ubuntu".

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Shih-Yuan Lee
It looks like it is a preloaded Ubuntu system.
Could you help to provide some logs as the followings?

/etc/buildstamp
`sudo mount /dev/sda2 /mnt` or `sudo mount /dev/nvme0n1p2 /mnt` and then attach 
/mnt/bto.xml
dpkg -l > dpkg.log and then attach dpkg.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/1748812

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Yuriy Vidineev
Yes it's Dell XPS 13 that comes with Ubuntu 16.04 preinstalled. But I
have the same issue on Lenovo T530 where I installed Ubuntu manually.

>From Dell XPS 13 9360:

/etc/buildstamp
kakaduplum Fri, 24 Jun 2016 10:26:40 +
somerville-xenial-amd64-20160624-2

There is no /mnt/bto.xml. Here is list of files I have on
/dev/nvme0n1p2:

boot  casper  debs  dell-e-star  dists  efi.factory  factory  install
installer  isolinux  md5sum.txt  pool  prepackage.dell  preseed  scripts

Please find dpkg.log in attachment



** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5053415/+files/dpkg.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/1748812

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Yuriy Vidineev
Kai-Heng Feng, you can see screenshot before restart in original bug
description:

> screenshot of nm-applet before restart

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Yuriy Vidineev
Shih-Yuan Lee,

> `Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that
Ubuntu supported.

I have this bug on a wide range of kernels from 4.4 to 4.15 We
completely the same behaviour. On 2 laptops with different wi-fi
adapters (ath10k and iwlwifi kernel modules)

Here is complete list of installed kernel versions and on every kernel I
have this bug.

linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
linux-image-4.10.0-40-generic 4.10.0-40.44~16.04.1
linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1
linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2
linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
linux-image-4.13.11-041311-generic 4.13.11-041311.201711020532
linux-image-4.13.3-041303-generic 4.13.3-041303.201709200606
linux-image-4.13.4-041304-generic 4.13.4-041304.201709270931
linux-image-4.14.0-041400-generic 4.14.0-041400.201711122031
linux-image-4.14.2-041402-generic 4.14.2-041402.201711240330
linux-image-4.14.7-041407-generic 4.14.7-041407.201712171031
linux-image-4.14.8-041408-generic 4.14.8-041408.201712200555
linux-image-4.15.0-041500-generic 4.15.0-041500.201802011154
linux-image-4.15.0-041500rc9-generic 4.15.0-041500rc9.201801212130
linux-image-4.4.0-101-generic 4.4.0-101.124
linux-image-4.4.0-103-generic 4.4.0-103.126
linux-image-4.4.0-104-generic 4.4.0-104.127
linux-image-4.4.0-109-generic 4.4.0-109.132
linux-image-4.4.0-112-generic 4.4.0-112.135
linux-image-4.4.0-93-generic 4.4.0-93.116
linux-image-4.4.0-96-generic 4.4.0-96.119
linux-image-4.4.0-97-generic 4.4.0-97.120
linux-image-4.4.0-98-generic 4.4.0-98.121
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-4.9.32-040932-generic 4.9.32-040932.201706141032
linux-image-extra-4.10.0-32-generic 4.10.0-32.36~16.04.1
linux-image-extra-4.10.0-33-generic 4.10.0-33.37~16.04.1
linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1
linux-image-extra-4.10.0-37-generic 4.10.0-37.41~16.04.1
linux-image-extra-4.10.0-38-generic 4.10.0-38.42~16.04.1
linux-image-extra-4.10.0-40-generic 4.10.0-40.44~16.04.1
linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1
linux-image-extra-4.13.0-26-generic 4.13.0-26.29~16.04.2
linux-image-extra-4.13.0-31-generic 4.13.0-31.34~16.04.1
linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1
linux-image-extra-4.4.0-101-generic 4.4.0-101.124
linux-image-extra-4.4.0-103-generic 4.4.0-103.126
linux-image-extra-4.4.0-104-generic 4.4.0-104.127
linux-image-extra-4.4.0-109-generic 4.4.0-109.132
linux-image-extra-4.4.0-112-generic 4.4.0-112.135
linux-image-extra-4.4.0-93-generic 4.4.0-93.116
linux-image-extra-4.4.0-96-generic 4.4.0-96.119
linux-image-extra-4.4.0-97-generic 4.4.0-97.120
linux-image-extra-4.4.0-98-generic 4.4.0-98.121
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic 4.4.0.112.118
linux-image-generic-hwe-16.04 4.13.0.32.52

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  

[Touch-packages] [Bug 1748816] Re: sudo crashed with SIGABRT in kill()

2018-02-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1565332 ***
https://bugs.launchpad.net/bugs/1565332

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1565332
   sudo crashed with SIGABRT in kill()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  apport-crash amd64 third-party-packages xenial need-amd64-retrace

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 03:06:32 2018
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2017-04-22 (295 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: sudo -E env 
PATH=/home/aumy/.local/share/umake/bin:/home/aumy/.local/share/umake/nodejs/nodejs-lang/bin:/home/aumy/.npm_modules/bin:/home/aumy/.local/share/umake/scala/scala-lang/bin:/home/aumy/.local/share/umake/swift/swift-lang/usr/bin:/home/aumy/bin:/home/aumy/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/usr/local/java/jre1.8.0_131/bin:/usr/local/java/jdk1.8.0_131/bin
 /usr/bin/umake games stencyl
  Signal: 6
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x55f5ef300a50, argc=7, argv=0x7fffe8129d98, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffe8129d88) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread GrzesiekC
The same here:

Linux E7470 4.13.0-33-generic #36~16.04.1-Ubuntu SMP Wed Feb 7 23:32:33
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Yuriy Vidineev
Sure thing. But 2 more points that maake me believe it's user space bug:

1. nmcli dev shows correct information (I believe under the hood it uses the 
same syscalls as nm-applet) 
2. I have this bug on a wide range of kernels from 4.4 to 4.15 We completely 
the same behaviour. On 2 laptops with different wi-fi adapters (ath10k and 
iwlwifi kernel modules)

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local

2018-02-11 Thread Launchpad Bug Tracker
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  trying to bind on all interfaces is a good default, but fails on ipv6
  link local

Status in ntp package in Ubuntu:
  Expired

Bug description:
  The default is "grab all" which is great for convenience and can be
  configured to be differently by argument -I (interface) or interface
  commands in the config.

  Currently it is "too" open on that.
  I see it trying to bing link local addresses for each of the KVM guests I 
spawn.
  They get virtual network devices and due to that ntp sees it tries to bind 
and fails.

 Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 
fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested 
address
 Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) 
for fe80::fc54:ff:fec3:3eb0%47#123
 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address 
fe80::fc54:ff:fec3:3eb0%47

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Kai-Heng Feng
So what does it look like before restart?

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Shih-Yuan Lee
`Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that
Ubuntu supported.

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Shih-Yuan Lee
It can not prove if it is a linux kernel bug or not even when you can
recover it from the UI.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Yuriy Vidineev
Here is how nm-applet looks after restart (killall nm-applet && nm-
applet &)

** Attachment added: "Here is how nm-applet looks after restart"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401/+attachment/5053390/+files/Screenshot%20from%202018-02-11%2019-50-55.png

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Yuriy Vidineev
I've filed separate bug
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread Yuriy Vidineev
Here is how nm-applet looks after restart (killall nm-applet && nm-
applet &)

** Attachment added: "Here is how nm-applet looks after restart"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5053391/+files/Screenshot%20from%202018-02-11%2019-50-55.png

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1748812] [NEW] cannot view wifi networks after resume from suspend

2018-02-11 Thread Yuriy Vidineev
Public bug reported:

Hello,
On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have 
the same issue:
After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
I can see current connection via CLI:

nmcli dev
DEVICE   TYPE  STATE  CONNECTION 
docker0  bridgeconnected  docker0
wlp58s0  wifi  connected  Turris 
lo   loopback  unmanaged  -- 

Now I have to run `killall nm-applet && nm-applet &` after every
suspend. That fixes my issue

I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1589401 but I was asked to submit separate bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.2
Uname: Linux 4.15.0-041500rc9-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb 11 19:41:21 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-10-06 (493 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
IpRoute:
 default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
 wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
 lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

** Attachment added: "screenshot of nm-applet before restart"
   
https://bugs.launchpad.net/bugs/1748812/+attachment/5053374/+files/Screenshot%20from%202018-02-11%2019-44-31.png

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Yuriy Vidineev
It's not seems as linux bug because there is how I'm fixing it:

killall nm-applet && nm-applet &

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2018-02-11 Thread Kai-Heng Feng
Yuriy, please file a separate bug. Run `ubuntu-bug linux`.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1725921] Re: Combobox has gray text on gray background

2018-02-11 Thread Daniel van Vugt
** Tags added: xenial

** Summary changed:

- Combobox has gray text on gray background
+ [regression] Combobox has gray text on gray background

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

Title:
  [regression] Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

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

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


[Touch-packages] [Bug 1748620] Re: PulseAudio can not remember my settings between reboots

2018-02-11 Thread Daniel van Vugt
I'm not sure, but suspect PulseAudio has nothing to do with remembering
settings. That's the job of your settings daemon/backend...

Can you please help us to find the right package(s) to assign this bug
to? Just open your settings app, and search the list of running
processes for which one is *-control-center or similar, and then find
which package provides that by running something like:

  dpkg -S `which YOUR-SETTINGS-APP`


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

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

Title:
  PulseAudio can not remember my settings between reboots

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono.
  Tested in ubuntu 18.04 daily

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  apolihron   1590 F pulseaudio
   /dev/snd/controlC0:  apolihron   1590 F pulseaudio
   /dev/snd/controlC2:  apolihron   1590 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 10 15:34:51 2018
  InstallationDate: Installed on 2018-02-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1659785] Re: package linux-firmware 1.157.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-11 Thread chrbau
Is this the same Bug? https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/1745428 (package linux-firmware 1.157.15 failed to
install/upgrade: subprocess installed post-installation script returned
error exit status 1)

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

Title:
  package linux-firmware 1.157.8 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  i can't upgrade from ubuntu 14.04 to 16.04, please help to fix this
  problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.8
  ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-108-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Jan 27 11:09:05 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-25 (2 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.8 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/initramfs-tools/+bug/1659785/+subscriptions

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


[Touch-packages] [Bug 1745428] Re: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-11 Thread chrbau
see also:
 #1742573 package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742573)
and
 #1745113 package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745113)

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

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 16:24:40 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-13 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 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/initramfs-tools/+bug/1745428/+subscriptions

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


[Touch-packages] [Bug 1745713] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-02-11 Thread chrbau
see also:
 #1742573 package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742573)
and
 #1745113 package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745113)

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  new installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan 27 15:50:58 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-01-12 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-02-11 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

** Tags added: artful

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in 

[Touch-packages] [Bug 1725921] Re: Combobox has gray text on gray background

2018-02-11 Thread Daniel van Vugt
** Tags added: regression-update visual-quality

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

Title:
  Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

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

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


[Touch-packages] [Bug 520118] Re: thunar select freezes after using mouse to select folders ("detailed view" mode)

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  thunar select freezes after using mouse to select folders ("detailed
  view" mode)

Status in GTK+:
  Expired
Status in thunar:
  Fix Released
Status in exo package in Ubuntu:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in libfm package in Ubuntu:
  Fix Released
Status in pcmanfm package in Ubuntu:
  Fix Released
Status in exo source package in Lucid:
  Fix Released
Status in gtk+2.0 source package in Lucid:
  Invalid
Status in libfm source package in Lucid:
  Fix Released
Status in pcmanfm source package in Lucid:
  Fix Released

Bug description:
  Binary package hint: thunar

  In thunar, in "detailed view" mode, if you enter a subrepertory by using the 
mouse, once inside you cannot select files, or subfiles to go deeper in the 
repertories. Neither right- click nor left-click are available. However, if you 
entered using the keyboard everything works.
  Once the bug happens, there is no way to interact with the contents of the 
repertory through the window. You have to close the window to open a new one
  This bug will happen every time

  ProblemType: Bug
  Architecture: i386
  Date: Wed Feb 10 23:01:21 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/Thunar
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
  NonfreeKernelModules: wl
  Package: thunar 1.0.1-2ubuntu4
  ProcEnviron:
   LANGUAGE=fr_FR.utf8
   LANG=fr_FR.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
  SourcePackage: thunar
  Uname: Linux 2.6.32-11-generic i686

  
  WORKAROUND: 
  Use icon view or compact view to navigate to the desired folder, then a 
simple Ctrl+2 will show you the detailed view. Another very easy Ctrl+1 or 
Ctrl+3 puts you back in icon view or compact view to navigate again.

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

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


[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

2018-02-11 Thread Daniel van Vugt
I guess the next step would be to try and find that
'rtl8821a_config.bin'. Although I don't know where to get it. It's
certainly missing from the 'linux-firmware' package, which is where I
would expect to see it.

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

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

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => New

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-02-11 Thread Hui Wang
Tested Bionic 1:11.1-1ubuntu6, this bug is fixed by pulseaudio
1:11.1-1ubuntu6.

Please put artful 1:10.0-2ubuntu4 and xenial 1:8.0-0ubuntu3.8 to
proposed channel.

I will test them later.

thanks.


** Tags added: verification-done-bionic

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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


[Touch-packages] [Bug 1725921] Re: Combobox has gray text on gray background on ubuntu 17.10 (gnome)

2018-02-11 Thread Daniel van Vugt
** Project changed: light-themes => ubuntu

** No longer affects: ubuntu

** Summary changed:

- Combobox has gray text on gray background on ubuntu 17.10 (gnome)
+ Combobox has gray text on gray background

** Changed in: ubuntu-themes
   Importance: Undecided => High

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-themes
   Status: New => Triaged

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: artful bionic

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

Title:
  Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

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

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


[Touch-packages] [Bug 1725921] Re: Combobox has gray text on gray background on ubuntu 17.10 (gnome)

2018-02-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

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

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


[Touch-packages] [Bug 1725921] Re: Combobox has gray text on gray background on ubuntu 17.10 (gnome)

2018-02-11 Thread Daniel van Vugt
** Package changed: ubuntu => ubuntu-themes (Ubuntu)

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

Title:
  Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

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

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


[Touch-packages] [Bug 1725921] [NEW] Combobox has gray text on gray background on ubuntu 17.10 (gnome)

2018-02-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

See pictures.

Application: pcbnew
Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
Libraries:
wxWidgets 3.0.3
libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.62.0
Curl: 7.52.1
Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_SPICE=ON

** Affects: light-themes
 Importance: Undecided
 Status: New

** Affects: ubuntu-themes
 Importance: Undecided
 Status: New

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: gnome gui theme
-- 
Combobox has gray text on gray background on ubuntu 17.10 (gnome)
https://bugs.launchpad.net/bugs/1725921
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes 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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-02-11 Thread Daniel van Vugt
Please note most users won't have an ath9k chip, so that bug won't be
relevant to them.

If you _do_ have an ath9k chip (see your 'lsmod' or 'lspci -k') then
yeah bug 1746164 is probably the answer.

Everyone else, please reply to my question in comment #149.

** Attachment removed: "The output of lspci on my system."
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/+attachment/5045388/+files/lspci.txt

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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


[Touch-packages] [Bug 298268] Re: shortcuts for view resize are not displayed in menu

2018-02-11 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu. See this document for currently 
supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test.

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

** Changed in: gtk+2.0 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  shortcuts for view resize are not displayed in menu

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: totem

  Shortcuts exist in Totem to resize the movie window to different zoom
  ratios: 1:1, 2:1, 1:2. There are keyboard shortcuts for these (namely
  '1', '2', and '0') but they are not displayed in the menu.

  Displaying keyboard shortcuts in the menus is the most usable way for
  a user to discover what those shortcuts are, and so they should most
  definitely be displayed there.

  Please add the keyboard shortcuts for these commands to the Totem
  menus.

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

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


[Touch-packages] [Bug 1728184] Re: mozjs38 is no longer supported by Mozilla

2018-02-11 Thread Bug Watch Updater
** Changed in: cinnamon-project
   Status: Unknown => Fix Released

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

Title:
  mozjs38 is no longer supported by Mozilla

Status in Cinnamon:
  Fix Released
Status in libproxy:
  New
Status in 0ad package in Ubuntu:
  Confirmed
Status in cjs package in Ubuntu:
  Triaged
Status in libproxy package in Ubuntu:
  Triaged
Status in mozjs38 package in Ubuntu:
  Triaged

Bug description:
  mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It
  has not been supported by Mozilla since June 2016.

  Please migrate to mozjs52, the only version currently supported by
  Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in
  Debian Testing.

  Currently these packages depend on mozjs38
  --
  0ad (embedded code copy)
  cjs
  libproxy1-plugin-mozjs

  https://github.com/linuxmint/cjs/issues/52
  https://github.com/libproxy/libproxy/issues/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/1728184/+subscriptions

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


[Touch-packages] [Bug 1598295] Re: $GTK_IM_MODULE ignored after upgrade

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Incomplete => Confirmed

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

Title:
  $GTK_IM_MODULE ignored after upgrade

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  After upgrade trusty → xenial, Compose key stopped producing
  configured through ~/.XCompose characters for GTK3 only apps. To be
  sure that its the GTK problem, I created a simple GTK3 window with
  textbox, launched it like:

  $ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

  and the textbox produces wrong characters for Compose key. (the
  variables are actually set globally, I wrote them here just for
  clarity).

  XCompose works fine for all other toolkit's apps, including GTK2 and
  Qt ones.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy libgtk-3-0
  libgtk-3-0:
Installed: 3.18.9-1ubuntu3
Candidate: 3.18.9-1ubuntu3
Version table:
   *** 3.18.9-1ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  «Compose + - + space» would produce «— » in GTK3 apps.

  4) What happened instead

  «Compose + - + space» producing «~» in GTK3 apps.

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

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


[Touch-packages] [Bug 1728184] Re: mozjs38 is no longer supported by Mozilla

2018-02-11 Thread Eli Schwartz
** Bug watch added: github.com/linuxmint/cjs/issues #52
   https://github.com/linuxmint/cjs/issues/52

** Also affects: cinnamon-project via
   https://github.com/linuxmint/cjs/issues/52
   Importance: Unknown
   Status: Unknown

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

Title:
  mozjs38 is no longer supported by Mozilla

Status in Cinnamon:
  Unknown
Status in libproxy:
  New
Status in 0ad package in Ubuntu:
  Confirmed
Status in cjs package in Ubuntu:
  Triaged
Status in libproxy package in Ubuntu:
  Triaged
Status in mozjs38 package in Ubuntu:
  Triaged

Bug description:
  mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It
  has not been supported by Mozilla since June 2016.

  Please migrate to mozjs52, the only version currently supported by
  Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in
  Debian Testing.

  Currently these packages depend on mozjs38
  --
  0ad (embedded code copy)
  cjs
  libproxy1-plugin-mozjs

  https://github.com/linuxmint/cjs/issues/52
  https://github.com/libproxy/libproxy/issues/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/1728184/+subscriptions

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


[Touch-packages] [Bug 1738984] Re: slowness

2018-02-11 Thread Christopher M. Penalver
Wagner Toscano:

>" I'm just finding it very slow."

1) What are you finding slow, the booting process, using the OS after
login, etc.? By how much is it slow in seconds, minutes, etc.?

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

3) Could you please attach a video that demonstrates the slowness?

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

Title:
  slowness

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The boot sometimes fails.
  Many applications, such as Firefox, Chromium, Eclipse and even Nautilus crash 
the system for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  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: Tue Dec 19 07:19:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1458:2272]
  InstallationDate: Installed on 2017-08-15 (125 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=d065c847-7bd5-4dda-ad58-74db9d131eb7 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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 Dec 19 05:45:23 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt Microsoft USB Optical Mouse MOUSE, id 8
   inputMicrosoft Wired Keyboard 400 KEYBOARD, id 9
  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/xorg/+bug/1738984/+subscriptions

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


[Touch-packages] [Bug 1672530] Re: Large amount of message "localhost systemd-udevd[25252]: Process '/bin/chmod 0666 ' failed with exit code 1." logged to syslog

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

http://www.ubuntubuzz.com/2017/07/what-to-do-after-ubuntu-1610-got-
eol.html

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

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

Title:
  Large amount of message "localhost systemd-udevd[25252]: Process
  '/bin/chmod 0666 ' failed with exit code 1." logged to syslog

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The message `localhost systemd-udevd[25252]: Process '/bin/chmod 0666
  ' failed with exit code 1.` makes up more than 50 % of
  `/var/log/syslog`. It is not useful without further information and
  either those should be added, the message be suppressed or the reason
  for it be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules 99-sbig.rules 50-firmware.rules 
60-persistent-v4l.rules 90-alsa-restore.rules 90-alsa-ucm.rules 
51-android.rules 56-hpmud.rules 60-vboxdrv.rules
  Date: Mon Mar 13 21:29:06 2017
  InstallationDate: Installed on 2015-12-12 (457 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (147 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1672530] Re: Large amount of message "localhost systemd-udevd[25252]: Process '/bin/chmod 0666 ' failed with exit code 1." logged to syslog

2018-02-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Large amount of message "localhost systemd-udevd[25252]: Process
  '/bin/chmod 0666 ' failed with exit code 1." logged to syslog

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The message `localhost systemd-udevd[25252]: Process '/bin/chmod 0666
  ' failed with exit code 1.` makes up more than 50 % of
  `/var/log/syslog`. It is not useful without further information and
  either those should be added, the message be suppressed or the reason
  for it be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules 99-sbig.rules 50-firmware.rules 
60-persistent-v4l.rules 90-alsa-restore.rules 90-alsa-ucm.rules 
51-android.rules 56-hpmud.rules 60-vboxdrv.rules
  Date: Mon Mar 13 21:29:06 2017
  InstallationDate: Installed on 2015-12-12 (457 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (147 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1641867] Re: GtkMenu: Submenu navigation triangle doesn't work

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Incomplete => Confirmed

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

Title:
  GtkMenu: Submenu navigation triangle doesn't work

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  The navigation triangle code for keeping a submenu open when the mouse
  is moving diagonally toward it is broken due to incorrect rounding.

  This was reported upstream at:
  https://bugzilla.gnome.org/show_bug.cgi?id=710388

  The attached patch (also submitted upstream) rounds the cursor
  location when calculating the navigation triangle bounds.

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

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


[Touch-packages] [Bug 1748779] [NEW] networking.service should have far less sleeping time

2018-02-11 Thread Cui Wei
Public bug reported:

Many networking service is blocked for this service:
/lib/systemd/system/networking.service.

For most of PC set "iface enp3s0 inet dhcp" in /etc/network/interfaces,
and when they are using wireless network access without wired network
plugged. Currently they have to wait for 5 minute of their booting time.
I think 3-5 sec is reasonable and 0 sec is the best.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ifupdown 0.8.16ubuntu2 [modified: 
lib/systemd/system/networking.service]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 12 01:56:56 2018
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  networking.service should have far less sleeping time

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Many networking service is blocked for this service:
  /lib/systemd/system/networking.service.

  For most of PC set "iface enp3s0 inet dhcp" in
  /etc/network/interfaces, and when they are using wireless network
  access without wired network plugged. Currently they have to wait for
  5 minute of their booting time. I think 3-5 sec is reasonable and 0
  sec is the best.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ifupdown 0.8.16ubuntu2 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 12 01:56:56 2018
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+1340

2018-02-11 Thread Abraham
Hi,

ibus is not working after months gone by. If I check ps aux |grep ibus
shows that ibus is launched. But, there is nothing visible. No panel
menu, no input option if I press SUPER+L . Kindly, let me know if
anything can be done to resolve this.

:~$ ps aux |grep -i ibus
gdm 4848 0.0 0.1 368428 9876 tty1 Sl 20:39 0:00 ibus-daemon --xim --panel 
disable
gdm 4851 0.0 0.0 287000 7508 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-dconf
gdm 4854 0.0 0.3 409656 28012 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
gdm 4917 0.0 0.0 211084 7460 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-engine-simple
admin20+ 5154 0.0 0.1 370704 10304 tty2 Sl 20:40 0:02 ibus-daemon --xim --panel 
disable
admin20+ 5164 0.0 0.0 289112 7564 tty2 Sl 20:40 0:00 /usr/lib/ibus/ibus-dconf
admin20+ 5166 0.0 0.3 411336 28176 tty2 Sl 20:40 0:01 /usr/lib/ibus/ibus-x11 
--kill-daemon
admin20+ 5290 0.0 0.0 213380 7512 tty2 Sl 20:40 0:00 
/usr/lib/ibus/ibus-engine-simple

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

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

2018-02-11 Thread Abraham
*** This bug is a duplicate of bug 1737618 ***
https://bugs.launchpad.net/bugs/1737618

Hi,

ibus is not working after months gone by. If I check ps aux |grep ibus
shows that ibus is launched. But, there is nothing visible. No panel
menu, no input option if I press SUPER+L . Kindly, let me know if
anything can be done to resolve this.

:~$ ps aux |grep -i ibus
gdm   4848  0.0  0.1 368428  9876 tty1 Sl   20:39   0:00 ibus-daemon 
--xim --panel disable
gdm   4851  0.0  0.0 287000  7508 tty1 Sl   20:39   0:00 
/usr/lib/ibus/ibus-dconf
gdm   4854  0.0  0.3 409656 28012 tty1 Sl   20:39   0:00 
/usr/lib/ibus/ibus-x11 --kill-daemon
gdm   4917  0.0  0.0 211084  7460 tty1 Sl   20:39   0:00 
/usr/lib/ibus/ibus-engine-simple
admin20+  5154  0.0  0.1 370704 10304 tty2 Sl   20:40   0:02 ibus-daemon 
--xim --panel disable
admin20+  5164  0.0  0.0 289112  7564 tty2 Sl   20:40   0:00 
/usr/lib/ibus/ibus-dconf
admin20+  5166  0.0  0.3 411336 28176 tty2 Sl   20:40   0:01 
/usr/lib/ibus/ibus-x11 --kill-daemon
admin20+  5290  0.0  0.0 213380  7512 tty2 Sl   20:40   0:00 
/usr/lib/ibus/ibus-engine-simple

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  

[Touch-packages] [Bug 1683077] Re: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: podproces nový pre-removal skript vrátil chybový status 1

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Invalid

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

Title:
  package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to
  install/upgrade: podproces nový pre-removal skript vrátil chybový
  status 1

Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  Problem dialog raised after upgrade to Ubuntu 17.04.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 15 02:04:01 2017
  ErrorMessage: podproces nový pre-removal skript vrátil chybový status 1
  InstallationDate: Installed on 2011-03-16 ( days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to 
install/upgrade: podproces nový pre-removal skript vrátil chybový status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1683077/+subscriptions

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


[Touch-packages] [Bug 1683148] Re: Sound delay with ASUS GL552VW in 17.04

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  Sound delay with ASUS GL552VW in 17.04

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  When I had 16.10 everything was fine but when I've installed 17.04
  (update was failed because X server crashed because of nvidia drivers)
  there is few seconds delay after sound is played, the sound and video
  is in sync but it look like sound is muted when it starts it work when
  playing next sound or when pausing the sound (for instance in
  audacious) but I've got delay when I stop and play again.

  I've try this in /etc/modprobe.d/alsa-base.conf file as mention in
  this thread https://ubuntuforums.org/showthread.php?t=1308604

  options snd-hda-intel model=laptop enable=1 index=0
  options snd-hda-intel power save=0

  but got error in dmesg that those options are not supported:

  [   15.253198] snd_hda_intel: unknown parameter 'power' ignored
  [   15.253199] snd_hda_intel: unknown parameter 'save' ignored

  the first sound test was without delay but the second one was.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kuba  15418 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Apr 16 16:27:58 2017
  InstallationDate: Installed on 2017-04-15 (1 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [GL552VW, Conexant CX20751/2, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-16T15:59:40.113763

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

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


[Touch-packages] [Bug 1683124] Re: package linux-firmware 1.164 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-firmware 1.164 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  error message after upgrading from 16.10 to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 15 11:46:42 2017
  Dependencies:
   
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2013-05-03 (1443 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.164 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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

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


[Touch-packages] [Bug 1683281] Re: package postgresql-common 179 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package postgresql-common 179 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 255 zurück

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  upgrade from ubuntu 16.10 to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: postgresql-common 179
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 15 11:47:14 2017
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 255 zurück
  InstallationDate: Installed on 2013-05-03 (1444 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package postgresql-common 179 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 255 zurück
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (1 days ago)

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

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


[Touch-packages] [Bug 1683518] Re: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 00:41:29 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1684463] Re: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  There is no sound on my pc. I had sound yesterday!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   work   2046 F...m pulseaudio
   /dev/snd/pcmC0D0c:   work   2046 F...m pulseaudio
   /dev/snd/controlC0:  work   2046 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr 20 10:12:51 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-07 (164 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   work   2046 F...m pulseaudio
   /dev/snd/pcmC0D0c:   work   2046 F...m pulseaudio
   /dev/snd/controlC0:  work   2046 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1684324] Re: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upgraded to 17.04 from 16.10 today. Sound worked ok in previous
  versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr 19 19:36:52 2017
  InstallationDate: Installed on 2015-03-28 (753 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.board.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1684332] Re: package click-apparmor 0.3.17 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: click-apparmor (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  Invalid

Bug description:
  This happens when I am upgrading from 16.10 to 17.04 via terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 19 20:38:04 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
new pre-removal 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/click-apparmor/+bug/1684332/+subscriptions

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


[Touch-packages] [Bug 1684506] Re: QT4 Trolltech.conf settings lost after reboot

2018-02-11 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: qt4-x11 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  QT4 Trolltech.conf settings lost after reboot

Status in qt4-x11 package in Ubuntu:
  Invalid

Bug description:
  Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based
  applications (e.g. KeePassX) render using wrong font instead of my
  personal configured font. When I run qtconfig-qt4 (4.8.7), change font
  and click 'save', a fresh .config/Trolltech.conf is saved, contains
  the correct font config and all qt4 applications now show correct
  font. These settings however do not survive a reboot although
  Trolltech.conf exists and contains correct settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.11 x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 20 10:33:21 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1684506/+subscriptions

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


[Touch-packages] [Bug 1748757] [NEW] package linux-firmware 1.157.14 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2018-02-11 Thread soisig albet
Public bug reported:

the error message appear at the end of the boot

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.14
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Feb  5 19:59:44 2018
Dependencies:
 
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2017-04-04 (312 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.14 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package linux-firmware 1.157.14 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  the error message appear at the end of the boot

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.14
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Feb  5 19:59:44 2018
  Dependencies:
   
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-04-04 (312 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.14 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1748553] Re: bash 4.4.18 failed to extract

2018-02-11 Thread Hans Joachim Desserud
** Tags added: armhf unmetdeps

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

Title:
  bash 4.4.18 failed to extract

Status in bash package in Ubuntu:
  New

Bug description:
  Selecting previously unselected package bash.
  dpkg: regarding .../bash_4.4.18-1ubuntu1_armhf.deb containing bash, 
pre-dependency problem:
   bash pre-depends on libtinfo5 (>= 6)
libtinfo5 is not installed.

  dpkg: warning: ignoring pre-dependency problem!
  Preparing to unpack .../bash_4.4.18-1ubuntu1_armhf.deb ...
  preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 
0' failed.
  qemu: uncaught target signal 6 (Aborted) - core dumped
  dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-1ubuntu1_armhf.deb (--unpack):
   new bash package pre-installation script subprocess was killed by signal 
(Aborted), core dumped

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

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


[Touch-packages] [Bug 1745027] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-11 Thread gl
Hi, Solution from dna did not work for me.  
I did the recoomended steps from robin this way: 

1. sudo /usr/sbin/sshd -t && echo PASS || echo FAIL

Result: PASS

2. sudo systemctl restart ssh.service

Results: 
Job for ssh.service failed because the control process exited with error code. 
See "systemctl status ssh.service" and "journalctl -xe" for details.

3. sudo systemctl status ssh.service

ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since So 2018-02-11 14:57:02 CET; 39s ago
  Process: 12337 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
 Main PID: 12337 (code=exited, status=255)

Feb 11 14:57:02 de systemd[1]: Starting OpenBSD Secure Shell server...
Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on 0.0.0.0 
failed: Address already in 
Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on :: failed: 
Address already in use.
Feb 11 14:57:02 de sshd[12337]: fatal: Cannot bind any address.
Feb 11 14:57:02 de systemd[1]: ssh.service: Main process exited, 
code=exited, status=255/n/a
Feb 11 14:57:02 de systemd[1]: Failed to start OpenBSD Secure Shell 
server.
Feb 11 14:57:02 de systemd[1]: ssh.service: Unit entered failed state.
Feb 11 14:57:02 de systemd[1]: ssh.service: Failed with result 
'exit-code'.

Any Idea?

Thanks

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Started installing upgrade new kernels.
  But yesterday i did not finish seting up vlan.
  So in sshd config remained a address for vlan.
  in net conf was set up automatic vlan conf

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Tue Jan 23 21:47:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-11-12 (803 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 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/openssh/+bug/1745027/+subscriptions

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


[Touch-packages] [Bug 1748723] [NEW] HP Laserjet1018 detected by 17.10 but not print anything

2018-02-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Cuos and HPLIB are installed but HP-Check show errors
The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined as 
standard printer
I can start a print request, it goes in the print queue and finished without 
printing.
On Ubuntu 16.04 everything works fine after install HPLIP

See same in attachment THANKS

cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check
Saving output in log file: /home/cyborg2058/hp-check.log

HP Linux Imaging and Printing System (ver. 3.17.7)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: 12-17.10 version is not supported. Using 12-17.04 versions
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux
 Host: cyborg2058-Z370-HD3P
 Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux
 Distribution: 12 17.10
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.17.7
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for 12 distro  
17.10 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.17.7

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=yes
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=yes
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.17.7
restricted-build=no
ui-toolkit=qt5
qt3=no
qt4=no
qt5=yes
policy-kit=yes
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[installation]
date_time = 02/11/18 10:25:05
version = 3.17.7


 


-
| External Dependencies |
-

 error: cups  CUPS - Common Unix Printing System
   REQUIRED1.1 -   INCOMPAT   'CUPS may not be 
installed or not running'
 gs   GhostScript - PostScript and PDF language interpreter and 
previewer REQUIRED7.059.21OK -
 error: xsane xsane - Graphical scanner frontend for SANE   
   OPTIONAL0.9 -   MISSING'xsane needs to 
be installed'
 scanimagescanimage - Shell scanning program
   OPTIONAL1.0 1.0.27  OK -
 error: dbus  DBus - Message bus system 
   REQUIRED-   1.10.22 MISSING'DBUS may not be 
installed or not running'
 policykitPolicyKit - Administrative policy framework 

[Touch-packages] [Bug 1748723] Re: HP Laserjet1018 detected by 17.10 but not print anything

2018-02-11 Thread Kay Erdmann
** Package changed: ubuntu => cups (Ubuntu)

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

Title:
  HP Laserjet1018 detected by 17.10 but not print anything

Status in cups package in Ubuntu:
  New

Bug description:
  Cuos and HPLIB are installed but HP-Check show errors
  The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined 
as standard printer
  I can start a print request, it goes in the print queue and finished without 
printing.
  On Ubuntu 16.04 everything works fine after install HPLIP

  See same in attachment THANKS

  cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check
  Saving output in log file: /home/cyborg2058/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.17.7)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the
  HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies
  are installed to successfully compile HPLIP.  
  
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro  
  
  supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
  
  has the proper dependencies installed to successfully run.
  
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode  
  
  will check both of the above cases (both compile- and run-time dependencies). 
  

  Check types:  
  
  a. EXTERNALDEP - External Dependencies
  
  b. GENERALDEP - General Dependencies (required both at compile and run time)  
  
  c. COMPILEDEP - Compile time Dependencies 
  
  d. [All are run-time checks]  
  
  PYEXT SCANCONF QUEUES PERMISSION  
  

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: 12-17.10 version is not supported. Using 12-17.04 versions
  dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 
GNU/Linux
   Host: cyborg2058-Z370-HD3P
   Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux
   Distribution: 12 17.10
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.17.7
  HPLIP-Home: /usr/share/hplip
  warning: HPLIP-Installation: Auto installation is not supported for 12 distro 
 17.10 version 

  Current contents of '/etc/hp/hplip.conf' file:
  # hplip.conf.  Generated from hplip.conf.in by configure.

  [hplip]
  version=3.17.7

  [dirs]
  home=/usr/share/hplip
  run=/var/run
  ppd=/usr/share/ppd/hplip/HP
  ppdbase=/usr/share/ppd/hplip
  doc=/usr/share/doc/hplip
  html=/usr/share/doc/hplip-doc
  icon=no
  cupsbackend=/usr/lib/cups/backend
  cupsfilter=/usr/lib/cups/filter
  drv=/usr/share/cups/drv
  bin=/usr/bin
  apparmor=/etc/apparmor.d
  # Following values are determined at configure time and cannot be changed.
  [configure]
  network-build=yes
  libusb01-build=no
  pp-build=yes
  gui-build=yes
  scanner-build=yes
  fax-build=yes
  dbus-build=yes
  cups11-build=no
  doc-build=yes
  shadow-build=no
  hpijs-install=yes
  foomatic-drv-install=yes
  foomatic-ppd-install=yes
  foomatic-rip-hplip-install=no
  hpcups-install=yes
  cups-drv-install=yes
  cups-ppd-install=no
  internal-tag=3.17.7
  restricted-build=no
  ui-toolkit=qt5
  qt3=no
  qt4=no
  qt5=yes
  policy-kit=yes
  lite-build=no
  udev_sysfs_rules=no
  hpcups-only-build=no
  hpijs-only-build=no
  apparmor_build=no

  
  Current contents of '/var/lib/hp/hplip.state' file:
  Plugins are not installed. Could not access file: No such file or directory

  Current contents of '~/.hplip/hplip.conf' file:
  [installation]
  date_time = 02/11/18 10:25:05
  version = 3.17.7

  
   


  -
  | External Dependencies |
  -

   error: cups  CUPS - Common Unix Printing System  
 REQUIRED1.1 -   INCOMPAT   'CUPS may not 
be installed or not running'
   gs   GhostScript - PostScript and PDF language interpreter 
and previewer REQUIRED7.059.21OK -
   error: xsane xsane 

[Touch-packages] [Bug 883138] Re: Dim file extensions

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Incomplete => Confirmed

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

Title:
  Dim file extensions

Status in GTK+:
  Confirmed
Status in Nautilus:
  Confirmed
Status in Wine:
  New
Status in enlightenment package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in lesstif2 package in Ubuntu:
  New
Status in mono package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged
Status in qt4-x11 package in Ubuntu:
  Opinion
Status in tcltk-defaults package in Ubuntu:
  New
Status in wine package in Ubuntu:
  Incomplete

Bug description:
  Many web browsers have now began dimming less relevant parts of the URL, such 
as the protocol, subdomain, path, and query string.
  I propose we have an option/setting/feature that does the same Nautilus and 
Gtk file dialogs. Dim the the file extension.

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

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


Re: [Touch-packages] [Bug 1738984] Re: slowness

2018-02-11 Thread Wagner Toscano
Hello!
I'm not having boot failure, I'm just finding it very slow.
I chose to open the boot log (boot.log), but it is empty. I am sending the
bootstrap.log.
I hope this is what you asked for.

Thank you for your attention.

2018-02-07 1:53 GMT-02:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:

> w...@wagnertoscano.eti.br, thank you for reporting this and helping make
> Ubuntu better.
>
> 1) Could you please provide a log of a failed boot following
> https://wiki.ubuntu.com/DebuggingKernelBoot ?
>
> ** Tags added: bios-outdated-fc
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738984
>
> Title:
>   slowness
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The boot sometimes fails.
>   Many applications, such as Firefox, Chromium, Eclipse and even Nautilus
> crash the system for a while.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
>   Uname: Linux 4.4.0-104-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.14
>   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: Tue Dec 19 07:19:17 2017
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9
> 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
>  Subsystem: Gigabyte Technology Co., Ltd Curacao XT [Radeon R7 370 /
> R9 270X/370 OEM] [1458:2272]
>   InstallationDate: Installed on 2017-08-15 (125 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic
> root=UUID=d065c847-7bd5-4dda-ad58-74db9d131eb7 ro drm.debug=0xe
> plymouth:debug
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/23/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: FB
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: 990FXA-UD5
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/23/2013:
> svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:
> rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.
> E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>   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 Dec 19 05:45:23 2017
>   xserver.configfile: default
>   xserver.devices:
>inputPower Button KEYBOARD, id 6
>inputPower Button KEYBOARD, id 7
>inputPixArt Microsoft USB Optical Mouse MOUSE, id 8
>inputMicrosoft Wired Keyboard 400 KEYBOARD, id 9
>   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/xorg/+bug/1738984/+subscriptions
>


-- 
- -
Wagner Toscano
Mestre em Sistemas Digitais - Inteligência Computacional - PCS-POLI-USP
Professor Universitário
Consultor independente: www.wagnertoscano.eti.br


** Attachment added: "bootstrap.log"
   
https://bugs.launchpad.net/bugs/1738984/+attachment/5053077/+files/bootstrap.log

-- 
You received this bug notification because you are a 

[Touch-packages] [Bug 1743710] Re: Since 2018 text in combo boxes is dark and unreadable

2018-02-11 Thread Eldar Khayrullin
*** This bug is a duplicate of bug 1725921 ***
https://bugs.launchpad.net/bugs/1725921

** This bug has been marked a duplicate of bug 1725921
   Combobox has gray text on gray background on ubuntu 17.10 (gnome)

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

Title:
  Since 2018 text in combo boxes is dark and unreadable

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Since 2018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

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

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


[Touch-packages] [Bug 1748729] Re: Xorg freeze

2018-02-11 Thread BertN45
I see the bug report talks about software rendering, but I do use 3D
acceleration and the problem only occurs when I select 3D acceleration.
With 3D acceleration disabled everything work fine.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu. 
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, Peppermint 8 and Windows 7 and 10 work without
  any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 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: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d 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.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1746771] Re: black background drop-down menu

2018-02-11 Thread Eldar Khayrullin
*** This bug is a duplicate of bug 1725921 ***
https://bugs.launchpad.net/bugs/1725921

** This bug is no longer a duplicate of bug 1743710
   Since 2018 text in combo boxes is dark and unreadable
** This bug has been marked a duplicate of bug 1725921
   Combobox has gray text on gray background on ubuntu 17.10 (gnome)

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

Title:
  black background drop-down menu

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1748729] [NEW] Xorg freeze

2018-02-11 Thread BertN45
Public bug reported:

I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu. 
The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
17.10, Xubuntu 17.10, Peppermint 8 and Windows 7 and 10 work without any
problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 11 06:31:52 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: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2017-12-22 (50 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d 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.89-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze reproducible single-occurrence 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/1748729

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu. 
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, Peppermint 8 and Windows 7 and 10 work without
  any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 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: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro 

[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

2018-02-11 Thread Sjors
I know I don’t need Windows to compile for Windows, but I’m writing /
updating those instructions for Windows users. Currently the Ubuntu 16
instructions tell the user to add sources from a newer release, which
could cause problems.

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

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

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

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


[Touch-packages] [Bug 259068] Re: gnome-panel crashed with SIGSEGV in gdk_screen_get_monitor_geometry()

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: New => Expired

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

Title:
  gnome-panel crashed with SIGSEGV in gdk_screen_get_monitor_geometry()

Status in GNOME Panel:
  Invalid
Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-panel

  short after rotation

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/gnome-panel
  Package: gnome-panel 1:2.23.6-0ubuntu3
  ProcAttrCurrent: unconfined
  ProcCmdline: gnome-panel
  ProcEnviron:
   SHELL=/bin/bash
   
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=de_DE.UTF-8
  Signal: 11
  SourcePackage: gnome-panel
  StacktraceTop:
   gdk_screen_get_monitor_geometry ()
   ?? () from /usr/lib/libgtk-x11-2.0.so.0
   g_cclosure_marshal_VOID__BOXED ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: gnome-panel crashed with SIGSEGV in gdk_screen_get_monitor_geometry()
  Uname: Linux 2.6.26-5-generic i686
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev powerdev pulse pulse-access pulse-rt sambashare scanner vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/259068/+subscriptions

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


[Touch-packages] [Bug 777246] Re: Memory leak: Circular reference in GtkMenuItem

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: New => Incomplete

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

Title:
  Memory leak: Circular reference in GtkMenuItem

Status in GTK+:
  Incomplete
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  I have an application (glipper) in which I update the menu quite
  frequently, and I noticed a slow rise in memory usage while running,
  and I tracked it down to GtkMenuItem.

  I noticed this in Ubuntu 10.10, but since there were only a few days
  to 11.04, I decided to wait. I can also confirm the bug in 11.04.

  Please note that this leak happens only if the GtkMenuItem has a
  label. There's no leak if it doesn't have a label.

  Proof code attached. Glipper is written in Python (with PyGTK), so the
  first thing I did to track this down was to create the simplest python
  program that demonstrates the bug. Using my friend Google, I managed
  to write the same code in Vala and compile it to C (to confirm it
  doesn't do anything else but create and destroy GtkMenuItem objects).
  The leak still exists after compiling the C source.

  How to test:
  1. Start "top", sort by memory (  )
  2. Run either the python script or the binary resulting from the Vala or C 
sources.
  3. Watch the program rise in "top". It will take less than a minute to become 
noticeable.

  Reading the source, unless I missed something, I should have at most
  one GtkMenuItem at any time, so the memory usage should not increase.
  So far, the workaround is to explicitly destroy the GtkMenuItem, but
  it's not that convenient.

  There may be a similar, but not as evident issue in GtkMenu after
  removing a GtkMenuItem, but I haven't pursued that possible problem
  yet. I'll file another bug report if I can confirm the GtkMenu leak
  it's not just my imagination.

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

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


[Touch-packages] [Bug 1056300] Re: If a GTK application quits the main loop and restarts it again, accessibility is lost.

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: New => Expired

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

Title:
  If a GTK application quits the main loop and restarts it again,
  accessibility is lost.

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Quantal:
  Fix Released
Status in ubiquity source package in Quantal:
  Fix Released

Bug description:
  On the quantal beta 2 image - 20120925, I'm trying to do the
  screenreader test.  So far I've been able to reproduce this with both
  i386 and amd64+mac.  After starting orca, things seem to work ok
  through the welcome screen in ubiquity, but then it quits reading.
  Starting with the screen titled "Install" with the text at the top
  "Preparing to install Ubuntu", it doesn't read the screen any longer.
  Nor does it seem to tell me when I press keys like enter to move on.
  Other apps are still read to me after this by orca though.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.3
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.324
  Date: Tue Sep 25 16:16:51 2012
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64+mac (20120925)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-02-11 Thread Hui Wang
Reply comment #45:

Yes, it also fix the bug 1745765.


** Tags removed: verification-failed-xenial

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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


[Touch-packages] [Bug 1748709] Re: Upgrade from xenial to bionic wants to replace moduli

2018-02-11 Thread Hans Joachim Desserud
** Tags added: xenial2bionic

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

Title:
  Upgrade from xenial to bionic wants to replace moduli

Status in openssh package in Ubuntu:
  New

Bug description:
  I see this on upgrade on one machine, which is unexpected. If this
  file is generated by each machine, why would we ship a default?

  Configuration file '/etc/ssh/moduli'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** moduli (Y/I/N/O/D/Z) [default=N] ?

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

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


[Touch-packages] [Bug 390735] Re: Colour of font on panel and desktop should be customisable

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Incomplete

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

Title:
  Colour of font on panel and desktop should be customisable

Status in GTK+:
  Incomplete
Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Right now, the colour of the fonts on the Desktop icons and panel
  changes at random (often to contrast with panel background
  colour/theme/wallpaper) but it does not always get it right.
  Especially if the theme or wallpaper has different colours in
  different areas.

  Both of these should be easily customisable.

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

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


[Touch-packages] [Bug 543088] Re: nautilus tabs are stretched over the entire width of the screen

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  nautilus tabs are stretched over the entire width of the screen

Status in GTK+:
  Expired
Status in Nautilus:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  As you can see in the screenshot, the previous nautilus version showed neat, 
evenly wide tabs.
  The new version stretches them over the entire screen, which is ridiculous 
when you have only 2 tabs open on a large screen.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Mar 21 01:03:21 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  Package: nautilus 1:2.29.92.1-0ubuntu1
  ProcEnviron:
   LANG=nl_BE.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.32-16-generic x86_64

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

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


[Touch-packages] [Bug 487604] Re: Ctrl- key mappings broken for anything but first keyboard layout in GTK applications

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Incomplete

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

Title:
  Ctrl- key mappings broken for anything but first keyboard layout in
  GTK applications

Status in GTK+:
  Incomplete
Status in gtk+2.0 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  * Have two keyboard layouts (e.g. US and US Dvorak)
  * Note that when in the first one in the list, all keys function as expected.
  * When in the 2nd one, the Ctrl- mappings in Gtk applications use the first 
layout.

  (gnome-terminal is a good test application)

  Workaround:
  * When changing layouts for any reasonable amount of work, rather than use 
the keyboard layout applet, re-order the layouts in the keyboard preferences so 
the preferred layout is on top.

  This is a long-standing GTK bug for people who use multiple keyboard
  layouts, and as the problem has never been well understood, there are
  many misfiled bugs on it (e.g. bug #204202).

  Present in karmic and every previous version I can remember.

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

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


[Touch-packages] [Bug 206837] Re: Gedit text area has small gap between edge of text area and edge of window

2018-02-11 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Incomplete

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

Title:
  Gedit text area has small gap between edge of text area and edge of
  window

Status in GTK+:
  Incomplete
Status in One Hundred Papercuts:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Ubuntu Hardy beta, gedit 2.22.0-0ubuntu1

  There is a 1 pixel gap between the edge of the window and the edge of
  the text edit area. When maximised and the scroll bar is present one
  can't reach the scrollbar by hitting the screen edge with the pointer.
  A similar gap exists on the left, but is not as critical.

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

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


[Touch-packages] [Bug 1746579] Re: A boxes instead of a Cyrillic chars in VTs

2018-02-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  A boxes instead of a Cyrillic chars in VTs

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
Встановлено: 1.166ubuntu7
Кандидат:1.166ubuntu7
Таблиця версій:
   *** 1.166ubuntu7 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  I expected to have cyrillic fonts in any of six VTs, /dev/tty[1-6],
  but it shows boxes instead of them. Please, see screen shot in
  attachment.

  It's very likely that this is an old bug that was fixed earlier but it
  appeared it 18.04 dev again. Here it is:
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1565542

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jan 31 20:46:57 2018
  InstallationDate: Installed on 2018-01-12 (19 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180103)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  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/1746579/+subscriptions

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


[Touch-packages] [Bug 1748709] [NEW] Upgrade from xenial to bionic wants to replace moduli

2018-02-11 Thread Mark Shuttleworth
Public bug reported:

I see this on upgrade on one machine, which is unexpected. If this file
is generated by each machine, why would we ship a default?

Configuration file '/etc/ssh/moduli'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** moduli (Y/I/N/O/D/Z) [default=N] ?

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

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

Title:
  Upgrade from xenial to bionic wants to replace moduli

Status in openssh package in Ubuntu:
  New

Bug description:
  I see this on upgrade on one machine, which is unexpected. If this
  file is generated by each machine, why would we ship a default?

  Configuration file '/etc/ssh/moduli'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** moduli (Y/I/N/O/D/Z) [default=N] ?

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

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