date:20181115

[Expired for qtbase-opensource-src (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  qBittorrent or any qt 5 applications still crashing on ubuntu 16.10

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

Bug description:
  
  https://bugs.launchpad.net/ubuntu/+source/qbittorrent/+bug/1630848

  https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

  Meanwhile it still not fixed in Ubuntu 16.10 Yakkety. Since 2016-10-21
  "patch" was backported from qt 5.8. All Qt5 applications with plugin
  architecture creahing on exit.

  Like typical strace from qbittorrent:

  #0  0x77eba5df in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #1  0x75eda019 in QHashData::free_helper(void (*)(QHashData::Node*)) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #2  0x77ecd06f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #3  0x75e77ed3 in QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #4  0x76050a2c in QCoreApplicationPrivate::cleanupThreadData() () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #5  0x7639a84b in QGuiApplicationPrivate::~QGuiApplicationPrivate() 
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #6  0x77524869 in QApplicationPrivate::~QApplicationPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #7  0x760862c7 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #8  0x76052ec6 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #9  0x77526331 in QApplication::~QApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

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

[Touch-packages] [Bug 1803649] [NEW] gtk plugin is missing

2018-11-15 Thread INIZAN yannick

Public bug reported:

Gtk plugin is missing. It was transferred from "bad" to "good" on
February 10, 2018 : https://cgit.freedesktop.org/gstreamer/gst-plugins-
good/commit/?id=a12f8df0c6933af629d7d75585a42371e59e9021

obviously this plugin is also absent from "bad" package

tested distro : Cosmic / Dingo
package version : 1.14.4-1ubuntu1

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gtk plugin is missing

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  Gtk plugin is missing. It was transferred from "bad" to "good" on
  February 10, 2018 : https://cgit.freedesktop.org/gstreamer/gst-
  plugins-good/commit/?id=a12f8df0c6933af629d7d75585a42371e59e9021

  obviously this plugin is also absent from "bad" package

  tested distro : Cosmic / Dingo
  package version : 1.14.4-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1803649/+subscriptions

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

[Touch-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

Reassigned to the kernel.

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

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

Status in linux package in Ubuntu:
  New

Bug description:
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech
  touchpad stopped working. This means it is not recognized at all. This
  problem occured after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  
  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS001AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS001AGE
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

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

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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

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

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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

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

Thanks for the bug report.

The backtrace in your log may not be completely accurate:

[ 83021.728] (EE) Backtrace:
[ 83021.730] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560581eab229]
[ 83021.731] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
[0x7f3cc6de2e1f]
[ 83021.731] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_get_pixmap_texture+0x7d) [0x7f3cc557244d]
[ 83021.732] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0x7b08) [0x7f3cc5584988]
[ 83021.732] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0x7f3c) [0x7f3cc558512c]
[ 83021.732] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0x854e) [0x7f3cc55858ce]
[ 83021.732] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0xa54c) [0x7f3cc558952c]
[ 83021.733] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) 
[0x560581e2d79f]
[ 83021.733] (EE) 8: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0x1137e) [0x7f3cc559787e]
[ 83021.734] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x41a5) [0x560581e260c5]
[ 83021.734] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) 
[0x560581d4c97e]
[ 83021.734] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x560581d50906]
[ 83021.734] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) 
[0x7f3cc6c0409b]
[ 83021.734] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x560581d3a67a]

so we will need a better stack trace. To help us find the cause of the
crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This bug is happening approximately every 24 hours. Any changes to
  open files are lost (DATA LOSS BEING EXPERIENCED).

  System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to
  date with all publish updates.

  System has two graphics card: 
  1) NVidia GK208B [GeForce GT 710]
  2) NVidia GT218 [GeForce 210]

  I am reluctant to switch to nvida drivers as google searches indicate
  that they do not support dual head systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 15 16:18:02 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b]
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
  InstallationDate: Installed on 2018-11-07 (7 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=9d341c90-212b-47c2-b0f0-a7e607ee860b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled

[Touch-packages] [Bug 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible

Please try logging into "Ubuntu on Wayland" instead of "Ubuntu" and tell
us if that stopps the bug from happening.

** Summary changed:

- Application windows in 18.04.01 go black but launcher is still visible
+ [radeon] Application windows in 18.04.01 go black but launcher is still 
visible

** Tags added: radeon

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

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

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

Title:
  [radeon] Application windows in 18.04.01 go black but launcher is
  still visible

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2018-11-15 Thread Dimitri John Ledkov

** Information type changed from Public to Public Security

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
  systemd+   153 1  0 15:34 ?00:00:00 /lib/systemd/systemd-networkd
  systemd+   154 1  0 15:34 ?00:00:00 /lib/systemd/systemd-resolved
  message+   194

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2018-11-15 Thread Dimitri John Ledkov

@ Security team please consider uploading the attached debdiff as
237-3ubuntu10.7 into security pocket to resolve hangs on shutdown when
applying updates on shutdown.

** Changed in: systemd (Ubuntu Disco)
   Status: New => Fix Committed

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

** Patch added: "systemd_237-3ubuntu10.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5213236/+files/systemd_237-3ubuntu10.7.debdiff

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and

[Touch-packages] [Bug 1799693] Re: Stable libopus-1.3 released

2018-11-15 Thread Ethan R. Jones

I can try doing this myself if someone wants to point me to the
documentation of rebasing/repacking/etc.

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

Title:
  Stable libopus-1.3 released

Status in opus package in Ubuntu:
  New

Bug description:
  Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now 
outdated and technically marked as a beta. 
  http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html

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

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

[Touch-packages] [Bug 1694006] Re: Tracker error slows down system and breaks suspend to RAM

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

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

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

Title:
  Tracker error slows down system and breaks suspend to RAM

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  By default Budgie installs tracker.

  $ tracker status

  (tracker status:11680): Tracker-WARNING **: tracker-backend.vala:211: Falling 
back to bus backend, the direct backend failed to initialize: unable to open 
database file
  Could not get basic status for Tracker, 
GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such table: 
nfo:FileDataObject

  in syslog:

  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  May 27 13:02:32 mbpr15 tracker-extract[11366]: char* 
poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed
  

  May 27 13:06:23 mbpr15 tracker-extract[11638]: Could not insert metadata for 
item "file:///home/wolf/Documents/books/it-vertrage-kurz-und-praktisch.pdf": 
42.33: invalid UTF-8 character
  May 27 13:06:23 mbpr15 tracker-extract[11638]: If the error above is 
recurrent for the same item/ID, consider running "tracker-extract" in the 
terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug 
with the additional information

  

  This slows down the system tremendously. As a side effect, the system
  can't go into suspend to RAM mode (wakes up every second)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: tracker 1.12.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 27 13:04:43 2017
  InstallationDate: Installed on 2017-05-25 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1803601] [NEW] motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

2018-11-15 Thread Simon Déziel

Public bug reported:

update-motd(5) says:

 Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the 
root user at each 
 login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
 tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
 a few caveats).

So sysadmins are used to "chmod -x" motd fragments from /etc/update-
motd.d/ to prevent their execution. When doing so for /etc/update-
motd.d/50-motd-news, I noticed that motd-news.timer was still trying to
execute the motd-news.service unit which then logged a failure:

 systemd[3704]: motd-news.service: Failed to execute command: Permission denied
 systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
  Permission denied
 systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
 systemd[1]: motd-news.service: Failed with result 'exit-code'.
 systemd[1]: Failed to start Message of the Day.


This problem was observed on a Bionic system:

$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
$ apt-cache policy base-files
base-files:
  Installed: 10.1ubuntu2.3
  Candidate: 10.1ubuntu2.3
  Version table:
 *** 10.1ubuntu2.3 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 10.1ubuntu2.2 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 10.1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

But the problem also exist in Disco.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  New

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each 
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
Installed: 10.1ubuntu2.3
Candidate: 10.1ubuntu2.3
Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

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

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

[Touch-packages] [Bug 1803600] [NEW] Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

2018-11-15 Thread Thilo

Public bug reported:

When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech
touchpad stopped working. This means it is not recognized at all. This
problem occured after the first boot in 18.10

`dmesg | grep -i elantech` shows the following errors:

[3.409043] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
[3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8
[3.464905] psmouse serio1: elantech: Trying to set up SMBus access
[5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
[5.586505] elan_i2c 0-0015: failed to get resolution: -71
[5.586527] elan_i2c: probe of 0-0015 failed with error -71

uname:

$ uname -a
Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
https://bugs.archlinux.org/task/59714

Running the following command enables it again for the current session:

sudo sh -c 'echo -n "elantech">
/sys/bus/serio/devices/serio1/protocol'

dmesg afterwards:

[  569.522490] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
[  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8

Before running the fix:

$ cat /sys/bus/serio/devices/serio1/protocol
ETSMBus

and after:

$ cat /sys/bus/serio/devices/serio1/protocol
ETPS/2


After reboot the command has to be run again, of course.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Nov 15 20:59:36 2018
DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
 virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
 virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
InstallationDate: Installed on 2018-08-06 (101 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: LENOVO 20LS001AGE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
dmi.bios.date: 02/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET37W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic kubuntu third-party-packages 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/1803600

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

Status in xorg package in Ubuntu:
  New

Bug description:
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech
  touchpad stopped working. This means it is not recognized at all. This
  problem occured after the first boot in 18.10

[Touch-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

2018-11-15 Thread Thilo

Sorry, this is not meant to be in xorg. (Or I actually don't know...)
However the bug-report application itsself seems to be buggy ;) (or the
user using it)

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

Status in xorg package in Ubuntu:
  New

Bug description:
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech
  touchpad stopped working. This means it is not recognized at all. This
  problem occured after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  
  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS001AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS001AGE
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications

[Touch-packages] [Bug 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

2018-11-15 Thread Simon Déziel

A possible fix would be to make the unit execution conditional to the
update-motd fragment being executable:

  [Unit]
  ConditionFileIsExecutable=/etc/update-motd.d/50-motd-news

I'm not sure if this should be added to motd-news.service, motd-
news.timer or both.

** Description changed:

  update-motd(5) says:
  
-  Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each 
-  login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
-  tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
-  a few caveats).
+  Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
+  login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
+  tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
+  a few caveats).
  
  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying to
  execute the motd-news.service unit which then logged a failure:
  
-  systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
-  systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
-   Permission denied
-  systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
-  systemd[1]: motd-news.service: Failed with result 'exit-code'.
-  systemd[1]: Failed to start Message of the Day.
+  systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
+  systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
+   Permission denied
+  systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
+  systemd[1]: motd-news.service: Failed with result 'exit-code'.
+  systemd[1]: Failed to start Message of the Day.
+ 
+ 
+ The motd-news.service unit looks like this:
+ 
+ $ systemctl cat motd-news.service
+ # /lib/systemd/system/motd-news.service
+ [Unit]
+ Description=Message of the Day
+ After=network-online.target
+ Documentation=man:update-motd(8)
+ 
+ [Service]
+ Type=oneshot
+ ExecStart=/etc/update-motd.d/50-motd-news --force
  
  
  This problem was observed on a Bionic system:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
-   Installed: 10.1ubuntu2.3
-   Candidate: 10.1ubuntu2.3
-   Version table:
-  *** 10.1ubuntu2.3 500
- 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  10.1ubuntu2.2 500
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
-  10.1ubuntu2 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 10.1ubuntu2.3
+   Candidate: 10.1ubuntu2.3
+   Version table:
+  *** 10.1ubuntu2.3 500
+ 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  10.1ubuntu2.2 500
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+  10.1ubuntu2 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  But the problem also exist in Disco.

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  New

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the

[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager

2018-11-15 Thread Steve Langasek

(In which case, I think this still warrants improvement, since AIUI the
next run of update-manager will do removals after installations, which
means a high water mark of 4 kernels rather than 3 which is what we
want)

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

Title:
  kernel from bionic did not get autoremoved by either unattended-
  upgrades or update-manager

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I happened to run apt manually on my system this morning to remove a
  package, and I was informed:

  The following packages were automatically installed and are no longer 
required:
linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic
linux-modules-extra-4.15.0-36-generic

  This was surprising, since I have run update-manager yesterday (with
  no intervening reboot), and unattended-upgrades is enabled, and both
  of those packages should have already removed this stale kernel before
  now.

  After apt autoremove, my current installed packages are:

  $ dpkg -l linux-image'*' | grep ^ii
  ii  linux-image-4.18.0-10-generic  4.18.0-10.11 amd64Signed 
kernel image generic
  ii  linux-image-4.18.0-11-generic  4.18.0-11.12 amd64Signed 
kernel image generic
  ii  linux-image-generic4.18.0.11.12 amd64Generic 
Linux kernel image
  $

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

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

[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager

2018-11-15 Thread Steve Langasek

History log:

Start-Date: 2018-11-14  17:21:44
Commandline: aptdaemon role='role-commit-packages' sender=':1.5400'
Install: linux-headers-4.18.0-11:amd64 (4.18.0-11.12, automatic), linux-image-4.
18.0-11-generic:amd64 (4.18.0-11.12, automatic), linux-modules-extra-4.18.0-11-g
eneric:amd64 (4.18.0-11.12, automatic), linux-modules-4.18.0-11-generic:amd64 (4
.18.0-11.12, automatic), linux-headers-4.18.0-11-generic:amd64 (4.18.0-11.12, au
tomatic)
Upgrade: evince:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), 
linux-headers-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), linux-libc-dev:amd64 
(4.18.0-10.11, 4.18.0-11.12), linux-libc-dev:i386 (4.18.0-10.11, 4.18.0-11.12), 
libevdocument3-4:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), 
linux-image-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), 
linux-signed-image-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), libpq5:amd64 
(10.5-1, 10.6-0ubuntu0.18.10.1), evince-common:amd64 (3.30.1-1ubuntu1, 
3.30.1-1ubuntu1.2), libevview3-3:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), 
linux-tools-common:amd64 (4.18.0-10.11, 4.18.0-11.12), 
postgresql-client-10:amd64 (10.5-1, 10.6-0ubuntu0.18.10.1), linux-generic:amd64 
(4.18.0.10.11, 4.18.0.11.12)
End-Date: 2018-11-14  17:24:10

Start-Date: 2018-11-15  08:39:50
Commandline: apt autoremove --purge
Requested-By: vorlon (1000)
Purge: linux-modules-extra-4.15.0-36-generic:amd64 (4.15.0-36.39), 
linux-modules-4.15.0-36-generic:amd64 (4.15.0-36.39), 
linux-image-4.15.0-36-generic:amd64 (4.15.0-36.39)
End-Date: 2018-11-15  08:40:08

So yes, it's possible that this was only a candidate for autoremoval
/after/ the previous run of update-manager had finished.

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

Title:
  kernel from bionic did not get autoremoved by either unattended-
  upgrades or update-manager

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I happened to run apt manually on my system this morning to remove a
  package, and I was informed:

  The following packages were automatically installed and are no longer 
required:
linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic
linux-modules-extra-4.15.0-36-generic

  This was surprising, since I have run update-manager yesterday (with
  no intervening reboot), and unattended-upgrades is enabled, and both
  of those packages should have already removed this stale kernel before
  now.

  After apt autoremove, my current installed packages are:

  $ dpkg -l linux-image'*' | grep ^ii
  ii  linux-image-4.18.0-10-generic  4.18.0-10.11 amd64Signed 
kernel image generic
  ii  linux-image-4.18.0-11-generic  4.18.0-11.12 amd64Signed 
kernel image generic
  ii  linux-image-generic4.18.0.11.12 amd64Generic 
Linux kernel image
  $

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

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2018-11-15 Thread Nick Kirkendall

Did this upgrade fail to happen because of the age of my desktop?  It's
a Core 2

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial.

  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]
   
   * original bug report

  
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1614942] Re: "GLib-CRITICAL" messages keep appearing in log file

2018-11-15 Thread Derek Poon

Unfortunately, this bug is unlikely to be fixed upstream:

"ConsoleKit is currently not actively maintained. The focus has shifted
to the built-in seat/user/session management of Software/systemd called
systemd-logind!"

https://www.freedesktop.org/wiki/Software/ConsoleKit/

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

Title:
  "GLib-CRITICAL" messages keep appearing in log file

Status in consolekit package in Ubuntu:
  Triaged

Bug description:
  At regular intervals, errors appear in the log files from consolekit:

  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: consolekit 0.4.6-5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 13:09:22 2016
  InstallationDate: Installed on 2012-03-26 (1606 days ago)
  InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: consolekit
  UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago)

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

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

[Touch-packages] [Bug 1785720] Re: Built-In Analog Audio Low & Distorted

2018-11-15 Thread Christian Saam

Same problem on

Manufacturer:  Alienware
Product Name:  Alienware Area-51 R2
Product Version:   
Firmware Version:  A03
Board Vendor:  Alienware
Board Name:0XJKKD

alsa-info.sh ouptut at 
http://www.alsa-project.org/db/?f=06ec7670b6375759d4367c8f8292b111b0cf2bad

Tried various fixes stated above as well as hdajackretask.

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

Title:
  Built-In Analog Audio Low & Distorted

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been having trouble with my sound since I installed Ubuntu
  18.04.1 LTS.  The sound from my graphics card via the HDMI monitor is
  fine, but the internal Intel HDA audio is very low, distorted and
  crackling, both for headphones and speakers (green front / green
  back).  I've spent many hours so far and tried a number of suggestions
  such as:

  Looking in Alsa Mixer for sound levels
  Adding "options snd-hda-intel position_fix=1" to the end of my 
/etc/modprobe.d/alsa-base.conf
  Issuing something like pulseaudio -k && rm -r ~/.config/pulse
  I've also followed the instructions here:
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
  But that didn't seem to help either

  The devices are all listed, and via pavucontrol I can see the audio
  bars moving and the sound levels seem fine

  In Windows, my sound device driver is SoundBlaster Recon3Di, if that
  helps at all?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brett  1769 F pulseaudio
   /dev/snd/pcmC0D0c:   brett  1769 F...m pulseaudio
   /dev/snd/pcmC0D0p:   brett  1769 F...m pulseaudio
   /dev/snd/controlC0:  brett  1769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  6 18:36:34 2018
  InstallationDate: Installed on 2018-06-01 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: High background noise, or volume is too low
  Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A13
  dmi.board.name: 0FRTKJ
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA13:bd02/09/2018:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0FRTKJ:rvrA00:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-06T18:13:00.717349

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

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

[Touch-packages] [Bug 1785720] Re: Built-In Analog Audio Low & Distorted

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

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

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

Title:
  Built-In Analog Audio Low & Distorted

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been having trouble with my sound since I installed Ubuntu
  18.04.1 LTS.  The sound from my graphics card via the HDMI monitor is
  fine, but the internal Intel HDA audio is very low, distorted and
  crackling, both for headphones and speakers (green front / green
  back).  I've spent many hours so far and tried a number of suggestions
  such as:

  Looking in Alsa Mixer for sound levels
  Adding "options snd-hda-intel position_fix=1" to the end of my 
/etc/modprobe.d/alsa-base.conf
  Issuing something like pulseaudio -k && rm -r ~/.config/pulse
  I've also followed the instructions here:
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
  But that didn't seem to help either

  The devices are all listed, and via pavucontrol I can see the audio
  bars moving and the sound levels seem fine

  In Windows, my sound device driver is SoundBlaster Recon3Di, if that
  helps at all?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brett  1769 F pulseaudio
   /dev/snd/pcmC0D0c:   brett  1769 F...m pulseaudio
   /dev/snd/pcmC0D0p:   brett  1769 F...m pulseaudio
   /dev/snd/controlC0:  brett  1769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  6 18:36:34 2018
  InstallationDate: Installed on 2018-06-01 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: High background noise, or volume is too low
  Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A13
  dmi.board.name: 0FRTKJ
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA13:bd02/09/2018:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0FRTKJ:rvrA00:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-06T18:13:00.717349

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

-- 
Mailing list: https://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 1803407] Re: Totem freeze while reading a video under wayland

2018-11-15 Thread J-Paul BERARD

Oups !

I tried to go to https://wiki.ubuntu.com/Bugs/Upstream/GNOME but when I 
use 'File a bug', I find only a few apps already registrated. It looks 
not so easy.

I found that I should go to 
http://bugzilla.gnome.org/enter_bug.cgi?product=totem but I must be 
registered... I will try again.

Bonne soirée

-- 
Jean-Paul

Le 14/11/2018 à 21:53, Sebastien Bacher a écrit :
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> ** Summary changed:
>
> - Totem freeze while reading a video
> + Totem freeze while reading a video under wayland
>
> ** Changed in: gstreamer1.0 (Ubuntu)
> Importance: Undecided => Low
>

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

Title:
  Totem freeze while reading a video under wayland

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

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

-- 
Mailing list: https://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 1803407] Re: Totem freeze while reading a video under wayland

2018-11-15 Thread J-Paul BERARD

Hi, bonjour,

Sorry but I don't know what are stdout/stderr...

Journal log : I used Ubuntu-bug command, so several files were added. 
But, if you tell me which log file you need, I may send it (it's easy to 
get the bug again).

A+

-- 
Jean-Paul

Le 14/11/2018 à 21:53, Sebastien Bacher a écrit :
> Do you have any error on stdout/stderr? Could you add your journal log
> when getting the issue?
>

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

Title:
  Totem freeze while reading a video under wayland

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure

2018-11-15 Thread Julian Andres Klode

It actually did not fix the issue.

** Changed in: apt (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Cosmic:
  Triaged

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

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

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

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

2018-11-15 Thread AdrianChallinor

To confirm: The bug being experienced is that the main screen goes black
for three seconds, then is replaced by the greeter. The current session
is killed, with no attempt at a clean shutdown.

The bug results in an Xorg Crash log, see above.

I have searched for solutions, but most seem to revolve around removing
the nouveau drivers and installing the NVidia driver. However, there are
other reports that this does not support dual screens unless xinerama is
used.

Happy to try the nvidea driver provided 
a) Someone lets me know definitively how to get back! or 
b) Someone lets me know that dual screen will work. 

You may assume that I am technically competent and willing to try most
things that do not destroy my box!

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug is happening approximately every 24 hours. Any changes to
  open files are lost (DATA LOSS BEING EXPERIENCED).

  System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to
  date with all publish updates.

  System has two graphics card: 
  1) NVidia GK208B [GeForce GT 710]
  2) NVidia GT218 [GeForce 210]

  I am reluctant to switch to nvida drivers as google searches indicate
  that they do not support dual head systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 15 16:18:02 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b]
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
  InstallationDate: Installed on 2018-11-07 (7 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=9d341c90-212b-47c2-b0f0-a7e607ee860b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-11-11T15:48:31.589269
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

This bug was fixed in the package apt - 1.8.0~alpha2ubuntu1

---
apt (1.8.0~alpha2ubuntu1) disco; urgency=medium

  * Adjust libapt-pkg Breaks aptitude to << 0.8.9

 -- Julian Andres Klode   Wed, 14 Nov 2018 12:07:59
+0100

** Changed in: apt (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure

This bug was fixed in the package apt - 1.8.0~alpha2ubuntu1

---
apt (1.8.0~alpha2ubuntu1) disco; urgency=medium

  * Adjust libapt-pkg Breaks aptitude to << 0.8.9

 -- Julian Andres Klode   Wed, 14 Nov 2018 12:07:59
+0100

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Cosmic:
  Triaged

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

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

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

[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager

Could you please attach the relavant part of dpkg history log a and dpkg
terminal log?

It is possible, that the last run of u-u/u-m installed kernel packages
triggering /etc/kernel/postinst.d/apt-auto-removal which resulted
kernels to be removed in the _next_ apt/u-u/u-m run.

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

Title:
  kernel from bionic did not get autoremoved by either unattended-
  upgrades or update-manager

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I happened to run apt manually on my system this morning to remove a
  package, and I was informed:

  The following packages were automatically installed and are no longer 
required:
linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic
linux-modules-extra-4.15.0-36-generic

  This was surprising, since I have run update-manager yesterday (with
  no intervening reboot), and unattended-upgrades is enabled, and both
  of those packages should have already removed this stale kernel before
  now.

  After apt autoremove, my current installed packages are:

  $ dpkg -l linux-image'*' | grep ^ii
  ii  linux-image-4.18.0-10-generic  4.18.0-10.11 amd64Signed 
kernel image generic
  ii  linux-image-4.18.0-11-generic  4.18.0-11.12 amd64Signed 
kernel image generic
  ii  linux-image-generic4.18.0.11.12 amd64Generic 
Linux kernel image
  $

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

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

[Touch-packages] [Bug 1803587] [NEW] kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager

2018-11-15 Thread Steve Langasek

Public bug reported:

I happened to run apt manually on my system this morning to remove a
package, and I was informed:

The following packages were automatically installed and are no longer required:
  linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic
  linux-modules-extra-4.15.0-36-generic

This was surprising, since I have run update-manager yesterday (with no
intervening reboot), and unattended-upgrades is enabled, and both of
those packages should have already removed this stale kernel before now.

After apt autoremove, my current installed packages are:

$ dpkg -l linux-image'*' | grep ^ii
ii  linux-image-4.18.0-10-generic  4.18.0-10.11 amd64Signed 
kernel image generic
ii  linux-image-4.18.0-11-generic  4.18.0-11.12 amd64Signed 
kernel image generic
ii  linux-image-generic4.18.0.11.12 amd64Generic 
Linux kernel image
$

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  kernel from bionic did not get autoremoved by either unattended-
  upgrades or update-manager

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I happened to run apt manually on my system this morning to remove a
  package, and I was informed:

  The following packages were automatically installed and are no longer 
required:
linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic
linux-modules-extra-4.15.0-36-generic

  This was surprising, since I have run update-manager yesterday (with
  no intervening reboot), and unattended-upgrades is enabled, and both
  of those packages should have already removed this stale kernel before
  now.

  After apt autoremove, my current installed packages are:

  $ dpkg -l linux-image'*' | grep ^ii
  ii  linux-image-4.18.0-10-generic  4.18.0-10.11 amd64Signed 
kernel image generic
  ii  linux-image-4.18.0-11-generic  4.18.0-11.12 amd64Signed 
kernel image generic
  ii  linux-image-generic4.18.0.11.12 amd64Generic 
Linux kernel image
  $

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

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

[Touch-packages] [Bug 1797224] Re: Stay on 2.0 for cosmic, update next cycle

2018-11-15 Thread Jeremy Bicha

https://launchpad.net/ubuntu/+source/tracker/2.1.6-1

** Changed in: tracker (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Fix Released

Bug description:
  The new version requires the MIR situation to be sorted out

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

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

[Touch-packages] [Bug 1037738] Re: race condition in if-up.d script

This bug was fixed in the package openssh - 1:7.9p1-1

---
openssh (1:7.9p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/txt/release-7.9):
- ssh(1), sshd(8): allow most port numbers to be specified using service
  names from getservbyname(3) (typically /etc/services; closes:
  #177406).
- ssh(1): allow the IdentityAgent configuration directive to accept
  environment variable names.  This supports the use of multiple agent
  sockets without needing to use fixed paths.
- sshd(8): support signalling sessions via the SSH protocol.  A limited
  subset of signals is supported and only for login or command sessions
  (i.e. not subsystems) that were not subject to a forced command via
  authorized_keys or sshd_config.
- ssh(1): support "ssh -Q sig" to list supported signature options.
  Also "ssh -Q help" to show the full set of supported queries.
- ssh(1), sshd(8): add a CASignatureAlgorithms option for the client and
  server configs to allow control over which signature formats are
  allowed for CAs to sign certificates.  For example, this allows
  banning CAs that sign certificates using the RSA-SHA1 signature
  algorithm.
- sshd(8), ssh-keygen(1): allow key revocation lists (KRLs) to revoke
  keys specified by SHA256 hash.
- ssh-keygen(1): allow creation of key revocation lists directly from
  base64-encoded SHA256 fingerprints.  This supports revoking keys using
  only the information contained in sshd(8) authentication log messages.
- ssh(1), ssh-keygen(1): avoid spurious "invalid format" errors when
  attempting to load PEM private keys while using an incorrect
  passphrase.
- sshd(8): when a channel closed message is received from a client,
  close the stderr file descriptor at the same time stdout is closed.
  This avoids stuck processes if they were waiting for stderr to close
  and were insensitive to stdin/out closing (closes: #844494).
- ssh(1): allow ForwardX11Timeout=0 to disable the untrusted X11
  forwarding timeout and support X11 forwarding indefinitely.
  Previously the behaviour of ForwardX11Timeout=0 was undefined.
- sshd(8): when compiled with GSSAPI support, cache supported method
  OIDs regardless of whether GSSAPI authentication is enabled in the
  main section of sshd_config.  This avoids sandbox violations if GSSAPI
  authentication was later enabled in a Match block.
- sshd(8): do not fail closed when configured with a text key revocation
  list that contains a too-short key.
- ssh(1): treat connections with ProxyJump specified the same as ones
  with a ProxyCommand set with regards to hostname canonicalisation
  (i.e. don't try to canonicalise the hostname unless
  CanonicalizeHostname is set to 'always').
- ssh(1): fix regression in OpenSSH 7.8 that could prevent public-key
  authentication using certificates hosted in a ssh-agent(1) or against
  sshd(8) from OpenSSH <7.8 (LP: #1790963).
- All: support building against the openssl-1.1 API (releases 1.1.0g and
  later).  The openssl-1.0 API will remain supported at least until
  OpenSSL terminates security patch support for that API version
  (closes: #828475).
- sshd(8): allow the futex(2) syscall in the Linux seccomp sandbox;
  apparently required by some glibc/OpenSSL combinations.
  * Remove dh_builddeb override to use xz compression; this has been the
default since dpkg 1.17.0.
  * Simplify debian/rules using /usr/share/dpkg/default.mk.
  * Remove /etc/network/if-up.d/openssh-server, as it causes more problems
than it solves (thanks, Christian Ehrhardt, Andreas Hasenack, and David
Britton; closes: #789532, LP: #1037738, #1674330, #1718227).  Add an
"if-up hook removed" section to README.Debian documenting the corner
case that may need configuration adjustments.

 -- Colin Watson   Sun, 21 Oct 2018 10:39:24 +0100

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

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

Title:
  race condition in if-up.d script

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  ifup -a with lots of new interfaces exposes a race condition in the
  init script:

  lamont
  ---
  ssh start/running, process 9328
  Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
  cat: /var/run/sshd.pid: No such file or directory
  ERROR: List of process IDs must follow -p.

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

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

[Touch-packages] [Bug 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server

This bug was fixed in the package openssh - 1:7.9p1-1

---
openssh (1:7.9p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/txt/release-7.9):
- ssh(1), sshd(8): allow most port numbers to be specified using service
  names from getservbyname(3) (typically /etc/services; closes:
  #177406).
- ssh(1): allow the IdentityAgent configuration directive to accept
  environment variable names.  This supports the use of multiple agent
  sockets without needing to use fixed paths.
- sshd(8): support signalling sessions via the SSH protocol.  A limited
  subset of signals is supported and only for login or command sessions
  (i.e. not subsystems) that were not subject to a forced command via
  authorized_keys or sshd_config.
- ssh(1): support "ssh -Q sig" to list supported signature options.
  Also "ssh -Q help" to show the full set of supported queries.
- ssh(1), sshd(8): add a CASignatureAlgorithms option for the client and
  server configs to allow control over which signature formats are
  allowed for CAs to sign certificates.  For example, this allows
  banning CAs that sign certificates using the RSA-SHA1 signature
  algorithm.
- sshd(8), ssh-keygen(1): allow key revocation lists (KRLs) to revoke
  keys specified by SHA256 hash.
- ssh-keygen(1): allow creation of key revocation lists directly from
  base64-encoded SHA256 fingerprints.  This supports revoking keys using
  only the information contained in sshd(8) authentication log messages.
- ssh(1), ssh-keygen(1): avoid spurious "invalid format" errors when
  attempting to load PEM private keys while using an incorrect
  passphrase.
- sshd(8): when a channel closed message is received from a client,
  close the stderr file descriptor at the same time stdout is closed.
  This avoids stuck processes if they were waiting for stderr to close
  and were insensitive to stdin/out closing (closes: #844494).
- ssh(1): allow ForwardX11Timeout=0 to disable the untrusted X11
  forwarding timeout and support X11 forwarding indefinitely.
  Previously the behaviour of ForwardX11Timeout=0 was undefined.
- sshd(8): when compiled with GSSAPI support, cache supported method
  OIDs regardless of whether GSSAPI authentication is enabled in the
  main section of sshd_config.  This avoids sandbox violations if GSSAPI
  authentication was later enabled in a Match block.
- sshd(8): do not fail closed when configured with a text key revocation
  list that contains a too-short key.
- ssh(1): treat connections with ProxyJump specified the same as ones
  with a ProxyCommand set with regards to hostname canonicalisation
  (i.e. don't try to canonicalise the hostname unless
  CanonicalizeHostname is set to 'always').
- ssh(1): fix regression in OpenSSH 7.8 that could prevent public-key
  authentication using certificates hosted in a ssh-agent(1) or against
  sshd(8) from OpenSSH <7.8 (LP: #1790963).
- All: support building against the openssl-1.1 API (releases 1.1.0g and
  later).  The openssl-1.0 API will remain supported at least until
  OpenSSL terminates security patch support for that API version
  (closes: #828475).
- sshd(8): allow the futex(2) syscall in the Linux seccomp sandbox;
  apparently required by some glibc/OpenSSL combinations.
  * Remove dh_builddeb override to use xz compression; this has been the
default since dpkg 1.17.0.
  * Simplify debian/rules using /usr/share/dpkg/default.mk.
  * Remove /etc/network/if-up.d/openssh-server, as it causes more problems
than it solves (thanks, Christian Ehrhardt, Andreas Hasenack, and David
Britton; closes: #789532, LP: #1037738, #1674330, #1718227).  Add an
"if-up hook removed" section to README.Debian documenting the corner
case that may need configuration adjustments.

 -- Colin Watson   Sun, 21 Oct 2018 10:39:24 +0100

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

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

This bug was fixed in the package openssh - 1:7.9p1-1

---
openssh (1:7.9p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/txt/release-7.9):
- ssh(1), sshd(8): allow most port numbers to be specified using service
  names from getservbyname(3) (typically /etc/services; closes:
  #177406).
- ssh(1): allow the IdentityAgent configuration directive to accept
  environment variable names.  This supports the use of multiple agent
  sockets without needing to use fixed paths.
- sshd(8): support signalling sessions via the SSH protocol.  A limited
  subset of signals is supported and only for login or command sessions
  (i.e. not subsystems) that were not subject to a forced command via
  authorized_keys or sshd_config.
- ssh(1): support "ssh -Q sig" to list supported signature options.
  Also "ssh -Q help" to show the full set of supported queries.
- ssh(1), sshd(8): add a CASignatureAlgorithms option for the client and
  server configs to allow control over which signature formats are
  allowed for CAs to sign certificates.  For example, this allows
  banning CAs that sign certificates using the RSA-SHA1 signature
  algorithm.
- sshd(8), ssh-keygen(1): allow key revocation lists (KRLs) to revoke
  keys specified by SHA256 hash.
- ssh-keygen(1): allow creation of key revocation lists directly from
  base64-encoded SHA256 fingerprints.  This supports revoking keys using
  only the information contained in sshd(8) authentication log messages.
- ssh(1), ssh-keygen(1): avoid spurious "invalid format" errors when
  attempting to load PEM private keys while using an incorrect
  passphrase.
- sshd(8): when a channel closed message is received from a client,
  close the stderr file descriptor at the same time stdout is closed.
  This avoids stuck processes if they were waiting for stderr to close
  and were insensitive to stdin/out closing (closes: #844494).
- ssh(1): allow ForwardX11Timeout=0 to disable the untrusted X11
  forwarding timeout and support X11 forwarding indefinitely.
  Previously the behaviour of ForwardX11Timeout=0 was undefined.
- sshd(8): when compiled with GSSAPI support, cache supported method
  OIDs regardless of whether GSSAPI authentication is enabled in the
  main section of sshd_config.  This avoids sandbox violations if GSSAPI
  authentication was later enabled in a Match block.
- sshd(8): do not fail closed when configured with a text key revocation
  list that contains a too-short key.
- ssh(1): treat connections with ProxyJump specified the same as ones
  with a ProxyCommand set with regards to hostname canonicalisation
  (i.e. don't try to canonicalise the hostname unless
  CanonicalizeHostname is set to 'always').
- ssh(1): fix regression in OpenSSH 7.8 that could prevent public-key
  authentication using certificates hosted in a ssh-agent(1) or against
  sshd(8) from OpenSSH <7.8 (LP: #1790963).
- All: support building against the openssl-1.1 API (releases 1.1.0g and
  later).  The openssl-1.0 API will remain supported at least until
  OpenSSL terminates security patch support for that API version
  (closes: #828475).
- sshd(8): allow the futex(2) syscall in the Linux seccomp sandbox;
  apparently required by some glibc/OpenSSL combinations.
  * Remove dh_builddeb override to use xz compression; this has been the
default since dpkg 1.17.0.
  * Simplify debian/rules using /usr/share/dpkg/default.mk.
  * Remove /etc/network/if-up.d/openssh-server, as it causes more problems
than it solves (thanks, Christian Ehrhardt, Andreas Hasenack, and David
Britton; closes: #789532, LP: #1037738, #1674330, #1718227).  Add an
"if-up hook removed" section to README.Debian documenting the corner
case that may need configuration adjustments.

 -- Colin Watson   Sun, 21 Oct 2018 10:39:24 +0100

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

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in

[Touch-packages] [Bug 1790963] Re: Unable to connect with openssh 7.8 client and certificates

This bug was fixed in the package openssh - 1:7.9p1-1

---
openssh (1:7.9p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/txt/release-7.9):
- ssh(1), sshd(8): allow most port numbers to be specified using service
  names from getservbyname(3) (typically /etc/services; closes:
  #177406).
- ssh(1): allow the IdentityAgent configuration directive to accept
  environment variable names.  This supports the use of multiple agent
  sockets without needing to use fixed paths.
- sshd(8): support signalling sessions via the SSH protocol.  A limited
  subset of signals is supported and only for login or command sessions
  (i.e. not subsystems) that were not subject to a forced command via
  authorized_keys or sshd_config.
- ssh(1): support "ssh -Q sig" to list supported signature options.
  Also "ssh -Q help" to show the full set of supported queries.
- ssh(1), sshd(8): add a CASignatureAlgorithms option for the client and
  server configs to allow control over which signature formats are
  allowed for CAs to sign certificates.  For example, this allows
  banning CAs that sign certificates using the RSA-SHA1 signature
  algorithm.
- sshd(8), ssh-keygen(1): allow key revocation lists (KRLs) to revoke
  keys specified by SHA256 hash.
- ssh-keygen(1): allow creation of key revocation lists directly from
  base64-encoded SHA256 fingerprints.  This supports revoking keys using
  only the information contained in sshd(8) authentication log messages.
- ssh(1), ssh-keygen(1): avoid spurious "invalid format" errors when
  attempting to load PEM private keys while using an incorrect
  passphrase.
- sshd(8): when a channel closed message is received from a client,
  close the stderr file descriptor at the same time stdout is closed.
  This avoids stuck processes if they were waiting for stderr to close
  and were insensitive to stdin/out closing (closes: #844494).
- ssh(1): allow ForwardX11Timeout=0 to disable the untrusted X11
  forwarding timeout and support X11 forwarding indefinitely.
  Previously the behaviour of ForwardX11Timeout=0 was undefined.
- sshd(8): when compiled with GSSAPI support, cache supported method
  OIDs regardless of whether GSSAPI authentication is enabled in the
  main section of sshd_config.  This avoids sandbox violations if GSSAPI
  authentication was later enabled in a Match block.
- sshd(8): do not fail closed when configured with a text key revocation
  list that contains a too-short key.
- ssh(1): treat connections with ProxyJump specified the same as ones
  with a ProxyCommand set with regards to hostname canonicalisation
  (i.e. don't try to canonicalise the hostname unless
  CanonicalizeHostname is set to 'always').
- ssh(1): fix regression in OpenSSH 7.8 that could prevent public-key
  authentication using certificates hosted in a ssh-agent(1) or against
  sshd(8) from OpenSSH <7.8 (LP: #1790963).
- All: support building against the openssl-1.1 API (releases 1.1.0g and
  later).  The openssl-1.0 API will remain supported at least until
  OpenSSL terminates security patch support for that API version
  (closes: #828475).
- sshd(8): allow the futex(2) syscall in the Linux seccomp sandbox;
  apparently required by some glibc/OpenSSL combinations.
  * Remove dh_builddeb override to use xz compression; this has been the
default since dpkg 1.17.0.
  * Simplify debian/rules using /usr/share/dpkg/default.mk.
  * Remove /etc/network/if-up.d/openssh-server, as it causes more problems
than it solves (thanks, Christian Ehrhardt, Andreas Hasenack, and David
Britton; closes: #789532, LP: #1037738, #1674330, #1718227).  Add an
"if-up hook removed" section to README.Debian documenting the corner
case that may need configuration adjustments.

 -- Colin Watson   Sun, 21 Oct 2018 10:39:24 +0100

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

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

Title:
  Unable to connect with openssh 7.8 client and certificates

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh package in Fedora:
  Confirmed

Bug description:
  Users are unable to connect to Ubuntu when using openssh client 7.8
  and certificates. We have seen this with both xenial and bionic, but
  this affects connecting to ANY host running openssh server <7.8.

  It appears to be specific to using certificate authentication.

  The only known recourse at this time is either downgrade clients to
  7.7 or a previous version of openssh, or create new keys/certificates
  with a different alg that is acceptable for both the older server and
  newer client.

  The error message

[Touch-packages] [Bug 1803583] [NEW] Xorg crash

2018-11-15 Thread AdrianChallinor

Public bug reported:

This bug is happening approximately every 24 hours. Any changes to open
files are lost (DATA LOSS BEING EXPERIENCED).

System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to
date with all publish updates.

System has two graphics card: 
1) NVidia GK208B [GeForce GT 710]
2) NVidia GT218 [GeForce 210]

I am reluctant to switch to nvida drivers as google searches indicate
that they do not support dual head systems.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Nov 15 16:18:02 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
 virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b]
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
InstallationDate: Installed on 2018-11-07 (7 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=9d341c90-212b-47c2-b0f0-a7e607ee860b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-11-11T15:48:31.589269
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic crash ubuntu

** Attachment added: "Output of sudo lshw -c video"
   https://bugs.launchpad.net/bugs/1803583/+attachment/5213157/+files/crt.log

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug is happening approximately every 24 hours. Any changes to
  open files are lost (DATA LOSS BEING EXPERIENCED).

  System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to
  date with all publish updates.

  System has two graphics card: 
  1) NVidia GK208B [GeForce GT 710]
  2) NVidia GT218 [GeForce 210]

  I am reluctant to switch to nvida drivers as google searches indicate
  that they do not support dual head systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 15

[Touch-packages] [Bug 1734285] Re: unattended-upgrades.service ignores (changes in) /etc/apt/preferences.d/ files

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  unattended-upgrades.service ignores (changes in)
  /etc/apt/preferences.d/ files

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  unattended-upgrades.service ignores (changes in)
  /etc/apt/preferences.d/ files that are done after the service has
  started.

  For example we 'pin' firefox on to a specific version and if a
  configuration file is placed after the service is started, the pinning
  is ignored. In our sitation that results in a newer firefox then we
  want at this moment.

  We run Ubuntu on 2000+ workstations and our users often start a
  workstation and let it run for days/weeks before rebooting and thus
  restarting the service unattended-upgrades again.

  I did not test if changes in other apt files are ignored also.

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

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

[Touch-packages] [Bug 1803579] Re: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1

2018-11-15 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this bug report isn't very useful in its current state
and a crash report would be much more useful.  Could you try recreating
this issue by enabling apport to catch the crash report 'sudo service
apport start force_start=1' and then trying to install the same package
again?  This process will create a new bug report so I am marking this
one as Invalid.  Thanks again for helping out!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: package-install-segfault

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

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

Title:
  package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade:
  installed x11-common package post-installation script subprocess
  returned error exit status 1

Status in xorg package in Ubuntu:
  Invalid

Bug description:
   sudo dpkg --configure -a

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  Failed to reload daemon: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: x11-common 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Nov 15 12:16:54 2018
  Dependencies: lsb-base 9.20170808ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: installed x11-common package post-installation script 
subprocess returned error exit status 1
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8c500269-234e-4a72-82b7-7ad3b0172dc9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: xorg
  Title: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: 
installed x11-common package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1616
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1616:bd10/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1803579] Re: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade:
  installed x11-common package post-installation script subprocess
  returned error exit status 1

Status in xorg package in Ubuntu:
  New

Bug description:
   sudo dpkg --configure -a

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  Failed to reload daemon: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: x11-common 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Nov 15 12:16:54 2018
  Dependencies: lsb-base 9.20170808ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: installed x11-common package post-installation script 
subprocess returned error exit status 1
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8c500269-234e-4a72-82b7-7ad3b0172dc9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: xorg
  Title: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: 
installed x11-common package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1616
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1616:bd10/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1803137] Re: Unattended-upgrades may keep running after unmounting local filesystems in InstallOnShutdown mode

** Description changed:

  [Impact]
  
   * Unattended-upgrades may keep running during shutdown even beyond 
unmounting local filesystems potentially leaving a broken installation behind.
   * The fix reverts the original fix of LP: #1778219 and applies a different 
one starting unattended-upgrades-shutdown _before_ the shutdown transaction 
starts/
  
  [Test Case]
  
   * Run unattended-upgrades in InstallOnShutdown mode and observe it
  being finished installing a few packages _before_ the shutdown
  transaction starts:
  
  $ lxc launch ubuntu:18.10 cc-uu-onshutdown
  Creating cc-uu-onshutdown
  Starting cc-uu-onshutdown
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# apt update -qq
  33 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' 
> /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@cc-uu-onshutdown:~# dbus-send --system --print-reply 
--dest=org.freedesktop.login1 /org/freedesktop/login1 
"org.freedesktop.login1.Manager.Reboot" boolean:false
  method return time=1542112922.046290 sender=:1.4 -> destination=:1.13 
serial=27 reply_serial=2
  
  Session terminated, terminating shell...$
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# journalctl -l
  ...
  Nov 13 12:50:10 cc-uu-shutdown systemd[1]: Started Unattended Upgrades 
Shutdown.
  Nov 13 12:51:17 cc-uu-shutdown systemd-logind[228]: System is rebooting.
  
  ...
  root@cc-uu-shutdown:~# cat 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  ...
  2018-11-13 12:51:13,835 WARNING - Running unattended-upgrades in shutdown mode
  2018-11-13 12:51:13,852 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:15,482 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,151 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,166 INFO - All upgrades installed
  
  [Regression Potential]
  
   * The change reverts the behavior of unattended-upgrades-shutdown to be
  close to the behavior observed in Ubuntu 18.04, blocking the shutdown
  process reliably until is unattended-upgrades finished, but it starts
  _before_ shutdown triggered by the PrepareForShutdown() signal. Due to
  the shutdown not fully starting yet users may not get visual
  notification of unattended-upgrades running.
  
  In my testing on Bionic when a logged-in user shuts down the system when
  InstallOnShutdown is configured the user is dropped out to the login
  manager and nothing shows that u-u is running behind the screens for
  30s, when the inhibition timer expires and u-u is starting to gracefully
  stop and the usual text appears after the login manager exits and
  plymouth shutdown screen is shown. The fix would be the login manager
- also monitoring PrepareForShutdown() and exiting.
+ also monitoring PrepareForShutdown() and exiting (LP: #1803581).
  
  On Xenial (with Unity) starting shutdown from the graphical session does
  not log the user out nor show any progress on the shutdown until the
  inhibition timer expires which is confusing. Users should be logged out
- on PrepareForShutdown().
+ on PrepareForShutdown() (LP: #1803581).
  
   * The reversion of unattended-upgrades.service was not complete in u-u
  1.7 and needed a further fix in 1.7ubuntu1 (which fix is already
  included in 1.5ubuntu4). This part may be source of potential
  regressions.
  
   * The fix itself rewrites big part of unattended-upgrades-shutdown and
  this rewrite could cause regressions in running unattended-upgrades in
  InstallOnShutdown mode, but also this mode was extensively tested.
  
   * The fix includes increasing logind's InhibitDelayMaxSec to 30s to
  give u-u enough time to gracefully stop in normal mode and install
  packages in InstallOnShutdown mode. The delay is global, thus any other
  program holding the lock can delay shutdown or sleep by 30s instead of
  the original 5s default. This regression is hard to avoid and the 30s
  was chosen to minimize the regression potential while still giving more
  than 5s to u-u to finish actions. Bugs reporting increased delay to
  sleep or shutdown should be monitored to catch other programs
  misbehaving with this new default.
  
  [Other Info]
  
  This is a regression of introduced in LP: #1778219 and can be observed
  in a cosmic lxd container easily:
  
  $ lxc launch ubuntu:18.10 cc-uu-onshutdown
  Creating cc-uu-onshutdown
  Starting cc-uu-onshutdown
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# apt update -qq
  33 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' 
>

[Touch-packages] [Bug 1803579] [NEW] package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1

2018-11-15 Thread Jorge Olivos

Public bug reported:

 sudo dpkg --configure -a

update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults

Failed to reload daemon: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: x11-common 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Thu Nov 15 12:16:54 2018
Dependencies: lsb-base 9.20170808ubuntu1
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: installed x11-common package post-installation script subprocess 
returned error exit status 1
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2018-11-15 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: System manufacturer System Product Name
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8c500269-234e-4a72-82b7-7ad3b0172dc9 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: xorg
Title: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: 
installed x11-common package post-installation script subprocess returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1616
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1616:bd10/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-package bionic ubuntu

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

Title:
  package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade:
  installed x11-common package post-installation script subprocess
  returned error exit status 1

Status in xorg package in Ubuntu:
  New

Bug description:
   sudo dpkg --configure -a

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  Failed to reload daemon: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: x11-common 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Nov 15 12:16:54 2018
  Dependencies: lsb-base 9.20170808ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: installed x11-common package post-installation script 
subprocess returned error exit status 1
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic

[Touch-packages] [Bug 1803568] Re: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

** Tags removed: need-duplicate-check

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new
  pre-installation script returned error exit status 2

Status in bash package in Ubuntu:
  New

Bug description:
  Ran do-release-upgrade from 16.04 LTS Ubuntu terminal on WSL. The
  upgrade still appeared to work because I'm not on 18.04 LTS, but it
  threw this error nonetheless. I attempted to send a report through the
  command as well, but it also generated this link for me to go to so
  that's what I did. :)

  Keep up the Awesome work all you Ubuntu devs ^.^

  UPDATE! Oh my gosh, my Chrome crashed after writing the above while
  trying to attach a screenshot and I don't know if it was Chrome or
  your site, but whoever preserved the state of what I typed previously,
  I LOVE YOU!!! :P

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Microsoft 4.4.0-17134.345-Microsoft 4.4.35
  Uname: Linux 4.4.0-17134-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Nov 15 06:42:59 2018
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
   dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 2
  DuplicateSignature:
   package:bash:4.3-14ubuntu1.2
   Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
   dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-11-15 (0 days ago)

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

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

[Touch-packages] [Bug 1803568] [NEW] package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

2018-11-15 Thread Matthew

Public bug reported:

Ran do-release-upgrade from 16.04 LTS Ubuntu terminal on WSL. The
upgrade still appeared to work because I'm not on 18.04 LTS, but it
threw this error nonetheless. I attempted to send a report through the
command as well, but it also generated this link for me to go to so
that's what I did. :)

Keep up the Awesome work all you Ubuntu devs ^.^

UPDATE! Oh my gosh, my Chrome crashed after writing the above while
trying to attach a screenshot and I don't know if it was Chrome or your
site, but whoever preserved the state of what I typed previously, I LOVE
YOU!!! :P

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bash 4.3-14ubuntu1.2
ProcVersionSignature: Microsoft 4.4.0-17134.345-Microsoft 4.4.35
Uname: Linux 4.4.0-17134-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Nov 15 06:42:59 2018
Dmesg:
 
DpkgTerminalLog:
 Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
 dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
  subprocess new pre-installation script returned error exit status 2
DuplicateSignature:
 package:bash:4.3-14ubuntu1.2
 Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
 dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
  subprocess new pre-installation script returned error exit status 2
ErrorMessage: subprocess new pre-installation script returned error exit status 
2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: bash
Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-11-15 (0 days ago)

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


** Tags: amd64 apport-package bionic uec-images

** Attachment added: "where do-release-upgrade failed"
   
https://bugs.launchpad.net/bugs/1803568/+attachment/5213125/+files/where%20do-release-upgrade%20failed.png

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new
  pre-installation script returned error exit status 2

Status in bash package in Ubuntu:
  New

Bug description:
  Ran do-release-upgrade from 16.04 LTS Ubuntu terminal on WSL. The
  upgrade still appeared to work because I'm not on 18.04 LTS, but it
  threw this error nonetheless. I attempted to send a report through the
  command as well, but it also generated this link for me to go to so
  that's what I did. :)

  Keep up the Awesome work all you Ubuntu devs ^.^

  UPDATE! Oh my gosh, my Chrome crashed after writing the above while
  trying to attach a screenshot and I don't know if it was Chrome or
  your site, but whoever preserved the state of what I typed previously,
  I LOVE YOU!!! :P

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Microsoft 4.4.0-17134.345-Microsoft 4.4.35
  Uname: Linux 4.4.0-17134-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Nov 15 06:42:59 2018
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
   dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 2
  DuplicateSignature:
   package:bash:4.3-14ubuntu1.2
   Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
   dpkg (subprocess): unable to execute new pre-installation script 
(/var/lib/dpkg/tmp.ci/preinst): No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4.18-2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-11-15 (0 days ago)

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

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2018-11-15 Thread Dimitri John Ledkov

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

** Also affects: systemd (Ubuntu Disco)
   Importance: High
   Status: New

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

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in Disco:
  New

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
  systemd+   153 1  0

[Touch-packages] [Bug 1803137] Re: Unattended-upgrades may keep running after unmounting local filesystems in InstallOnShutdown mode

** Description changed:

  [Impact]
  
   * Unattended-upgrades may keep running during shutdown even beyond 
unmounting local filesystems potentially leaving a broken installation behind.
-  * The fix reverts the original fix of LP: #1778219 and applies a different 
one startin unattended-upgrades-shutdown _before_ the shutdown transaction 
starts/
+  * The fix reverts the original fix of LP: #1778219 and applies a different 
one starting unattended-upgrades-shutdown _before_ the shutdown transaction 
starts/
  
  [Test Case]
  
   * Run unattended-upgrades in InstallOnShutdown mode and observe it
  being finished installing a few packages _before_ the shutdown
  transaction starts:
  
  $ lxc launch ubuntu:18.10 cc-uu-onshutdown
  Creating cc-uu-onshutdown
  Starting cc-uu-onshutdown
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# apt update -qq
  33 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' 
> /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@cc-uu-onshutdown:~# dbus-send --system --print-reply 
--dest=org.freedesktop.login1 /org/freedesktop/login1 
"org.freedesktop.login1.Manager.Reboot" boolean:false
  method return time=1542112922.046290 sender=:1.4 -> destination=:1.13 
serial=27 reply_serial=2
  
  Session terminated, terminating shell...$
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# journalctl -l
  ...
  Nov 13 12:50:10 cc-uu-shutdown systemd[1]: Started Unattended Upgrades 
Shutdown.
  Nov 13 12:51:17 cc-uu-shutdown systemd-logind[228]: System is rebooting.
  
  ...
  root@cc-uu-shutdown:~# cat 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  ...
  2018-11-13 12:51:13,835 WARNING - Running unattended-upgrades in shutdown mode
  2018-11-13 12:51:13,852 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:15,482 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,151 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,166 INFO - All upgrades installed
  
  [Regression Potential]
  
   * The change reverts the behavior of unattended-upgrades-shutdown to be
  close to the behavior observed in Ubuntu 18.04, blocking the shutdown
  process reliably until is unattended-upgrades finished, but it starts
  _before_ shutdown triggered by the PrepareForShutdown() signal. Due to
  the shutdown not fully starting yet users may not get visual
  notification of unattended-upgrades running.
  
  In my testing on Bionic when a logged-in user shuts down the system when
  InstallOnShutdown is configured the user is dropped out to the login
  manager and nothing shows that u-u is running behind the screens for
  30s, when the inhibition timer expires and u-u is starting to gracefully
  stop and the usual text appears after the login manager exits and
  plymouth shutdown screen is shown. The fix would be the login manager
  also monitoring PrepareForShutdown() and exiting.
  
  On Xenial (with Unity) starting shutdown from the graphical session does
  not log the user out nor show any progress on the shutdown until the
  inhibition timer expires which is confusing. Users should be logged out
  on PrepareForShutdown().
  
   * The reversion of unattended-upgrades.service was not complete in u-u
  1.7 and needed a further fix in 1.7ubuntu1 (which fix is already
  included in 1.5ubuntu4). This part may be source of potential
  regressions.
  
   * The fix itself rewrites big part of unattended-upgrades-shutdown and
  this rewrite could cause regressions in running unattended-upgrades in
  InstallOnShutdown mode, but also this mode was extensively tested.
  
   * The fix includes increasing logind's InhibitDelayMaxSec to 30s to
  give u-u enough time to gracefully stop in normal mode and install
  packages in InstallOnShutdown mode. The delay is global, thus any other
  program holding the lock can delay shutdown or sleep by 30s instead of
  the original 5s default. This regression is hard to avoid and the 30s
  was chosen to minimize the regression potential while still giving more
  than 5s to u-u to finish actions. Bugs reporting increased delay to
  sleep or shutdown should be monitored to catch other programs
  misbehaving with this new default.
  
  [Other Info]
  
  This is a regression of introduced in LP: #1778219 and can be observed
  in a cosmic lxd container easily:
  
  $ lxc launch ubuntu:18.10 cc-uu-onshutdown
  Creating cc-uu-onshutdown
  Starting cc-uu-onshutdown
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# apt update -qq
  33 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@cc-uu-onshutdown:~# echo

[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

2018-11-15 Thread Matthias Klose

** Description changed:

  SRU: update python3.6 to the new minor release 3.6.7
  
  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).
  
  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.
  
  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.
  
  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests
  
  Failing autopkg tests:
   - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
     failed before, flaky autopkg tests history, now passes in disco.
   - snapcraft: amd64 and i386 try to download some rust installation,
     which then fails to build some downloaded code. This doesn't look
     like a reliable test.
   - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
     Fixed in cosmic, filed LP: #1802835 for a fix anyway.
   - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
     doesn't look like a regression in the autopkg test history.
     pinged the lxd maintainers, but no response yet. LP: #1803344
+lxd now passes after giving back several times
   - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
     This does not seem to be a regression, although fixed in disco via
     a new upstream version 6.2.5.
-And now fixed by another SRU ...
+    And now fixed by another SRU ...

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3.6 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

  Failing autopkg tests:
   - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
     failed before, flaky autopkg tests history, now passes in disco.
   - snapcraft: amd64 and i386 try to download some rust installation,
     which then fails to build some downloaded code. This doesn't look
     like a reliable test.
   - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
     Fixed in cosmic, filed LP: #1802835 for a fix anyway.
   - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
     doesn't look like a regression in the autopkg test history.
     pinged the lxd maintainers, but no response yet. LP: #1803344
 lxd now passes after giving back several times
   - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
     This does not seem to be a regression, although fixed in disco via
     a new upstream version 6.2.5.
     And now fixed by another SRU ...

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

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

[Touch-packages] [Bug 1803168] Re: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

Title:
  package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  not sure. It just notifies a failure of installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.8
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Nov 13 06:26:36 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-27 (138 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. OptiPlex 9020
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d6f84918-e5e2-4e2e-abb9-cc9127cf0382 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/14/2015:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1803562] [NEW] Please merge 2:4.20-1 into disco

2018-11-15 Thread Karl Stenerud

Public bug reported:

Please merge 2:4.20-1 into disco

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

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

Title:
  Please merge 2:4.20-1 into disco

Status in nspr package in Ubuntu:
  New

Bug description:
  Please merge 2:4.20-1 into disco

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

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

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

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

Since this issue is marked as invalid for linux i'm setting it as a
duplicate of the u-u bug where SRU-ing the fix is tracked.

** This bug has been marked a duplicate of bug 1778219
   unattended-upgrades hangs on shutdown, leaves system in a broken state

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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

[Touch-packages] [Bug 1803545] [NEW] segfault during installing nvidia-driver-415 using apt

2018-11-15 Thread Alex Spanos

Public bug reported:

segfault during installing nvidia-driver-415 using apt.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.5
Uname: Linux 4.19.2-041902-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 15 12:07:27 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2018-11-05 (9 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  segfault during installing nvidia-driver-415 using apt

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  segfault during installing nvidia-driver-415 using apt.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  Uname: Linux 4.19.2-041902-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Nov 15 12:07:27 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-11-05 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  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/1803545/+subscriptions

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

[Touch-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

2018-11-15 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

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

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

[Touch-packages] [Bug 1803545] Re: segfault during installing nvidia-driver-415 using apt

** Tags removed: need-duplicate-check

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

Title:
  segfault during installing nvidia-driver-415 using apt

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  segfault during installing nvidia-driver-415 using apt.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  Uname: Linux 4.19.2-041902-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Nov 15 12:07:27 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-11-05 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  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/1803545/+subscriptions

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

[Touch-packages] [Bug 1803530] [NEW] [Xenial][udev] postinst script should use "invoke-rc.d stop" instead of "systemctl stop"

2018-11-15 Thread Guillaume Penin

Public bug reported:

In order to respect the local initscript policy layer that may be
present in /usr/sbin/policy-rc.d, the postinst script of the udev
package should use "invoke-rc.d stop" instead of "systemctl stop".

This direct systemctl call can be found in the handle_service_rename()
function :

handle_service_rename() {
  if dpkg --compare-versions "$2" lt "204-1"; then
if [ -d /run/systemd/system ]; then
  systemctl stop udev.service udev-control.socket udev-kernel.socket 
>/dev/null 2>&1 || true
fi
  fi
}

Using "systemctl stop" during unattended-upgrades in shutdown mode hangs
and leaves the dpkg database in a broken state after reboot. Using a
local initscript policy layer that prevents start/stop/restart actions
on this case is a way to prevent those hangs but maintainer scripts have
to use invoke-rc.d instead of direct systemctl calls.

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

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

Title:
  [Xenial][udev] postinst script should use "invoke-rc.d stop" instead
  of "systemctl stop"

Status in systemd package in Ubuntu:
  New

Bug description:
  In order to respect the local initscript policy layer that may be
  present in /usr/sbin/policy-rc.d, the postinst script of the udev
  package should use "invoke-rc.d stop" instead of "systemctl stop".

  This direct systemctl call can be found in the handle_service_rename()
  function :

  handle_service_rename() {
if dpkg --compare-versions "$2" lt "204-1"; then
  if [ -d /run/systemd/system ]; then
systemctl stop udev.service udev-control.socket udev-kernel.socket 
>/dev/null 2>&1 || true
  fi
fi
  }

  Using "systemctl stop" during unattended-upgrades in shutdown mode
  hangs and leaves the dpkg database in a broken state after reboot.
  Using a local initscript policy layer that prevents start/stop/restart
  actions on this case is a way to prevent those hangs but maintainer
  scripts have to use invoke-rc.d instead of direct systemctl calls.

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

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

[Touch-packages] [Bug 1287400] Re: vim.nox crashed with SIGSEGV on ruby file

2018-11-15 Thread Paul White

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

Do you still see a problem related to the one that you reported?

Please let us know if you do otherwise this bug report will expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  vim.nox crashed with SIGSEGV on ruby file

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  vim will crash using this trivial example (note carefully the amount
  of whitespace).  Name it blah.rb.

  def a
hij_klmn(v)#foo
  end

  The file in base64 is
  ZGVmIGEKICBoaWpfa2xtbih2KSAgICAgICAgICAgICAgICAgICAgICAgICNmb28KZW5kCg==

  It will crash when using the default vimrc ( vim -u /etc/vim/vimrc
  blah.rb ), but not when you use no vimrc ( vim -u NONE blah.rb ).

  The crash:
  Vim: Caught deadly signal SEGV

  Vim: Finished.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: vim-nox 2:7.4.000-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Mar  3 15:14:19 2014
  ExecutablePath: /usr/bin/vim.nox
  ExecutableTimestamp: 1376267020
  InstallationDate: Installed on 2013-11-04 (119 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcCmdline: vim blah.rb
  ProcCwd: /home/jake
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: vim.nox crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-11-15 Thread Michael Vogt

** Changed in: snapd
   Status: New => Fix Released

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Fix Released
Status in snapd:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

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

[Touch-packages] [Bug 1051288] Re: LightDM assumes there's only ONE system default layout

2018-11-15 Thread Adam Niedling

I have Hungarian and English keyboard layouts set up.
However at the login screen it's English and Afghan. Have no idea why. It 
changed at some point during 18.04.

$ grep XKBLAYOUT /etc/default/keyboard
XKBLAYOUT="us,af"

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

Title:
  LightDM assumes there's only ONE system default layout

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  In Greece, the default system layout is "us,gr":
  $ grep XKBLAYOUT /etc/default/keyboard 
  XKBLAYOUT="us,gr"

  For new users that don't have .dmrc or accountsservice entries and are 
supposed to get the system defaults, LightDM assumes their keyboard layout is 
"us".
  So they can't switch languages in the greeter and they can't input national 
characters until they login, go to gnome settings and manually set the keyboard 
layout.

  A similar bug was
  https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/919200, but
  that was only solved for the single-layout case.

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

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

[Touch-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

2018-11-15 Thread James Henstridge

A backport of the UUID cache file directory feature from fontconfig
2.13.

** Patch added: "fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff"

https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+attachment/5213086/+files/fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff

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

Title:
Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
New

Bug description:
Fontconfig 2.13.0 changed the cache file naming scheme to be based on
the contents of ".uuid" file in the directory rather than a hash of
the directory name. On a pure debs system this doesn't really matter
since everything is using the same libfontconfig.so.

When snaps are involved, it can lead to some apps not seeing the cache
files produced by a different fontconfig version. In particular,
while libfontconfig 2.13 can reuse 2.12's cache files for read only
directories, the reverse is not true. This will be a problem for apps
built on top of the "core18" base snap when run on later Ubuntu
releases (cosmic, disco, etc).

By providing a backport of the UUID cache file feature to bionic for
use by snap applications, we'd avoid this. Having it in bionic-
updates would be ideal so that snapcraft picks it up automatically.

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

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

[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2018-11-15 Thread Dmitry Shachnev

This needs fixes in both qtbase and qttools. In addition, I will upload
a no-change rebuild of qtdeclarative to demonstrate that the fix works.

Updating the description accordingly.

** Description changed:

  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.
  
  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine, etc.).
- I am now fixing it for qtbase, the largest module, but I may fix it for
- other modules if someone requests it.
+ 
+ To properly fix this bug, we need changes in qtbase and qttools modules.
+ In addition, I will be uploading a no-change rebuild of qtdeclarative
+ module to demonstrate that the fixes work.
+ 
+ If requested, I can also upload no-change rebuilds of some other modules
+ to get their -doc packages properly regenerated.
  
  [Test Case]
+ For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.
  
+ For qtdeclarative5-doc-html:
+ 1. Install qtdeclarative5-doc-html package.
+ 2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.
+ 
  [Regression Potential]
- The proposed fix only adds a new build-dependency. There is absolutely no 
regression potential.
+ The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.
+ 
+ The proposed change in qttools can affect more packages. It can result
+ in qdoc passing more -isystem flags to clang code analyzer. I am not
+ aware of negative consequences of this, but if they happen, these
+ consequences will be limited to potential build failures or wrong
+ documentation contents.
  
  [Other Info]
  Description of the fix:
  
  qdoc is a tool that parses C++ source files and generates documentation
  from them. Recently, qdoc began using clang instead of its own C++
- parser. Clang needs the C++ standard library to work. qdoc build system
- uses a build-time macro (CLANG_RESOURCE_DIR) that hard-codes the path to
- standard library in the executable:
- https://code.qt.io/cgit/qt/qttools.git/tree/src/qdoc/qdoc.pro?h=5.11#n19.
+ parser. Clang needs the C++ standard library to work. Starting with
+ llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard library is no
+ longer on clang’s default search paths, so we need to pass it explicitly
+ as -I flag. The proposed qtbase patch (qdoc_default_incdirs.diff) does
+ that.
  
- From qttools-opensource-src 5.11.1-5 build log in Cosmic amd64, one can
- see that qdoc was compiled with
- -D'CLANG_RESOURCE_DIR="/usr/lib/llvm-6.0/lib/clang/6.0.1/include"'. So
- this directory needs to be present when qdoc is used. This directory is
- provided by libclang-common-6.0-dev package. So adding it to build-
- dependencies makes the documentation build correctly.
- 
- This is the minimal fix for Cosmic. For Ubuntu 19.04, I will try to use
- a better solution like moving the clang standard library detection from
- build time to run time, or making qttools5-dev-tools depend on the
- needed -dev packages.
+ That patch fixes documentation build for qtbase, but for other modules
+ there is another problem. The Qt headers are installed into
+ /usr/include//qt5 directory, but it is also not on Clang
+ default search path. qmake passes these directories as -isystem flags,
+ but qdoc ignores -isystem by default, unless it is built with
+ QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is building
+ with this define.
  
  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

** Also affects: qttools-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: qtdeclarative-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: qttools-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qttools-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in

[Touch-packages] [Bug 1803534] [NEW] Backport uuid based cache file naming scheme

2018-11-15 Thread James Henstridge

Public bug reported:

Fontconfig 2.13.0 changed the cache file naming scheme to be based on
the contents of ".uuid" file in the directory rather than a hash of the
directory name.  On a pure debs system this doesn't really matter since
everything is using the same libfontconfig.so.

When snaps are involved, it can lead to some apps not seeing the cache
files produced by a different fontconfig version.  In particular, while
libfontconfig 2.13 can reuse 2.12's cache files for read only
directories, the reverse is not true.  This will be a problem for apps
built on top of the "core18" base snap when run on later Ubuntu releases
(cosmic, disco, etc).

By providing a backport of the UUID cache file feature to bionic for use
by snap applications, we'd avoid this.  Having it in bionic-updates
would be ideal so that snapcraft picks it up automatically.

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

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

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

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

[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

2018-11-15 Thread Iain Lane

** Tags added: rls-cc-incoming

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

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

  xserver.version:

[Touch-packages] [Bug 1797224] Re: Stay on 2.0 for cosmic, update next cycle

2018-11-15 Thread Jeremy Bicha

** Tags removed: block-proposed

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Fix Committed

Bug description:
  The new version requires the MIR situation to be sorted out

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

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

[Touch-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04

2018-11-15 Thread William.Yeung

Dear Till,
Thanks for your investigation of this problem.

Below are the information we found maybe helpful for the investigation:
As we said before:"The phenomenon that print jobs slower in 16.04 is more
obvious when printing many jobs in the same time."
We figure out that the interval time of one print job to the next print job is
huge when print many jobs in the same time.
And the error_log files shows that the step below takes time , this step is
only exist in 16.04:
"Expiring subscriptions..."

Attach file description:
File 1: error_log.1-16.04-orca-rpdl-20181113_Job284_290: error_log of Job284 to
Job 290 is the consecutive printing 7 jobs on 16.04 in the same time.

File 2:error_log.2-14.04-orca-rpdl-20181114_Job327_332 : error_log of Job327 to
Job 332 is the consecutive printing 7 jobs on 14.04 in the same time.
---

By the way, we did the ghostscript investigation of you advice, but we
didn't found it cause the slowdown problem.

Best Regards,

** Attachment added: "LogConsecutivePrinting.zip"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+attachment/5213036/+files/LogConsecutivePrinting.zip

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

Title:
Printing job in 16.04 is slower than in 14.04

Status in cups package in Ubuntu:
Incomplete

Bug description:
Ubuntu 16.04LTS
OS Version： 16.04.5
CUPS Version： 2.1.3
Ghostscript Version： 9.25 （2018-09-13）

Printing job in 16.04 is slower than in 14.04

We(RICOH printer driver developer) are report a problem from our printer
users:
I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
print the same file with the same driver is slow(326 Seconds).

I figure out that all the print jobs is much slower on Ubuntu 16.04.

I view the "CUPS Error Log", it shows that there are three points
which maybe the reasons that makes the print job slowly.

FIRST:

By counting the time from "Starting renderer" to "renderer exited with status
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
So we assuming that："renderer" is one of the key process that makes the print
job slowly.

"Starting renderer with command: \"printf \'\\033%%-12345X@PJL
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\ @PJL
EOJ\\012\\033%%-12345X\'\""
.
renderer exited with status 0"

SECOND:

On 16.04, a print job outputs lots of logs as below:
"[Job xxx] Removing document files."

This step(“Removing document files”)does not exsit on 14.04.

The phenomenon that print jobs slower in 16.04 is more obvious when printing
many jobs in the same time.

THIRD
We tried drivers form other company(HP,Brother…), the printings also slow
down in Ubuntu 16.04 than 14.04.

Our question is:
1. Do you have any plan to improve the performance of printing on Ubuntu
16.04?
2. Do you have any workaround before this problems fixed?

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-11-15 Thread Kai-Heng Feng

This requires the following fixes:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19fffc8450d4378580a8f019b195c4617083176f
https://gitlab.freedesktop.org/upower/upower/merge_requests/19
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/278
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/266

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gnome-control-center (Ubuntu Artful)

** No longer affects: gnome-shell (Ubuntu Artful)

** No longer affects: upower (Ubuntu Artful)

** No longer affects: linux (Ubuntu Artful)

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  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/gnome-control-center/+bug/1745032/+subscriptions

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

[Touch-packages] [Bug 1801128] Re: OpenSSH 7.7 -w tunnel bug

2018-11-15 Thread  Christian Ehrhardt 

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

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

Title:
  OpenSSH 7.7 -w tunnel bug

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  A regression in OpenSSH 7.7 breaks tunnelling via the -w switch in the
  ssh command.

  [Test Case]

  # lxc launch ubuntu:cosmic tester && lxc exec tester bash

  # apt update && \
  apt dist-upgrade -y && \
  sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' 
/etc/ssh/sshd_config && \
  service sshd restart && \
  echo ubuntu:ubuntu | chpasswd

  # ssh -w any ubuntu@localhost
  ubuntu@localhost's password: 
  Tunnel device open failed.
  Could not request tunnel forwarding.

  [Regression Potential]

  This is already fixed and tested upstream, and thus has little
  regression potential.

  [Original Description]

  Just upgraded to cosmic, which picks up OpenSSH 7.7.

  OpenSSH 7.7 has known bug
  https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in
  OpenSSH 7.8. It's a regression that completely breaks -w tunneling.

  The OpenSSH bug contains a trivial two-line patch to fix the bug. I
  downloaded the Ubuntu openssh package source, applied the patch and
  rebuilt, and can confirm that is does fix the problem.

  Any chance we could get this patch backported to Cosmic?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: openssh-client 1:7.7p1-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Thu Nov 1 09:36:16 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass N/A
   libpam-ssh N/A
   keychain N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago)

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

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

[Touch-packages] [Bug 1801302] Re: Disconnected wired connection on dock after startup - reason 'carrier-changed' after update to 18.10

2018-11-15 Thread Lubomir Stanko

I've tried to clean install Ubuntu 18.10. I don't have this problem
anymore. So I'm closing this issue. I suppose clean install could fix a
lot of things.

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

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

Title:
  Disconnected wired connection on dock after startup - reason 'carrier-
  changed' after update to 18.10

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I have a problem with wired connection while connected in docking
  station on startup after update from Ubuntu 18.04 to 18.10.

  HW info:
  Manufacturer: LENOVO
  Product Name: 20HGS27000
  Version: ThinkPad T470s
  Serial Number: PC0MJA2W
  BIOS Version: N1WET51W (Release Date: 09/14/2018)

  System info:
  $ lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.12.4-1ubuntu1
Candidate: 1.12.4-1ubuntu1
Version table:
   *** 1.12.4-1ubuntu1 500
  500 http://sk.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ uname -a
  Linux citadel 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps to reproduce:
  1. Update Ubuntu from 18.04 to 18.10
  2. Start the laptop on docking station
  3. Laptop is trying to connect automatically on wired connection after 
startup, but not successfully.
  Log:
  $ journalctl -u NetworkManager
  nov 02 07:34:30 citadel NetworkManager[1158]:   [1541140470.6335] 
device (enp0s31f6): state change: ip-config -> unavailable (reason 
'carrier-changed', sys-iface-state: 'managed')
  nov 02 07:34:30 citadel NetworkManager[1158]:   [1541140470.6979] dhcp4 
(enp0s31f6): canceled DHCP transaction, DHCP client pid 3447
  nov 02 07:34:30 citadel NetworkManager[1158]:   [1541140470.6979] dhcp4 
(enp0s31f6): state changed unknown -> done
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.3778] 
device (enp0s31f6): carrier: link connected
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.3780] 
device (enp0s31f6): state change: unavailable -> disconnected (reason 
'carrier-changed', sys-iface-state: 'managed')
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.3787] 
policy: auto-activating connection 'Wired connection' 
(9a6bb9a9-2739-4bdc-b853-0eec29c6e42d)
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.3797] 
device (enp0s31f6): Activation: starting connection 'Wired connection' 
(9a6bb9a9-2739-4bdc-b853-0eec29c6e42d)
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.3799] 
device (enp0s31f6): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.4719] 
device (enp0s31f6): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.4725] 
device (enp0s31f6): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.4728] dhcp4 
(enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
  nov 02 07:34:32 citadel NetworkManager[1158]:   [1541140472.4778] dhcp4 
(enp0s31f6): dhclient started with pid 3689
  nov 02 07:34:32 citadel dhclient[3689]: DHCPREQUEST of 10.10.20.214 on 
enp0s31f6 to 255.255.255.255 port 67 (xid=0x687f173)
  nov 02 07:34:35 citadel dhclient[3689]: DHCPREQUEST of 10.10.20.214 on 
enp0s31f6 to 255.255.255.255 port 67 (xid=0x687f173)
  nov 02 07:34:38 citadel NetworkManager[1158]:   [1541140478.4738] 
device (enp0s31f6): state change: ip-config -> unavailable (reason 
'carrier-changed', sys-iface-state: 'managed')
  nov 02 07:34:38 citadel NetworkManager[1158]:   [1541140478.5066] dhcp4 
(enp0s31f6): canceled DHCP transaction, DHCP client pid 3689
  nov 02 07:34:38 citadel NetworkManager[1158]:   [1541140478.5067] dhcp4 
(enp0s31f6): state changed unknown -> done
  nov 02 07:34:40 citadel NetworkManager[1158]:   [1541140480.2266] 
device (enp0s31f6): carrier: link connected
  nov 02 07:34:40 citadel NetworkManager[1158]:   [1541140480.2273] 
device (enp0s31f6): state change: unavailable -> disconnected (reason 
'carrier-changed', sys-iface-state: 'managed')
  nov 02 07:34:40 citadel NetworkManager[1158]:   [1541140480.2298] 
policy: auto-activating connection 'Wired connection' 
(9a6bb9a9-2739-4bdc-b853-0eec29c6e42d)
  nov 02 07:34:40 citadel NetworkManager[1158]:   [1541140480.2354] 
device (enp0s31f6): Activation: starting connection 'Wired connection' 
(9a6bb9a9-2739-4bdc-b853-0eec29c6e42d)
  nov 02 07:34:40 citadel NetworkManager[1158]:   [1541140480.2361] 
device (enp0s31f6): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')

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

Can you please:

1. Change the bug title to better describe the problem; and

2. Attach a video of the problem.

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Xorg freeze

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Moving a window, on the bottom of screen there is a zone of 2 or 3 cm you 
can't pas the window.
  The down movement is blocked and the mouse cursor with the closed hand moves 
down into the inner window area. When you try to move the window ones again 
upwards you will see a broken graphic part of the window as background and the 
graphic structure of the window get lost. All these movements with the left 
mouse bottom pressed.
  But:
  If you move first the window to the left border and forward out of the screen 
area you can move the window down without the graphic problem. If at least a 
small part of the window is outside of the left screen area you can move the 
window up again passing through the bottom zone of 2 or 3 cm without problems.
  On the right-hand side of the screen area these movements are impossible.

  A big problem you will have with a windows virtual machine in full screen 
mode.
  You can't use the bottom menu.

  (This week y made the upgrade from 16.04.n to 18.04.1 with big graphic 
problems, black screen etc.
  Then reinstall gnome from command line solved the problems with black screen.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 08:07:37 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 0a) (prog-if 00 [VGA controller])
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
  InstallationDate: Installed on 2016-03-17 (972 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 360
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.96+git1811120630.e642f4~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1811141930.e13dd7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1811141930.e13dd7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1811071935.5e6fa5~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1811140735.746ab3~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b
  xserver.bootTime: Wed Nov 14 13:05:37 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard Hub KEYBOARD, id 8
   inputDell Dell USB Keyboard Hub KEYBOARD, id 9
   inputMicrosoft Basic Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Touch-packages] [Bug 1803491] [NEW] in codeblocks ide

2018-11-15 Thread khushboo jain

Public bug reported:

the system is taking much time to boot and hangs when codeblocks ide is
opened.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 15 11:26:35 2018
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, x86_64: 
installed
 oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: 
installed
 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: 
installed
 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: 
installed
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0841]
InstallationDate: Installed on 2018-08-26 (80 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Vostro 3478
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=01b2b9ec-7c39-4d22-8f6c-e43fcdc44c2b ro acpi_rev_override quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 08R7RH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnVostro3478:pvr:rvnDellInc.:rn08R7RH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Vostro 3478
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.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.1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Nov 15 11:15:34 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1805 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  in codeblocks ide

Status in xorg package in Ubuntu:
  New

Bug description:
  the system is taking much time to boot and hangs when codeblocks ide
  is opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 15 11:26:35 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, 
x86_64: installed
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: 
installed
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if

[Touch-packages] [Bug 1791484] Re: [FFe] Update tracker and tracker-miners to 2.1.4

This bug was fixed in the package tracker - 2.1.6-1

---
tracker (2.1.6-1) unstable; urgency=medium

  * New upstream release
  * Cherry-pick libtracker-miners-common-Make-g_error-a-soft-error.patch:
- Allow tracker library to still be used without ontology rules
  (Closes: #908800)

 -- Jeremy Bicha   Mon, 12 Nov 2018 17:34:31 -0500

** Changed in: tracker (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  [FFe] Update tracker and tracker-miners to 2.1.4

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Invalid

Bug description:
  To go along with the rest of GNOME 3.30
  Both tracker and tracker-miners 2.1.4 will be synced from Debian. 

  tracker is not installed by default on any Ubuntu Flavours, but does
  provide an important part of the GNOME-Shell experience.

  These releases bring lots of fixes and a few new features.

  Tracker NEW in 2.1.4 - 2018-09-04
  =

* Fix build with format-security flag

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Fix resource refcounting issues in database. Reset is advised.
* Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights
* Fix superfluous ontology checks on second tracker-store run
* Use more SPARQL1.1 correct syntax.
* Allow use of domain rules outside prefix
* Compatibility fixes with C++

  Translations: gl, id, ko

  NEW in 2.1.2 - 2018-08-15
  =

* libtracker-sparql: Delete TrackerResource elements one by one
* libtracker-sparql: Fix compilation with C++
* build: Fixes for FreeBSD
* build: Fixes on meson

  Translations: cs, el, fr, fur, hu, sl, tr, zh_TW

  NEW in 2.1.1 - 2018-08-01
  =

* libtracker-direct: Plug leaks
* libtracker-sparql-backend: Fix fallback from direct to bus
  connection for queries.

  Translations: es, lt, ro

  NEW in 2.1.0 - 2018-07.22
  =

* Brown paper bag release
* All features from unreleased 2.0.5 apply
* One feature was missed: TrackerResource is now able to output
  JSON-LD. This is a new API call, so a minor bump should happen
  as per Semantic Versioning.

From 2.0.5 NEWS:
* build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
* build: Various meson build fixes
* tests: Many fixes to functional tests
* libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
* libtracker-direct: Majorly rewritten
* tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  Tracker-miners NEW in 2.1.4 - 2018-09-04
  =

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Unbreak watch on domain ontology owner. Fixes miners spuriously
  exiting.

  NEW in 2.1.2 - 2018-08-30
  =

* Allow use of domain rules outside prefix
* Add core-as-subproject as explicit meson option
* Ensure utf8ness in TrackerResource helpers
* Fix multiple cardinality issues in different extractors/properties
* Other minor SPARQL correctness fixes

  Translations: gl, id, ko

  NEW in 2.1.1 - 2018-08-15
  =

* tracker-miner-fs: Ignore mercurial repositories
* build: Fix build with -Werror=format-security
* tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors
* tracker-extract: Do not add named destinations to PDF TOCs
* tracker-extract: Ignore XMP image metadata on PDFs
* tracker-extract: Fix ISO 8601 date string generation on gstreamer 
extractor

  Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW

  NEW in 2.1.0 - 2018-07-23
  =

* tests: Many updates and fixes to functional tests
* tracker-extract: Better infrastructure for tests, based on JSON-LD
* tracker-miner-fs: Restart tracker extract from the right domain
* tracker-extract: Persistently avoid files that trigger recoverable
  errors, to avoid log spamming on restarts.

  Translations: de, es, it, pl, pt_BR, ro, sv

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

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

[Touch-packages] [Bug 1803503] Re: package vim-runtime 2:8.0.1453-1ubuntu1 failed to install/upgrade: installed vim-runtime package post-installation script subprocess returned error exit status 255