[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-12-14 Thread Wayne Bell
Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390,
396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from
beta and previously 18.04 as original install)

Resolved by switching to lightdm and booting into Cinnamon Desktop instead of 
Gnome.  Mate works as well.
Also uncommented "WaylandEnable=false" for future possible use of gdm3 and 
gnome desktop.

Can someone either mark this as "not fixed" or "won't fix" since it's
clearly not resolved.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Touch-packages] [Bug 1808618] [NEW] package grep 2.5.4-4 failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile returned error exit status 2

2018-12-14 Thread Hany Mahmoud
Public bug reported:

i am using an old version of ubuntu 9.10 
problem is i have an old machine without cdrom and need to upgrade my system to 
any stable version of ubuntu .

ProblemType: Package
Architecture: i386
Date: Sat Dec 15 08:17:01 2018
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: grep 2.5.4-4
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: grep
Title: package grep 2.5.4-4 failed to install/upgrade: subprocess dpkg-deb 
--fsys-tarfile returned error exit status 2
Uname: Linux 2.6.31-14-generic i686

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


** Tags: apport-package i386

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

Title:
  package grep 2.5.4-4 failed to install/upgrade: subprocess dpkg-deb
  --fsys-tarfile returned error exit status 2

Status in grep package in Ubuntu:
  New

Bug description:
  i am using an old version of ubuntu 9.10 
  problem is i have an old machine without cdrom and need to upgrade my system 
to any stable version of ubuntu .

  ProblemType: Package
  Architecture: i386
  Date: Sat Dec 15 08:17:01 2018
  DistroRelease: Ubuntu 9.10
  ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: grep 2.5.4-4
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: grep
  Title: package grep 2.5.4-4 failed to install/upgrade: subprocess dpkg-deb 
--fsys-tarfile returned error exit status 2
  Uname: Linux 2.6.31-14-generic i686

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

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


[Touch-packages] [Bug 1808611] [NEW] chamelon

2018-12-14 Thread Michael
Public bug reported:

export PATH=$PATH:/data/user/0/burrows.apps.busybox/app_busybox; export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/user/0/burrows.apps.busybox/app_busybox

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

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

Title:
  chamelon

Status in iputils package in Ubuntu:
  New

Bug description:
  export PATH=$PATH:/data/user/0/burrows.apps.busybox/app_busybox;
  export
  LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/user/0/burrows.apps.busybox/app_busybox

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

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


[Touch-packages] [Bug 1808610] [NEW] chamelon

2018-12-14 Thread Michael
Public bug reported:


Search or scan a URL, IP address, domain, or file hash
Sign in
1 / 61
One engine detected this file
SHA-25676e27c4b09f9c1cbbf0b414719b741d3087fc744f6de9431a282fbd976bd445a
File namemssoJ77AHDuALWGu6G
File size11.78 MB
Last analysis2018-03-28 08:17:09 UTC
Detection
Details
Relations
Behavior
Community
VirusTotal Droidy
Detailed report
Network Communication
HTTP Requests
http://api.exc.mob.com:80/errconf
http://api.share.mob.com:80/conn
http://api.share.mob.com:80/snsconf
https://static.yuanbaopu.com/hotcode/fidewd/
http://api.share.mob.com:80/conf4
http://api.share.mob.com:80/data2
http://api.share.mob.com:80/date
http://loc.map.baidu.com/offline_loc
http://loc.map.baidu.com/sdk.php
http://loc.map.baidu.com/statloc
DNS Resolutions
loc.map.baidu.com
180.97.104.187
cdn.polyfill.io
151.101.122.109
dualstack.f3.shared.global.fastly.net
151.101.122.109
api.share.mob.com
newloc.map.n.shifen.com
api.exc.mob.com
static.yuanbaopu.com
IP Traffic
61.174.10.208:80 (TCP)
120.132.176.173:80 (TCP)
151.101.122.109:443 (TCP)
182.254.154.23:443 (TCP)
180.97.104.187:80 (TCP)
File System Actions
Files Opened
/data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml
/data/misc/keychain/pins
/storage/emulated/0/ShareSDK/com.yuanbaopu.ybpmark/cache/com.yuanbaopu.ybpmark/.lock
/storage/emulated/0/baidu/.cuid
/proc/net/if_inet6
/sys/class/net/ip6tnl0/ifindex
/sys/class/net/lo/ifindex
/sys/class/net/sit0/ifindex
/sys/class/net/eth0/ifindex
/storage/emulated/0/ShareSDK/.dk
Files Written
/storage/emulated/0/baidu/tempdata/ls.db
/data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_location.db
/data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_statistics.db
/storage/emulated/0/test.0
/data/data/com.yuanbaopu.ybpmark/files/ofld/ofl.config
/storage/emulated/0/baidu/tempdata/ller.dat
/storage/emulated/0/baidu/tempdata/conlts.dat
/storage/emulated/0/baidu/tempdata/grtcf.dat
Files Deleted
/data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml.bak
/data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml
/data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml.bak
/data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml
/storage/emulated/0/test.0
Files Copied
/data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml
/data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml
Files Dropped
36ac59e578357746f7ab39a543f47e84260ca584534b3bbf3371bc1f4b407fd9
Process And Service Actions
Permissions Checked
android.permission.READ_PHONE_STATE
android.permission.ACCESS_WIFI_STATE
android.permission.CHANGE_WIFI_STATE
android.permission.GET_TASKS
Shell Commands
su
Services Opened
com.google.android.gms.games.service.GamesIntentService (com.google.android.gms)
com.google.android.gms.people.service.bg.PeopleBackgroundTasks 
(com.google.android.gms)
Activities Started
com.yuanbaopu.ybpmark.MainActivity (com.yuanbaopu.ybpmark)
Synchronization Mechanisms & Signals
Signals Hooked
android.intent.action.PROXY_CHANGE
android.intent.action.CONFIGURATION_CHANGED
android.intent.action.PHONE_STATE
android.intent.action.PACKAGE_ADDED
android.intent.action.PACKAGE_REMOVED
android.net.wifi.SCAN_RESULTS
Modules Loaded
Runtime Modules
neh
locSDK6a
Invoked Methods
android.os.SystemProperties.addChangeCallback
android.os.SystemProperties.getLong
com.fasterxml.jackson.databind.MapperFeature.values
com.fasterxml.jackson.databind.DeserializationFeature.values
com.fasterxml.jackson.databind.SerializationFeature.values
com.android.org.conscrypt.OpenSSLCipher$Padding.values
com.android.org.conscrypt.OpenSSLCipher$Mode.values
android.net.wifi.SupplicantState.values
android.net.wifi.WifiSsid.createFromAsciiEncoded
com.nordnetab.chcp.main.model.ChcpError.values
Highlighted Actions
Calls Highlighted
android.net.wifi.WifiInfo.getBSSID
android.net.wifi.WifiInfo.getMacAddress
android.net.wifi.WifiInfo.getSSID
android.os.Debug.isDebuggerConnected
android.telephony.TelephonyManager.getCellLocation
android.telephony.TelephonyManager.getDeviceId
android.telephony.TelephonyManager.getNetworkCountryIso
android.telephony.TelephonyManager.getSimOperator
android.telephony.TelephonyManager.getSubscriberId
android.util.Base64.encode
Cryptographical Algorithms Observed
AES
Cryptographical Keys Observed
30212102dicudiab
sdk.sharesdk.sdk
14f0c07c317771a2
Encoding Algorithms Observed
base64
Dataset Actions
System Property Lookups
debug.force_rtl
debug.second-display.pkg
debug.atrace.tags.enableflags
sys.settings_system_version
persist.sys.timezone
persist.sys.ui.hw
debug.layout
sys.settings_secure_version
viewroot.profile_rendering
config.disable_media
Shared Preferences Sets
config_json
config_json
device_time
device_data
device_ext_data
service_time
lastInsertRunEventTime
insertRunEventCount
Content Model Observers
NOT CACHED
Content Model Sets
exception_time
exception_msg
exception_level
exception_md5
exception_time
exception_msg
exception_md5
exception_time
exception_msg
exception_md5

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread chovy
i have those lines already. this guide is terrible.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-12-14 Thread Not Martin Wimpress
I understand. Saying "the default is true" is a bit puzzling, but after
reading https://github.com/mvo5/unattended-upgrades/blob/master
/unattended-upgrade#L1957 , the conditional makes sense since the
default [object] is defined as "True". It also makes sense how this
works for proposed-16.04 since that line isn't even mentioned in the
config but "True" is pushed in the script anyway.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread craig jackson
Don't forget to 'sudo apt update' after making those changes.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread craig jackson
Just uncomment the deb-src lines in /etc/apt/sources.list.

For example, replace:

# deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main
restricted

With:

deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-12-14 Thread Steve Langasek
The line is commented out, that's what the leading // characters mean.
Therefore the default is used, and the default is true.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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


[Touch-packages] [Bug 1808605] [NEW] the screen graphics card and input device settings could not be detected correctly and in lightdm.log file it says fail to start a greeter, i hard shutdown my lapt

2018-12-14 Thread Michael Odumosu
Public bug reported:

the screen graphics card and input device settings could not be detected
correctly and in lightdm.log file it says  fail to start a greeter, i
hard shutdown my laptop many times also, I also made another user
without giving them a home directory does that help

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Dec 14 20:17:50 2018
InstallationDate: Installed on 2017-12-25 (354 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  the screen graphics card and input device settings could not be
  detected correctly and in lightdm.log file it says  fail to start a
  greeter, i hard shutdown my laptop many times also, I also made
  another user without giving them a home directory does that help

Status in lightdm package in Ubuntu:
  New

Bug description:
  the screen graphics card and input device settings could not be
  detected correctly and in lightdm.log file it says  fail to start a
  greeter, i hard shutdown my laptop many times also, I also made
  another user without giving them a home directory does that help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Dec 14 20:17:50 2018
  InstallationDate: Installed on 2017-12-25 (354 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 834575] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()

2018-12-14 Thread Bug Watch Updater
** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gsettings-data-convert crashed with signal 5 in g_settings_set_value()

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gconf2 3.1.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug 26 17:54:26 2011
  ExecutablePath: /usr/bin/gsettings-data-convert
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: gsettings-data-convert
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   g_settings_set_value () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   g_settings_set () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? ()
  Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
  UpgradeStatus: Upgraded to oneiric on 2011-08-25 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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


[Touch-packages] [Bug 1807134] Re: lxc 3.0.2/3 - cannot create root password in privileged container

2018-12-14 Thread km
The issue persists after having upgraded lxc to version 3.0.3

** Summary changed:

- lxc 3.0.2  - cannot create root password in privileged container
+ lxc 3.0.2/3  - cannot create root password in privileged container

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

Title:
  lxc 3.0.2/3  - cannot create root password in privileged container

Status in lxc package in Ubuntu:
  New

Bug description:
  Prior filing this as potential bug help was sought but did not yield a
  remedy

  https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root-
  password-in-privileged-container/3425

  host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor
  2.12

  Whilst there is no issue with creating a root password via lxc-attach
  and passwd in an unprivileged container it is however not possible to
  create a password the same way for a privileged container (tried
  centos 7 and ubuntu cosmic).

  Error reported from within the containers:

  passwd: System error
  passwd: Authentication token manipulation error

  Error reported at the host:

  passwd: PAM audit_log_acct_message() failed: Operation not permitted

  Next tried with:

  chroot /container/path/rootfs passwd

  but that produced the same error.

  Next tried with:

  lxc.cap.keep = CAP_AUDIT_WRITE

  but the container would not boot.

  Next tried with:

  lxc.apparmor.profile = unconfined

  but no remedy.

  Next switched the kernel to 4.19.7 but no dice either.

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

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


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

2018-12-14 Thread Matt Caswell
** Attachment added: "ufw.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222404/+files/ufw.tar.gz

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  Incomplete
Status in ufw source package in Xenial:
  Incomplete
Status in ufw source package in Bionic:
  Incomplete
Status in ufw source package in Cosmic:
  Incomplete
Status in ufw source package in Disco:
  Incomplete

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

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

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

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

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


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

2018-12-14 Thread Matt Caswell
** Attachment added: "dpkg.list"
   
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222403/+files/dpkg.list

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  Incomplete
Status in ufw source package in Xenial:
  Incomplete
Status in ufw source package in Bionic:
  Incomplete
Status in ufw source package in Cosmic:
  Incomplete
Status in ufw source package in Disco:
  Incomplete

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

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

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

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

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


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

2018-12-14 Thread Matt Caswell
** Attachment added: "ufw.raw"
   
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222405/+files/ufw.raw

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  Incomplete
Status in ufw source package in Xenial:
  Incomplete
Status in ufw source package in Bionic:
  Incomplete
Status in ufw source package in Cosmic:
  Incomplete
Status in ufw source package in Disco:
  Incomplete

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

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

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

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

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


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

2018-12-14 Thread Matt Caswell
I rebooted and confirmed that ufw still reports itself as inactive.
Attached are the requested files. Note: I only included the last 25000
lines from journal.full - otherwise I would have to upload 250Mb!

** Attachment added: "journal.full"
   
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222402/+files/journal.full

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  Incomplete
Status in ufw source package in Xenial:
  Incomplete
Status in ufw source package in Bionic:
  Incomplete
Status in ufw source package in Cosmic:
  Incomplete
Status in ufw source package in Disco:
  Incomplete

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

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

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

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

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


[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-12-14 Thread Not Martin Wimpress
Balint, I'm confused on your statement in the other dup bug report
(https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1357093/comments/129 ) that this is fixed in 18.04, but
looking at line 60 in the "50unattended-upgrades.Ubuntu" file in the
current package (1.1ubuntu1.18.04.7):

//Unattended-Upgrade::Remove-Unused-Kernel-Packages "false";

...it appears to me that 2 modifications are needed before any kernels
are auto-removed. I saw your Nov 9th commit to switch it to "true", but
doesn't the line still needs to be commented out in order to activate?

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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


[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

2018-12-14 Thread Christopher Snowhill
Yes, but this does not grant transparent access to the Documents folders
of installed applications. Pairing and libimobiledevice are still needed
for that.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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


[Touch-packages] [Bug 1661809] Re: failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-12-14 Thread Steve Langasek
I don't see anything in this bug report which references rpcbind; Jamie,
was this reassigned by mistake?

** Package changed: rpcbind (Ubuntu) => ufw (Ubuntu)

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

Title:
  failed to install/upgrade: subprocess installed post-removal script
  returned error exit status 1

Status in ufw package in Ubuntu:
  New

Bug description:
  I purged ufw from the system. systemctl list-unit-files showed UFW
  enabled.

  
  The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   ufw: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Feb  4 00:04:25 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ufw
  Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1661809] [NEW] failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-12-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I purged ufw from the system. systemctl list-unit-files showed UFW
enabled.


The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ufw (not installed)
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 ufw: Purge
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Feb  4 00:04:25 2017
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
InstallationDate: Installed on 2016-09-25 (131 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: ufw
Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial
-- 
failed to install/upgrade: subprocess installed post-removal script returned 
error exit status 1
https://bugs.launchpad.net/bugs/1661809
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ufw in Ubuntu.

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread chovy
ettinger@sunny:~
$ sudo apt-get build-dep linux-image-$(uname -r)
[sudo] password for ettinger: 
Sorry, try again.
[sudo] password for ettinger: 
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
ettinger@sunny:~
$ apt-get source linux-image-$(uname -r)
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
ettinger@sunny:~
$ sudo apt-get source linux-image-$(uname -r)
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

2018-12-14 Thread Jamie Strandboge
This is fixed in the new 0.36 release.

** Changed in: ufw
   Status: Fix Committed => Fix Released

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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


[Touch-packages] [Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
This is fixed in the new 0.36 release.

** Changed in: ufw
   Status: Fix Committed => Fix Released

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

Title:
  bash completion not working: uses deprecated have()

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress

Bug description:
  bash completion, defined in /usr/share/bash-
  completion/completions/ufw, doesn't work: the completion is not
  dynamically loaded, because it uses deprecated helper function have().

  According to /usr/share/bash-completions/bash_completion, which
  defines the helper functions:

  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.

  and at the end of the file:

  unset -f have
  unset have

  which means: function have() is not available for usage. The bash
  completion for ufw conditionally defines _ufw and the comspec:

  have ufw &&   


  _ufw()
  ...

  [ "$have" ] && complete -F _ufw ufw

  These should be changed to:

  _have ufw &&  

 
  _ufw()
  ...

  _have ufw && complete -F _ufw ufw

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ufw 0.35-5
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun  4 14:34:11 2018
  InstallationDate: Installed on 2018-04-28 (37 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1664133] Re: ipv6 multicast pings don't return

2018-12-14 Thread Jamie Strandboge
This is fixed in the new 0.36 release.

** Changed in: ufw
   Status: Fix Committed => Fix Released

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

Title:
  ipv6 multicast pings don't return

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress

Bug description:
  Hi,
  I have the default settings from Linux Mint 18 for ufw. When I "ping6 
ff02::1%wlp3s0", I get only an answer from my own ip. Duplicates from other 
devices on the net get filtered. It works fine after "sudo ufw disable".

  ufw --version
  ufw 0.35
  Copyright 2008-2015 Canonical Ltd.

  I've attached the output of ip6tables-save.

  There is a similar old and long fixed bug:
  https://bugs.launchpad.net/ufw/+bug/720605

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

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


[Touch-packages] [Bug 1633698] Re: ufw before6.rules adds echo-request and echo-response rules to wrong chain

2018-12-14 Thread Jamie Strandboge
This is fixed in the new 0.36 release.

** Changed in: ufw
   Status: Fix Committed => Fix Released

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

Title:
  ufw before6.rules adds echo-request and echo-response rules to wrong
  chain

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  The default before6.rules file that is installed with the ufw package
  contains a copy/paste error. It is apparent that the intention is to
  add rules for echo-request and echo-response to the following chains:

  ufw6-before-input
  ufw6-before-output
  ufw6-before-forward

  However there is a copy/paste error and instead of adding the rules to
  ufw6-before-output, it adds it to ufw6-before-input a second time. The
  result is that the rules are absent from ufw6-before-output.

  The file that needs to be fixed in the package is:
  /usr/share/ufw/iptables/before6.rules

  Here is what diff -u shows if I compare the original file to the
  corrected version:

  --- /usr/share/ufw/iptables/before6.rules 2016-04-15 17:16:29.0 
+1200
  +++ ufw_fixed_before6.rules   2016-10-15 23:00:57.763041239 +1300
  @@ -77,8 +77,8 @@
   -A ufw6-before-output -p icmpv6 --icmpv6-type time-exceeded -j ACCEPT
   # codes 0-2
   -A ufw6-before-output -p icmpv6 --icmpv6-type parameter-problem -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type router-solicitation -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-advertisement -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-solicitation -m hl 
--hl-eq 255 -j ACCEPT

  The impact of this error is minor because the ufw.conf file sets the default 
outbound policy to accept:
  DEFAULT_OUTPUT_POLICY="ACCEPT"

  Of course if anyone changed the default outbound policy then the error
  would mean that pings made from the server to other machines would be
  blocked.

  I will attach the original and my fixed version of before6.rules to
  this bug report.

  Thanks for taking the time to look at this issue.

  Nick.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ufw 0.35-2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sat Oct 15 23:09:04 2016
  InstallationDate: Installed on 2016-10-14 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

2018-12-14 Thread Jamie Strandboge
This is fixed in the new 0.36 release.

** Changed in: ufw
   Status: Fix Committed => Fix Released

** Changed in: ufw
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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


[Touch-packages] [Bug 1804558] Re: ubuntu-bug opens external brower synchronously

2018-12-14 Thread Juhani Numminen
Hi,

to close a bug, simply set its status accordingly.

Regards,
Juhani

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

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

Title:
  ubuntu-bug opens external brower synchronously

Status in apport package in Ubuntu:
  Invalid

Bug description:
  The ubuntu-bug script opens a web browser for the user to enter bug
  details directly on launchpad; however, it does so synchronously, thus
  needlessly tying up the linux terminal. The browser should be launched
  asynchronously (eg. cd ; nohup firefox & disown ; cd - )

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu13.1
  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.1
  Architecture: amd64
  CrashReports:
   640:1000:118:3259756:2018-11-21 01:45:22.691858609 -0500:2018-11-21 
01:45:13.699984813 -0500:/var/crash/_usr_bin_qterminal.1000.crash
   640:1000:118:12037880:2018-11-21 10:54:46.573234972 -0500:2018-11-21 
10:54:31.229049840 -0500:/var/crash/_usr_bin_transmission-qt.1000.crash
  CurrentDesktop: LXQt
  Date: Wed Nov 21 20:41:07 2018
  InstallationDate: Installed on 2018-11-21 (0 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1808581] [NEW] cannot print to Canon MX860 after upgrade to Ubuntu 18.04

2018-12-14 Thread Kim Eckert
Public bug reported:

After upgrading to Ubuntu 18.04, I can no longer print to my Canon MX860. It is 
connected to my WiFi network.
- I can successfully ping the printer.
- I can connect to the printer via the printer web server.
- When I try to print, it just hangs: no error messages, no printing.
Additional information was submitted with 'ubuntu-bug cups'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 14 13:30:40 2018
InstallationDate: Installed on 2015-01-10 (1434 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
KernLog:
 
Lpstat: device for MX860: cnijnet:/00:1E:8F:74:5A:78
MachineType: MSI MS-7865
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/MX860.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MX860.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=c7580c78-9be5-43e5-8256-d02dd697238b ro plymouth:debug drm.debug=0xe
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2018-08-16 (120 days ago)
dmi.bios.date: 02/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V10.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: AM1I (MS-7865)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7865
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug bionic

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

Title:
  cannot print to Canon MX860 after upgrade to Ubuntu 18.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, I can no longer print to my Canon MX860. It 
is connected to my WiFi network.
  - I can successfully ping the printer.
  - I can connect to the printer via the printer web server.
  - When I try to print, it just hangs: no error messages, no printing.
  Additional information was submitted with 'ubuntu-bug cups'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 14 13:30:40 2018
  InstallationDate: Installed on 2015-01-10 (1434 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  KernLog:
   
  Lpstat: device for MX860: cnijnet:/00:1E:8F:74:5A:78
  MachineType: MSI MS-7865
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/MX860.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MX860.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=c7580c78-9be5-43e5-8256-d02dd697238b ro plymouth:debug drm.debug=0xe
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (120 days ago)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AM1I (MS-7865)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7865
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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


[Touch-packages] [Bug 1761508] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

2018-12-14 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214

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

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

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  updates applied..   then upon reboot..  I got this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Apr  3 10:56:24 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20BHS0G900
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=140091728889600, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (6 days ago)
  UserGroups:
   
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET73WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS0G900
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET73WW(2.21):bd03/12/2015:svnLENOVO:pn20BHS0G900:pvrThinkPadW540:rvnLENOVO:rn20BHS0G900:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS0G900
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

2018-12-14 Thread spm2011
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214

I'm seeing this as well, after closing lid and resuming in an attempt to
reset an unresponsive, seemingly thrashing system with many tabs open in
Firefox.

Where is bug #1754214 ?

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ???

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 06:46:33 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-21 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  Lsusb:
   Bus 002 Device 002: ID 0781:5591 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1760992] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

2018-12-14 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214

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

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

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I haven't a clue who what where why but its' nice to be included. I
  wanna give a shout out to my homies Stryfer for his awesome gaming
  abilities. My homeboy Tuko for his spiritual guidance and myself, I'd
  like to say thank you Ubuntu for all that you are and do! Pew, pew!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  Date: Mon Apr  2 18:46:46 2018
  ExecutablePath: /lib/systemd/systemd-journald
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: MSI MS-7903
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt persistent 
boot=casper 
iso-scan/filename=/multiboot/hostname-bionic-desktop-amd64/hostname-bionic-desktop-amd64.iso
 quiet --
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=140009756866304, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM GAMING (MS-7903)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd08/18/2016:svnMSI:pnMS-7903:pvr1.0:rvnMSI:rnA88XMGAMING(MS-7903):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7903
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Touch-packages] [Bug 1273752] Re: Can't Copy Crash Report Details to Clipboard

2018-12-14 Thread spm2011
** Also affects: apport
   Importance: Undecided
   Status: New

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

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

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  New

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

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

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


[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-14 Thread Brian Murray
** Changed in: software-properties (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: software-properties (Ubuntu Cosmic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Triaged

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

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

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


[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-14 Thread Brian Murray
** Changed in: software-properties (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Cosmic)
   Importance: Undecided => High

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Triaged

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

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

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


[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-14 Thread Jarno Suni
I can verify the update-notifier 3.168.10
Did not test unattended-upgrades
Did not change the tag since it is the same for unattended-upgrades 
unfortunately.

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1641928] Re: "Unknown audio device" dialog pops up every time I plug in headphones

2018-12-14 Thread tom
Finally fixed.

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

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

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I used to use Ubuntu 15.10 for a long time and everything was fine. As
  soon as I installed (clean install) Ubuntu 16.04 the dialog started
  appearing every time I plugged in my earphones. Problem still present
  on 16.10.

  -Saw this bug report 
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790
  -In there someone posted a link to 
http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/
  -which encourages users to submit their own bug reports using ubuntu-bug 
audio in order to collect hw info, so I did.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoltan  F pulseaudio
   /dev/snd/controlC1:  zoltan  F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:48:15 2016
  InstallationDate: Installed on 2016-10-15 (30 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (22 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1602834] Re: obsolete conffiles not cleaned up on upgrade

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress

Bug description:
  Hi,

  the following conffile is marked as obsolete in my dpkg status db

   /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete

  Ufw now ships /usr/share/bash-completion/completions/ufw, so the
  conffile should be removed on upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:19:52 2016
  InstallationDate: Installed on 2011-11-10 (1706 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago)

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

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


[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

2018-12-14 Thread Thadeu Lima de Souza Cascardo
https://lore.kernel.org/linux-block/20181213113549.GA7543@calabresa/T/#t

Upstream discussion in progress.

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   

[Touch-packages] [Bug 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test

2018-12-14 Thread Stefano Cappa
The same for avahi 0.7 also with bonjour conformance test 1.4.0

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

Title:
  avahi-0.6.31 doesn't pass Apple conformance test

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  We are working on to support Apple bonjour conformance test-1.3.0 and
  test fails with avahi version 0.6.31 for test case - SRV
  PROBING/ANNOUNCEMENTS. This test fails both on IPV4 and IPV6. And the
  configured network package - dhcpcd-6.6.4.

  After parsing all logs(wireshark, apple PC and linux PC syslogs), and
  looks like avahi does not support a particular scenario in which Apple
  bonjour conformance test looks for. And also confirmed Apple test is
  inline with the RFC 6762 document for a special use-case(resolving SRV
  names on power up).

  Below is the bug description,

  setup:
  Apple MAC with Bonjour conformance test - 1.3.0 (latest OS x)
  Apple airport  (latest version)
  Linux device(PC) (ubuntu 14.04)

  Configure all above devices to communicate on link local mode.

  1) Start avahi bonjour conformance test on APPLE PC and Power ON linux
  device with avahi-0.6.31 and with _ssh._tcp.local service file

  2) First Linux device sends SRV initial probe message on link and followed by 
apple test sends same SRV (Linux device) question on link,
 example:(commands on wire shark)
  Linux Device sends ->  Who has "SSH" SRV QM question?
  Apple Bonjour Conformance Test -> Who has "SSH" SRV QM question?

  3) Then after this there is no message from Linux device on network and Apple 
test expecting new SRV probe message from device.
And so conformance test failed, since device couldn't able to send new 
SRV probe message with new name for service "SSH"

  4) After parsing log files found that,
 avahi-daemon logged service with new name ("SSH #2") in log file and could 
not publish/probe SRV message on network.

Linux device syslog messages,
Loading service file /etc/avahi/services/ssh.service
Service name conflict for "SSH" (/etc/avahi/services/ssh.service), 
retrying with "SSH #2).

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

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


[Touch-packages] [Bug 1808193] ProcCpuinfoMinimal.txt

2018-12-14 Thread Irfan
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1808193/+attachment/5222353/+files/ProcCpuinfoMinimal.txt

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: upower
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1808193] ProcEnviron.txt

2018-12-14 Thread Irfan
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1808193/+attachment/5222354/+files/ProcEnviron.txt

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: upower
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1808193] GsettingsChanges.txt

2018-12-14 Thread Irfan
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1808193/+attachment/5222352/+files/GsettingsChanges.txt

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: upower
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in

2018-12-14 Thread Irfan
apport information

** Description changed:

  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-10 (4 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: upower
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1808193/+attachment/5222351/+files/Dependencies.txt

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: upower
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1808557] Re: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

2018-12-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in network-manager package in Ubuntu:
  New

Bug description:
  the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
  Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
  It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
  In the small window it was stated that libnm-glib-vpn1:i386 would be in total 
bad shape so it should be removed and reinstalled. This is now done. But that 
seems only the result of  an instability occuring lately quite often with 
Ubuntu, starting with some larger uodate a couple of months ago. 
  I know this is not a very precise description. I will now clean up the system 
starting with verifying all packages. The instability will probably remain 
though. 
  In the process the gui was also updated and seems now to be functioning, so 
the version is now 
  ubuntu-software 3.20.5-0ubuntu0 i386 . 
  There are similar issues of being outphased  with libreoffice, evince and 
probably some more which we seldom use.
  The common link between these errors is that contact with X is temporarily 
lost while free memory is low.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Fri Dec 14 15:49:36 2018
  DuplicateSignature:
   package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
   dpkg: error processing package libnm-glib-vpn1:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-25 (476 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.103  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
dlink-5C98  af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1808557] [NEW] package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

2018-12-14 Thread Leo Germeys
Public bug reported:

the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
In the small window it was stated that libnm-glib-vpn1:i386 would be in total 
bad shape so it should be removed and reinstalled. This is now done. But that 
seems only the result of  an instability occuring lately quite often with 
Ubuntu, starting with some larger uodate a couple of months ago. 
I know this is not a very precise description. I will now clean up the system 
starting with verifying all packages. The instability will probably remain 
though. 
In the process the gui was also updated and seems now to be functioning, so the 
version is now 
ubuntu-software 3.20.5-0ubuntu0 i386 . 
There are similar issues of being outphased  with libreoffice, evince and 
probably some more which we seldom use.
The common link between these errors is that contact with X is temporarily lost 
while free memory is low.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
Uname: Linux 4.4.0-140-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Fri Dec 14 15:49:36 2018
DuplicateSignature:
 package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
 dpkg: error processing package libnm-glib-vpn1:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-08-25 (476 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.103  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
dlink-5C98  af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: apport-package i386 xenial

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

Title:
  package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in network-manager package in Ubuntu:
  New

Bug description:
  the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
  Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
  It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
  

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

2018-12-14 Thread Cristian Aravena Romero
Hello Brian Murray (brian-murray),

Will this change come in the next version?

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-12-14 Thread Jamie Strandboge
@Matt, there aren't any errors in your journalctl output that I can see.

Without removing the change to /lib/ufw/ufw-init yet, can you reboot
until you see the problem, and then before you correct the issue, can
you attach the output of all of the following:

1. journalctl --no-pager > /tmp/journal.full
2. dpkg -l > /tmp/dpkg.list
3. sudo tar -zcf /tmp/ufw.tar.gz /lib/ufw/ /etc/default/ufw /etc/ufw/ 
/usr/share/ufw/
4. sudo ufw show raw > /tmp/ufw.raw


** Also affects: ufw (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  Incomplete
Status in ufw source package in Xenial:
  Incomplete
Status in ufw source package in Bionic:
  Incomplete
Status in ufw source package in Cosmic:
  Incomplete
Status in ufw source package in Disco:
  Incomplete

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

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

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

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

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


[Touch-packages] [Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Disco)
   Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
   Status: Triaged

** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

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

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

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

Title:
  bash completion not working: uses deprecated have()

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

Bug description:
  bash completion, defined in /usr/share/bash-
  completion/completions/ufw, doesn't work: the completion is not
  dynamically loaded, because it uses deprecated helper function have().

  According to /usr/share/bash-completions/bash_completion, which
  defines the helper functions:

  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.

  and at the end of the file:

  unset -f have
  unset have

  which means: function have() is not available for usage. The bash
  completion for ufw conditionally defines _ufw and the comspec:

  have ufw &&   


  _ufw()
  ...

  [ "$have" ] && complete -F _ufw ufw

  These should be changed to:

  _have ufw &&  

 
  _ufw()
  ...

  _have ufw && complete -F _ufw ufw

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ufw 0.35-5
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun  4 14:34:11 2018
  InstallationDate: Installed on 2018-04-28 (37 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1724793] Re: Error localization

2018-12-14 Thread Jamie Strandboge
** Package changed: ufw (Ubuntu) => language-selector (Ubuntu)

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

Title:
  Error localization

Status in language-selector package in Ubuntu:
  New

Bug description:
  After some manipulation of the system interface of the OS was in
  English, as all the default startup application. I tried to change the
  locale via GUI, however, everything on the ground.

  ---
  После некоторых манипуляций с системой интерфейс ОС стал на английском, как и 
все запускаемые по умолчанию приложения. Пробовал изменить локаль через ГУИ, 
однако там всё на местах.

  locale
  LANG=ru_RU.UTF-8
  LANGUAGE=C.UTF-8
  LC_CTYPE="ru_RU.UTF-8"
  LC_NUMERIC="ru_RU.UTF-8"
  LC_TIME="ru_RU.UTF-8"
  LC_COLLATE="ru_RU.UTF-8"
  LC_MONETARY="ru_RU.UTF-8"
  LC_MESSAGES="ru_RU.UTF-8"
  LC_PAPER="ru_RU.UTF-8"
  LC_NAME="ru_RU.UTF-8"
  LC_ADDRESS="ru_RU.UTF-8"
  LC_TELEPHONE="ru_RU.UTF-8"
  LC_MEASUREMENT="ru_RU.UTF-8"
  LC_IDENTIFICATION="ru_RU.UTF-8"
  LC_ALL=ru_RU.UTF-8

  locale -a
  C
  C.UTF-8
  en_AG
  en_AG.utf8
  en_AU.utf8
  en_BW.utf8
  en_CA.utf8
  en_DK.utf8
  en_GB.utf8
  en_HK.utf8
  en_IE.utf8
  en_IN
  en_IN.utf8
  en_NG
  en_NG.utf8
  en_NZ.utf8
  en_PH.utf8
  en_SG.utf8
  en_US.utf8
  en_ZA.utf8
  en_ZM
  en_ZM.utf8
  en_ZW.utf8
  POSIX
  ru_RU.utf8
  ru_UA.utf8

  cat /etc/default/locale 
  #  File generated by update-locale
  LANG="ru_RU.UTF-8"
  LANGUAGE="ru:en"
  LC_NUMERIC="ru_RU.UTF-8"
  LC_TIME="ru_RU.UTF-8"
  LC_MONETARY="ru_RU.UTF-8"
  LC_PAPER="ru_RU.UTF-8"
  LC_IDENTIFICATION="ru_RU.UTF-8"
  LC_NAME="ru_RU.UTF-8"
  LC_ADDRESS="ru_RU.UTF-8"
  LC_TELEPHONE="ru_RU.UTF-8"
  LC_MEASUREMENT="ru_RU.UTF-8"

  nano ~/.bashrc
  # ~/.bashrc: executed by bash(1) for non-login shells.
  # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
  # for examples
  #export LC_xxx=C.UTF-8
  export LC_ALL=ru_RU.UTF-8
  ...

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

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


[Touch-packages] [Bug 1792835] Re: Bash completion for Inkscape does not work

2018-12-14 Thread Jamie Strandboge
The ufw bug is being tracking in bug 1775043. Removing that task.

** No longer affects: ufw (Ubuntu)

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

Title:
  Bash completion for Inkscape does not work

Status in apt-xapian-index package in Ubuntu:
  New
Status in cowdancer package in Ubuntu:
  Fix Committed
Status in dpatch package in Ubuntu:
  New
Status in inkscape package in Ubuntu:
  Fix Released
Status in jackd2 package in Ubuntu:
  New

Bug description:
  Bash completion for Inkscape does not work in Ubuntu 18.04. It will
  for example suggest non-svg files.

  The reason seems to be that /usr/share/bash-
  completion/completions/inkscape uses the have() function, which is
  temporarily defined in /usr/share/bash-completion/bash_completion, but
  then unset at the end of that file.

  Workaround: Copy /usr/share/bash-completion/completions/inkscape to
  ~/.local/share/bash-completion/completions/inkscape and remove the
  uses of "have".

  The bash completion for some other commands seem to use have() too,
  e.g. jackd, ufw, cowbuilder, dpatch_edit_patch, and axi-cache, so bash
  completion for these commands will presumably not work either.


  From /usr/share/bash-completion/bash_completion:
  -
  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.
  have()
  {
  unset -v have
  _have $1 && have=yes
  }
  [...]
  unset -f have
  unset have
  -

  From /usr/share/bash-completion/completions/inkscape:
  -
  [...]
  have inkscape &&
  _inkscape()
  {
[...]
  }
  [ "${have:-}" ] && complete -F _inkscape $filenames inkscape
  -


  System information:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy inkscape
  inkscape:
Installed: 0.92.3-1
Candidate: 0.92.3-1
Version table:
   *** 0.92.3-1 500
  500 http://no.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu)
   Status: New => Invalid

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

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
ufw -> gconf2
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
menu: /usr/share/menu
tex-common: texmf-format
gconf2: /usr/share/GConf/gsettings
ufw: /etc/ufw/applications.d
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  ...
  Setting up python3-all-dev (3.6.4-1) ...
  Processing triggers for menu (2.1.47ubuntu1) ...
  Processing triggers for tex-common (6.09) ...
  Building format(s) --all.
This may take some time... done.
  Errors were encountered while processing:
   libc-bin
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Setting up libc-bin (2.26-0ubuntu2) ...
  Press Return to continue, 'q' followed by Return to quit.

  Ubuntu: bionic 18.04

  dpkg:
Installed: 1.19.0.5ubuntu1
Candidate: 1.19.0.5ubuntu1
Version table:
   *** 1.19.0.5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  aptitude:
Installed: 0.8.10-6ubuntu1
Candidate: 0.8.10-6ubuntu1
Version table:
   *** 0.8.10-6ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libc-bin:
Installed: 2.26-0ubuntu2
Candidate: 2.26-0ubuntu2
Version table:
   *** 2.26-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  menu:
Installed: 2.1.47ubuntu1
Candidate: 2.1.47ubuntu1
Version table:
   *** 2.1.47ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  tex-common:
Installed: 6.09
Candidate: 6.09
Version table:
   *** 6.09 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  gconf2:
Installed: 3.2.6-4ubuntu1
Candidate: 3.2.6-4ubuntu1
Version table:
   *** 3.2.6-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  ufw:
Installed: 0.35-5
Candidate: 0.35-5
Version table:
   *** 0.35-5 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  libav-tools:
Installed: 7:3.4.2-1
Candidate: 7:3.4.2-1
Version table:
   *** 7:3.4.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.26-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 16 16:08:12 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2
   libgcc1 1:8-20180208-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (649 days ago)
  InstallationMedia:
   
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
   -- No entries --
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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


[Touch-packages] [Bug 1660040] Re: old-fashioned ufw structure reduces usability

2018-12-14 Thread Jamie Strandboge
*** This bug is a duplicate of bug 910324 ***
https://bugs.launchpad.net/bugs/910324

** This bug has been marked a duplicate of bug 910324
   Add directory support for before.rules and after.rules

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

Title:
  old-fashioned ufw structure reduces usability

Status in ufw package in Ubuntu:
  New

Bug description:
  Hi,

  ufw makes it difficult to deploy firewall rules through management
  systems like puppet, ansible or other scripts.

  ufw has three points where to put rules in:

  before.rules
  user.rules
  after.rules

  
  the ufw command accepts only a very limited sort of rules, and user.rules 
should not be used to deploy files, since user changes would be overwritten. 

  before.rules and after.rules could easily be used for that purpose,
  but then the machine is cut from automated updates through apt, since
  apt refuses (for good reason) to replace modified files in /etc.


  It would be much better to have a directory like /etc/ufw/rules_v4.d ,
  to put the old-fashioned three files into 20_before, 50_user and
  70_after, and to execute all rules in this directory, thus allowing to
  have additional rules in separate files.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Jan 28 16:21:02 2017
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (297 days ago)

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

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


[Touch-packages] [Bug 1509725] Re: Some ICMPv6 packets rejected due to rule ordering

2018-12-14 Thread Jamie Strandboge
*** This bug is a duplicate of bug 1664133 ***
https://bugs.launchpad.net/bugs/1664133

** This bug has been marked a duplicate of bug 1664133
   ipv6 multicast pings don't return

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

Title:
  Some ICMPv6 packets rejected due to rule ordering

Status in ufw package in Ubuntu:
  New

Bug description:
  In the default before6.rules file, the following lines:

  # drop INVALID packets (logs these in loglevel medium and higher)
  -A ufw6-before-input -m conntrack --ctstate INVALID -j ufw6-logging-deny
  -A ufw6-before-input -m conntrack --ctstate INVALID -j DROP

  are present before the ICMPv6 rules. The problem is that this also
  captures echo replies (but, somehow, allows echo requests) and some
  IPv6 routing announcements. If I try to ping ff02::1 to ping all
  devices on the local network, I only get a response from my own
  device.

  Moving those three lines towards the end of the file (after all ICMP
  rules and before the COMMIT) fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ufw 0.34-2
  Uname: Linux 4.3.0-rc5arcot x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Oct 24 18:07:40 2015
  InstallationDate: Installed on 2012-10-19 (1099 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to wily on 2015-02-28 (238 days ago)
  mtime.conffile..etc.ufw.sysctl.conf: 2015-08-08T23:49:55.322401

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

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


[Touch-packages] [Bug 1155250] Re: ufw should error if arguments given to "ufw enable"

2018-12-14 Thread Jamie Strandboge
This was fixed in 0.35.

** Changed in: ufw (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 ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1155250

Title:
  ufw should error if arguments given to "ufw enable"

Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  Consider the following:

  # ufw enable OpenSSH
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  Firewall is active and enabled on system startup

  ...but of course the OpenSSH application profile has not been loaded;
  the word "OpenSSH" was silently ignored.

  It is (IMO) a reasonable user error - the syntax "sounds" like it
  should work.  And the warning message is a great red herring, sigh.

  So, I believe that ufw should check to see if there are other
  arguments specified after single-argument commands, and throw an
  error.

  behavior verified on ubuntu 12.04 Version: 0.31.1-1; i took a quick
  look at the ufw release notes and it does not seem this is addressed
  in any subsequent releases.

  thanks!

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

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


[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

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

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

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

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

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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


[Touch-packages] [Bug 1602834] Re: obsolete conffiles not cleaned up on upgrade

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu)
   Status: New => Triaged

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

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

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
   Status: Triaged

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

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

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

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

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

** Changed in: ufw (Ubuntu Disco)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  Triaged

Bug description:
  Hi,

  the following conffile is marked as obsolete in my dpkg status db

   /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete

  Ufw now ships /usr/share/bash-completion/completions/ufw, so the
  conffile should be removed on upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:19:52 2016
  InstallationDate: Installed on 2011-11-10 (1706 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago)

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

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


[Touch-packages] [Bug 1664133] Re: ipv6 multicast pings don't return

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ufw (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Changed in: ufw (Ubuntu Disco)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ipv6 multicast pings don't return

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

Bug description:
  Hi,
  I have the default settings from Linux Mint 18 for ufw. When I "ping6 
ff02::1%wlp3s0", I get only an answer from my own ip. Duplicates from other 
devices on the net get filtered. It works fine after "sudo ufw disable".

  ufw --version
  ufw 0.35
  Copyright 2008-2015 Canonical Ltd.

  I've attached the output of ip6tables-save.

  There is a similar old and long fixed bug:
  https://bugs.launchpad.net/ufw/+bug/720605

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

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


[Touch-packages] [Bug 1719211] Re: Bad interface name

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

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

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

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

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

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

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  Bad interface name

Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress

Bug description:
  Is there a reason to restrict interface's name in ufw?
  Should ufw accept what iptables accept as iface name?

  I've a vpn with lot of nodes, its iface name contain a '-' so cannot
  use ufw on it.

  I've found the check here and cannot found a reason for it:
  http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300

  thanks

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

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


[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2018-12-14 Thread Michal
OK. I got it. In my case processes starts in similar way /tmp/XXX-XXX...
that's was suspicious after search info about similar cases I found
this:

https://ubuntuforums.org/showthread.php?t=2389313
https://www.reddit.com/r/Addons4Kodi/comments/8eto78/people_using_unofficial_kodi_addon_on_linux/

Please check if ~/.config/autostart/dbus-daemon.desktop exists.

After cleaning ~/.config/autostart/ folder situation is better also i
found suspicious inictl file in ~/.cache/fontconfig

I will check files with ClamAV but this will take some time.

For now CPU usage looks good for me.

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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


[Touch-packages] [Bug 1661809] Re: package ufw (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-12-14 Thread Jamie Strandboge
** Package changed: ufw (Ubuntu) => rpcbind (Ubuntu)

** Summary changed:

- package ufw (not installed) failed to install/upgrade: subprocess installed 
post-removal script returned error exit status 1
+ failed to install/upgrade: subprocess installed post-removal script returned 
error exit status 1

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

Title:
  failed to install/upgrade: subprocess installed post-removal script
  returned error exit status 1

Status in rpcbind package in Ubuntu:
  New

Bug description:
  I purged ufw from the system. systemctl list-unit-files showed UFW
  enabled.

  
  The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   ufw: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Feb  4 00:04:25 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ufw
  Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu)
   Status: Triaged => In Progress

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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


[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt

2018-12-14 Thread Jamie Strandboge
This will be fixed with the new feature for concurrent updates, which is
scheduled for ufw 0.36.

** Changed in: ufw (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

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

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

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

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

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

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

Title:
  ufw errors after ctr+c interupt

Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress

Bug description:
  in ufw.util.get_netfilter_capabilities

  ```
  # Cleanup
  cmd([exe, '-F', chain])
  (rc, out) = cmd([exe, '-X', chain])
  if rc != 0:
  raise OSError(errno.ENOENT, out) # pragma: no cover
  ```

  if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called,
  so every ufw cmd afterwards cause error:

  ```
  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.
  ```

  I think we should catch error and cleanup in a finally statement. 
  Or cleanup related rules before ufw init.

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

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


[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw
   Importance: Undecided => Low

** Changed in: ufw
   Importance: Low => Medium

** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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


[Touch-packages] [Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw
   Importance: Undecided => Medium

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

Title:
  bash completion not working: uses deprecated have()

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  bash completion, defined in /usr/share/bash-
  completion/completions/ufw, doesn't work: the completion is not
  dynamically loaded, because it uses deprecated helper function have().

  According to /usr/share/bash-completions/bash_completion, which
  defines the helper functions:

  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.

  and at the end of the file:

  unset -f have
  unset have

  which means: function have() is not available for usage. The bash
  completion for ufw conditionally defines _ufw and the comspec:

  have ufw &&   


  _ufw()
  ...

  [ "$have" ] && complete -F _ufw ufw

  These should be changed to:

  _have ufw &&  

 
  _ufw()
  ...

  _have ufw && complete -F _ufw ufw

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ufw 0.35-5
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun  4 14:34:11 2018
  InstallationDate: Installed on 2018-04-28 (37 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-12-14 Thread Tony Partridge
Confirmed fixed with live ubuntu, working with gnome-shell
3.28.3-0ubuntu0.18.04.4 from bionic-proposed. Thanks guys, was a pesky
bug.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  In Progress
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xorg-hwe-18.04 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
hwe-18.04/1:7.7+19ubuntu8~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xorg (Ubuntu Bionic) => xorg-hwe-18.04 (Ubuntu
Bionic)

** Changed in: xorg-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  

[Touch-packages] [Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
This was committed to ufw a while ago and will be in the upcoming 0.36,
which I plan to SRU back to bionic.

** Changed in: ufw
   Status: In Progress => Fix Committed

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

Title:
  bash completion not working: uses deprecated have()

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  bash completion, defined in /usr/share/bash-
  completion/completions/ufw, doesn't work: the completion is not
  dynamically loaded, because it uses deprecated helper function have().

  According to /usr/share/bash-completions/bash_completion, which
  defines the helper functions:

  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.

  and at the end of the file:

  unset -f have
  unset have

  which means: function have() is not available for usage. The bash
  completion for ufw conditionally defines _ufw and the comspec:

  have ufw &&   


  _ufw()
  ...

  [ "$have" ] && complete -F _ufw ufw

  These should be changed to:

  _have ufw &&  

 
  _ufw()
  ...

  _have ufw && complete -F _ufw ufw

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ufw 0.35-5
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun  4 14:34:11 2018
  InstallationDate: Installed on 2018-04-28 (37 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1759836] Florian is dope

2018-12-14 Thread ach619
i started this thread the day ubuntu 18 was released, I've tried the work
around. It solved my problem, so I want to thank the original solution
contributor (...forgot which email it was. Read it and implemented it a
while ago). but I also thank you Florian for the clear, concise, well
articulated, up to date description of the work around. Specifically the
line numbers and code diff. much appreciated.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread VanVan
Thanks to craig-jackson if you want to check before compiling your
kernel if you have the same problem that I had, you can check if the
sound can work for a few seconds with the command below :


sudo apt install git
git clone https://github.com/VanVan/check_sound.git
sudo ./check_sound/check_sound

If you can hear a sound from your internal speaker it's good, if not,
compiling a new kernel can still give you sound, depends on your laptop.


When you compile a new kernel, do not forget do to a git pull inside the linux 
folder or you can remove and clone again the repository to have the latest 
commit (hda_codec.h correction):
git clone https://github.com/VanVan/linux.git

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-dummy-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-dummy-
hwe-18.04/1:0.3.8-1build3~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock 

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

2018-12-14 Thread Timo Aaltonen
Hello Damiön, or anyone else affected,

Accepted landscape-client into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/14.12-0ubuntu6.14.04.4 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: landscape-client (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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


[Touch-packages] [Bug 1670291] Please test proposed package

2018-12-14 Thread Timo Aaltonen
Hello Damiön, or anyone else affected,

Accepted landscape-client into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/16.03-0ubuntu2.16.04.5 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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


[Touch-packages] [Bug 1670291] Please test proposed package

2018-12-14 Thread Timo Aaltonen
Hello Damiön, or anyone else affected,

Accepted landscape-client into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/18.01-0ubuntu3.2 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: landscape-client (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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


[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

2018-12-14 Thread Timo Aaltonen
Hello Damiön, or anyone else affected,

Accepted landscape-client into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/18.01-0ubuntu4.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: landscape-client (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-cosmic

** Changed in: landscape-client (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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


[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-12-14 Thread Phil Pemberton
I'm seeing this on an Ubuntu 16.04.5 LTS system running on top of LVM.
In my case, I get:


*** /dev/mapper/wolf-root will be checked for errors at next reboot ***


Having to dig out a 16.04 LTS Server USB stick every time I need to run FSCK is 
extremely inconvenient. It turns an unattended maintenance job into one that 
requires a lot of hand-holding.

Please let me know if there's any information I can provide to get this
fixed.

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

Title:
  fsck not running at all on reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
  that says:

  *** /dev/xvda1 should be checked for errors ***

  I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub before running 'sudo update-grub'. I also verified
  that fsck was present in /boot/grub/grub.cfg afterwards, before
  rebooting the server.

  Surprisingly I was met with the same error message in MOTD when
  logging in. I then ran tune2fs to see when the last check was
  performed and this is the output:

  $ sudo tune2fs -l /dev/xvda1  | grep checked
  Last checked: Wed Sep 12 16:17:00 2018

  I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
  but after another reboot I was still met with the same error message
  and the timestamp for last checked was unchanged.

  I have the same problem on all the servers that was upgraded from
  16.04 to 18.04, but also on a new server installed directly with
  18.04.

  In should be mentioned that the servers are AWS EC2 instances, so I
  have no way of trying to run fsck from a liveusb.

  Another user has reported the same issue here:
  https://ubuntuforums.org/showthread.php?t=2403368

  I'm not quite sure what information is needed, but attached are some
  basic information about the system.

  Please let me know if you need any any other outputs or logs.

  Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1
  LTS (Xubuntu) and it works fine. Seems to be related to the server
  edition.

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

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


[Touch-packages] [Bug 1808415] Re: i dont no

2018-12-14 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
   i dont no

Status in xorg package in Ubuntu:
  New

Bug description:
  plus de son en sortie et la clef bluethoot pas detecter

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: pata_acpi r8169 radeon pata_atiixp wmi
  .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 Dec 13 21:27:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 6310] [1043:101c]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-05-23 (569 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K53BY
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a12e05bc-12f2-4433-9815-2d789360b75c ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53BY
  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.:bvr210:bd05/12/2011:svnASUSTeKComputerInc.:pnK53BY:pvr1.0:rvnASUSTeKComputerInc.:rnK53BY:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53BY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec 13 21:22:15 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread craig jackson
For those following https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel, I
had to do some extra things to get kernel compilation working.

The workaround steps are described here:
https://askubuntu.com/questions/1085411/unable-to-follow-kernel-
buildyourownkernel/1099988. Substitute the kernel version relevant to
you wherever you see "4.18.0"...

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-14 Thread craig jackson
The above worked for (k)ubuntu 18.10.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  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/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-qxl-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-qxl-
hwe-18.04/0.1.5-2build2~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-qxl (Ubuntu Bionic) => xserver-
xorg-video-qxl-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-qxl-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-vmware-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-vmware-
hwe-18.04/1:13.3.0-2build1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-vmware (Ubuntu Bionic) =>
xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a 

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

2018-12-14 Thread Florian Dittmer
Had the same problem on Dell Latitude E6400 laptop using Gentoo Linux
with udev versions newer than udev-233. Disabling Bluetooth in BIOS
solved the issue, however, I need bluetooth. Researching the web
resulted in this page:

https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses-
high-cpu-conflict-with-wifi

Following the instructions mentioned by one user in the comments helped
me to solve the cpu load issue with udev-239 and kernel 4.18.17,  while
Bluetooth still works.

Run the following command:

/lib/systemd/systemd-udevd -D
 
This should print garbage in endless loop containing ".../97-hid2hci.rules:"

If so, edit /lib/udev/rules.d/97-hid2hci.rules

and add

ACTION=="add",

in front of line mentioned by above command.

In my case, I had to change the following lines in 97-hid2hci.rules
from:

ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

to:

ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

And this fixed the issue (after reboot).

Best regards
Florian

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-fbdev-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev-
hwe-18.04/1:0.5.0-1ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-fbdev (Ubuntu Bionic) => xserver-
xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-vesa-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-vesa-
hwe-18.04/1:2.4.0-1~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-vesa (Ubuntu Bionic) => xserver-
xorg-video-vesa-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-vesa-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-nouveau-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau-
hwe-18.04/1:1.0.15-3~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-nouveau (Ubuntu Bionic) =>
xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-ati-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati-
hwe-18.04/1:18.1.0-1~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xserver-xorg-video-ati (Ubuntu Bionic) => xserver-
xorg-video-ati-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-input-synaptics-hwe-18.04 into bionic-proposed.
The package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics-
hwe-18.04/1.9.1-1ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl source package in Bionic:
  New
Status in xserver-xorg-video-vesa source package in Bionic:
  New
Status in xserver-xorg-video-vmware source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

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

-- 
Mailing list: 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-input-libinput-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput-
hwe-18.04/0.28.1-1~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-qxl source package in Bionic:
  New
Status in xserver-xorg-video-vesa source package in Bionic:
  New
Status in xserver-xorg-video-vmware source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

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

-- 
Mailing list: 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-amdgpu-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu-
hwe-18.04/18.1.0-1~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Package changed: xf86-input-wacom (Ubuntu Bionic) => xf86-input-
wacom-hwe-18.04 (Ubuntu Bionic)

** Changed in: xf86-input-wacom-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Package changed: xserver-xorg-input-evdev (Ubuntu Bionic) => xserver-
xorg-input-evdev-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-input-evdev-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Package changed: xserver-xorg-input-joystick (Ubuntu Bionic) =>
xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Package changed: xserver-xorg-input-libinput (Ubuntu Bionic) =>
xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Package changed: xserver-xorg-input-synaptics (Ubuntu Bionic) =>
xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Package changed: xserver-xorg-video-amdgpu (Ubuntu Bionic) =>
xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Committed
Status in 

[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-input-joystick-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-input-joystick-
hwe-18.04/1:1.6.3-1build1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom source package in Bionic:
  New
Status in xorg source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in xserver-xorg-input-evdev source package in Bionic:
  New
Status in xserver-xorg-input-joystick source package in Bionic:
  New
Status in xserver-xorg-input-libinput source package in Bionic:
  New
Status in xserver-xorg-input-synaptics source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu source package in Bionic:
  New
Status in xserver-xorg-video-ati source package in Bionic:
  New
Status in xserver-xorg-video-fbdev source package in Bionic:
  New
Status in xserver-xorg-video-nouveau source package in Bionic:
  New
Status in xserver-xorg-video-qxl source package in Bionic:
  New
Status in xserver-xorg-video-vesa source package in Bionic:
  New
Status in xserver-xorg-video-vmware source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-input-evdev-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-input-evdev-
hwe-18.04/1:2.10.6-1~18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom source package in Bionic:
  New
Status in xorg source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in xserver-xorg-input-evdev source package in Bionic:
  New
Status in xserver-xorg-input-joystick source package in Bionic:
  New
Status in xserver-xorg-input-libinput source package in Bionic:
  New
Status in xserver-xorg-input-synaptics source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu source package in Bionic:
  New
Status in xserver-xorg-video-ati source package in Bionic:
  New
Status in xserver-xorg-video-fbdev source package in Bionic:
  New
Status in xserver-xorg-video-nouveau source package in Bionic:
  New
Status in xserver-xorg-video-qxl source package in Bionic:
  New
Status in xserver-xorg-video-vesa source package in Bionic:
  New
Status in xserver-xorg-video-vmware source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

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

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


[Touch-packages] [Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xf86-input-wacom-hwe-18.04 into bionic-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/xf86-input-wacom-
hwe-18.04/1:0.36.1-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in wayland source package in Bionic:
  Fix Committed
Status in xf86-input-wacom source package in Bionic:
  New
Status in xorg source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in xserver-xorg-input-evdev source package in Bionic:
  New
Status in xserver-xorg-input-joystick source package in Bionic:
  New
Status in xserver-xorg-input-libinput source package in Bionic:
  New
Status in xserver-xorg-input-synaptics source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu source package in Bionic:
  New
Status in xserver-xorg-video-ati source package in Bionic:
  New
Status in xserver-xorg-video-fbdev source package in Bionic:
  New
Status in xserver-xorg-video-nouveau source package in Bionic:
  New
Status in xserver-xorg-video-qxl source package in Bionic:
  New
Status in xserver-xorg-video-vesa source package in Bionic:
  New
Status in xserver-xorg-video-vmware source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

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

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


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

2018-12-14 Thread Matt Caswell
I made the change to /lib/ufw/ufw-init as requested and confirmed that
after reboot I was still hitting the issue (Ubuntu 18.04.1 LTS):

$ sudo ufw status
Status: inactive

Attached is the requested journalctl output.

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/551/+files/journalctl.log

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Incomplete
Status in ufw package in Ubuntu:
  New
Status in ufw source package in Xenial:
  New
Status in ufw source package in Bionic:
  New
Status in ufw source package in Cosmic:
  New

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

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

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

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

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


[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-12-14 Thread Massimo S.
I had updated my laptop so to Ubuntu 18.10 64bit and the message is
still present for me.

I see the messages (Could not find key with description...) in dmesg
output but all works fine.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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


[Touch-packages] [Bug 1405001] Re: Gstreamer 1.0 has missing core elements

2018-12-14 Thread Meghdad
^ that solution worked for me.

I can't believe that such a basic system functionality can get messed up
by user config files!

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

Title:
  Gstreamer 1.0 has missing core elements

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I wanted to test gstreamer's pipeline functions in command line using
  Jono Bacon's tutorial. I thus ran

  gst-launch-1.0 filesrc location=mysong.mp3  ! decodebin !
  audioconvert ! alsasink

  And this error came up:

 ERROR: pipeline could not be constructed: no element "filesrc".

  I dug a little through the google searches, and using gstreamer-
  inspect1.0, I was able to list all the installed plugins. Amazingly,
  *none of the coreelements plugins are present*.

  Is there a way to fix this? Is there a packet that might have been
  forgotten in the 13.10-14.04 update process?

  PS: I have troubles with *all* the gstreamer-dependent application on
  my 14.04 install so this is probably related.

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

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


[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)

2018-12-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/debian-installer/trusty-proposed

** Branch linked: lp:~ubuntu-core-dev/debian-installer/xenial-proposed

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

Title:
  installer stock images fail to validate any HTTPS certificates (ca-
  certificates missing)

Status in debian-installer:
  Fix Released
Status in ca-certificates package in Ubuntu:
  Invalid
Status in debian-installer package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Committed
Status in debian-installer source package in Trusty:
  Fix Committed
Status in ca-certificates source package in Xenial:
  Fix Committed
Status in debian-installer source package in Xenial:
  Fix Committed
Status in ca-certificates source package in Bionic:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in ca-certificates source package in Cosmic:
  Invalid
Status in debian-installer source package in Cosmic:
  Fix Released
Status in ca-certificates source package in Disco:
  Invalid
Status in debian-installer source package in Disco:
  Fix Released
Status in debian-installer package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The installer stock images fail to validate any HTTPS
     certificates because ca-certificates is not available
     in the installer environment.

   * This causes wget/download errors for preseed files on
     HTTPS servers (or HTTP servers that redirect to HTTPS,
     which are increasingly common nowadays - e.g., GitHub)
     and theoretically any other files that are downloaded
     with d-i-utils/fetch-url/wget.

   * The fix is to ship ca-certificates-udeb in installer
     stock images.

   * Debian already ships ca-certificate-udeb in the stock
     installer images; the fix is applied since Jan 2017.
     (reference: Debian Bug #842040 / d-i commit 2f00c51a [1])

  [Test Case]

   * In the installer shell:

     ~ # wget http://github.com  # or https://github.com

     - FAIL if ca-certificates-udeb is missing:
   "ERROR: cannot verify github.com's certificate, <...>'

     - PASS if ca-certificates-udeb is available
   "Saving to: 'index.html'"

   * Test steps with virt-install and netboot images
     are provided in the comments, for each release.

  [Regression Potential]

   * Low. This just adds the ca-certificates files in
     /etc/ssl/certs and symlink in /usr/lib/ssl/certs,
     so only tools looking for that would be affected.

   * Apparently only wget checks for/uses those files,
     and the difference in behavior is download errors
     no longer occur.

  [Notes]

   * The ca-certificates-udeb is not currently present
     in the Ubuntu 'main' component, but in 'universe',
     despite the normal deb being in 'main'.

     However, when rebuilding in a PPA it goes into
     'main' accordingly, and can be used by default
     by debian-installer (otherwise, UDEB_COMPONENTS
     has to be modified to include universe/d-i).

   * So this fix includes a no-change-rebuild for the
     ca-certificates package, in order to publish the
     udeb in the archive (at least in PPA for testing).

     Hopefully that can be sorted out for this fix
     to work out.

   * The ca-certificates and debian-installer builds
     have been done in a PPA using all architectures,
     and testing has been done with the amd64 images.

   * This fix is requested for Bionic, Cosmic, Disco
 at least.

   * The fix for Trusty and Xenial needed a little
     bit more work to build/ship the (new) udeb.
 (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])

     It would be good to have them too if at all possible.

  [1] 
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
  [2] 
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4

  [Debugging]

  For debugging purposes, one can install strace-udeb in the installer
  to verify wget's stat() calls to /usr/lib/ssl/certs.

  ~ # anna-install strace-udeb

  ~ # strace -e stat wget -O- https://github.com >/dev/null
  ...
  Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=20, ...}) = 0
  140.82.118.3, 140.82.118.4
  Connecting to github.com|140.82.118.3|:443... connected.
  stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2 
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
    Unable to locally verify the issuer's authority.
  To connect to 

[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)

2018-12-14 Thread Launchpad Bug Tracker
This bug was fixed in the package debian-installer - 20101020ubuntu557.1

---
debian-installer (20101020ubuntu557.1) cosmic; urgency=medium

  * build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS
without d-i/allow_unauthenticated_ssl in stock initramfs image
as in Debian. (LP: #1807023)

 -- Mauricio Faria de Oliveira   Mon, 26 Nov 2018
16:49:46 -0200

** Changed in: debian-installer (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  installer stock images fail to validate any HTTPS certificates (ca-
  certificates missing)

Status in debian-installer:
  Fix Released
Status in ca-certificates package in Ubuntu:
  Invalid
Status in debian-installer package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Committed
Status in debian-installer source package in Trusty:
  Fix Committed
Status in ca-certificates source package in Xenial:
  Fix Committed
Status in debian-installer source package in Xenial:
  Fix Committed
Status in ca-certificates source package in Bionic:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in ca-certificates source package in Cosmic:
  Invalid
Status in debian-installer source package in Cosmic:
  Fix Released
Status in ca-certificates source package in Disco:
  Invalid
Status in debian-installer source package in Disco:
  Fix Released
Status in debian-installer package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The installer stock images fail to validate any HTTPS
     certificates because ca-certificates is not available
     in the installer environment.

   * This causes wget/download errors for preseed files on
     HTTPS servers (or HTTP servers that redirect to HTTPS,
     which are increasingly common nowadays - e.g., GitHub)
     and theoretically any other files that are downloaded
     with d-i-utils/fetch-url/wget.

   * The fix is to ship ca-certificates-udeb in installer
     stock images.

   * Debian already ships ca-certificate-udeb in the stock
     installer images; the fix is applied since Jan 2017.
     (reference: Debian Bug #842040 / d-i commit 2f00c51a [1])

  [Test Case]

   * In the installer shell:

     ~ # wget http://github.com  # or https://github.com

     - FAIL if ca-certificates-udeb is missing:
   "ERROR: cannot verify github.com's certificate, <...>'

     - PASS if ca-certificates-udeb is available
   "Saving to: 'index.html'"

   * Test steps with virt-install and netboot images
     are provided in the comments, for each release.

  [Regression Potential]

   * Low. This just adds the ca-certificates files in
     /etc/ssl/certs and symlink in /usr/lib/ssl/certs,
     so only tools looking for that would be affected.

   * Apparently only wget checks for/uses those files,
     and the difference in behavior is download errors
     no longer occur.

  [Notes]

   * The ca-certificates-udeb is not currently present
     in the Ubuntu 'main' component, but in 'universe',
     despite the normal deb being in 'main'.

     However, when rebuilding in a PPA it goes into
     'main' accordingly, and can be used by default
     by debian-installer (otherwise, UDEB_COMPONENTS
     has to be modified to include universe/d-i).

   * So this fix includes a no-change-rebuild for the
     ca-certificates package, in order to publish the
     udeb in the archive (at least in PPA for testing).

     Hopefully that can be sorted out for this fix
     to work out.

   * The ca-certificates and debian-installer builds
     have been done in a PPA using all architectures,
     and testing has been done with the amd64 images.

   * This fix is requested for Bionic, Cosmic, Disco
 at least.

   * The fix for Trusty and Xenial needed a little
     bit more work to build/ship the (new) udeb.
 (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])

     It would be good to have them too if at all possible.

  [1] 
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
  [2] 
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4

  [Debugging]

  For debugging purposes, one can install strace-udeb in the installer
  to verify wget's stat() calls to /usr/lib/ssl/certs.

  ~ # anna-install strace-udeb

  ~ # strace -e stat wget -O- https://github.com >/dev/null
  ...
  Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=20, ...}) = 0
  140.82.118.3, 140.82.118.4
  Connecting to github.com|140.82.118.3|:443... connected.
  stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file 

[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)

2018-12-14 Thread Launchpad Bug Tracker
This bug was fixed in the package debian-installer - 20101020ubuntu543.4

---
debian-installer (20101020ubuntu543.4) bionic; urgency=medium

  * build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS
without d-i/allow_unauthenticated_ssl in stock initramfs image
as in Debian. (LP: #1807023)

 -- Mauricio Faria de Oliveira   Mon, 26 Nov 2018
16:49:46 -0200

** Changed in: debian-installer (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  installer stock images fail to validate any HTTPS certificates (ca-
  certificates missing)

Status in debian-installer:
  Fix Released
Status in ca-certificates package in Ubuntu:
  Invalid
Status in debian-installer package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Committed
Status in debian-installer source package in Trusty:
  Fix Committed
Status in ca-certificates source package in Xenial:
  Fix Committed
Status in debian-installer source package in Xenial:
  Fix Committed
Status in ca-certificates source package in Bionic:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in ca-certificates source package in Cosmic:
  Invalid
Status in debian-installer source package in Cosmic:
  Fix Released
Status in ca-certificates source package in Disco:
  Invalid
Status in debian-installer source package in Disco:
  Fix Released
Status in debian-installer package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The installer stock images fail to validate any HTTPS
     certificates because ca-certificates is not available
     in the installer environment.

   * This causes wget/download errors for preseed files on
     HTTPS servers (or HTTP servers that redirect to HTTPS,
     which are increasingly common nowadays - e.g., GitHub)
     and theoretically any other files that are downloaded
     with d-i-utils/fetch-url/wget.

   * The fix is to ship ca-certificates-udeb in installer
     stock images.

   * Debian already ships ca-certificate-udeb in the stock
     installer images; the fix is applied since Jan 2017.
     (reference: Debian Bug #842040 / d-i commit 2f00c51a [1])

  [Test Case]

   * In the installer shell:

     ~ # wget http://github.com  # or https://github.com

     - FAIL if ca-certificates-udeb is missing:
   "ERROR: cannot verify github.com's certificate, <...>'

     - PASS if ca-certificates-udeb is available
   "Saving to: 'index.html'"

   * Test steps with virt-install and netboot images
     are provided in the comments, for each release.

  [Regression Potential]

   * Low. This just adds the ca-certificates files in
     /etc/ssl/certs and symlink in /usr/lib/ssl/certs,
     so only tools looking for that would be affected.

   * Apparently only wget checks for/uses those files,
     and the difference in behavior is download errors
     no longer occur.

  [Notes]

   * The ca-certificates-udeb is not currently present
     in the Ubuntu 'main' component, but in 'universe',
     despite the normal deb being in 'main'.

     However, when rebuilding in a PPA it goes into
     'main' accordingly, and can be used by default
     by debian-installer (otherwise, UDEB_COMPONENTS
     has to be modified to include universe/d-i).

   * So this fix includes a no-change-rebuild for the
     ca-certificates package, in order to publish the
     udeb in the archive (at least in PPA for testing).

     Hopefully that can be sorted out for this fix
     to work out.

   * The ca-certificates and debian-installer builds
     have been done in a PPA using all architectures,
     and testing has been done with the amd64 images.

   * This fix is requested for Bionic, Cosmic, Disco
 at least.

   * The fix for Trusty and Xenial needed a little
     bit more work to build/ship the (new) udeb.
 (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])

     It would be good to have them too if at all possible.

  [1] 
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
  [2] 
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4

  [Debugging]

  For debugging purposes, one can install strace-udeb in the installer
  to verify wget's stat() calls to /usr/lib/ssl/certs.

  ~ # anna-install strace-udeb

  ~ # strace -e stat wget -O- https://github.com >/dev/null
  ...
  Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=20, ...}) = 0
  140.82.118.3, 140.82.118.4
  Connecting to github.com|140.82.118.3|:443... connected.
  stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file 

[Touch-packages] [Bug 1807023] Update Released

2018-12-14 Thread Adam Conrad
The verification of the Stable Release Update for debian-installer has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  installer stock images fail to validate any HTTPS certificates (ca-
  certificates missing)

Status in debian-installer:
  Fix Released
Status in ca-certificates package in Ubuntu:
  Invalid
Status in debian-installer package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Committed
Status in debian-installer source package in Trusty:
  Fix Committed
Status in ca-certificates source package in Xenial:
  Fix Committed
Status in debian-installer source package in Xenial:
  Fix Committed
Status in ca-certificates source package in Bionic:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in ca-certificates source package in Cosmic:
  Invalid
Status in debian-installer source package in Cosmic:
  Fix Committed
Status in ca-certificates source package in Disco:
  Invalid
Status in debian-installer source package in Disco:
  Fix Released
Status in debian-installer package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The installer stock images fail to validate any HTTPS
     certificates because ca-certificates is not available
     in the installer environment.

   * This causes wget/download errors for preseed files on
     HTTPS servers (or HTTP servers that redirect to HTTPS,
     which are increasingly common nowadays - e.g., GitHub)
     and theoretically any other files that are downloaded
     with d-i-utils/fetch-url/wget.

   * The fix is to ship ca-certificates-udeb in installer
     stock images.

   * Debian already ships ca-certificate-udeb in the stock
     installer images; the fix is applied since Jan 2017.
     (reference: Debian Bug #842040 / d-i commit 2f00c51a [1])

  [Test Case]

   * In the installer shell:

     ~ # wget http://github.com  # or https://github.com

     - FAIL if ca-certificates-udeb is missing:
   "ERROR: cannot verify github.com's certificate, <...>'

     - PASS if ca-certificates-udeb is available
   "Saving to: 'index.html'"

   * Test steps with virt-install and netboot images
     are provided in the comments, for each release.

  [Regression Potential]

   * Low. This just adds the ca-certificates files in
     /etc/ssl/certs and symlink in /usr/lib/ssl/certs,
     so only tools looking for that would be affected.

   * Apparently only wget checks for/uses those files,
     and the difference in behavior is download errors
     no longer occur.

  [Notes]

   * The ca-certificates-udeb is not currently present
     in the Ubuntu 'main' component, but in 'universe',
     despite the normal deb being in 'main'.

     However, when rebuilding in a PPA it goes into
     'main' accordingly, and can be used by default
     by debian-installer (otherwise, UDEB_COMPONENTS
     has to be modified to include universe/d-i).

   * So this fix includes a no-change-rebuild for the
     ca-certificates package, in order to publish the
     udeb in the archive (at least in PPA for testing).

     Hopefully that can be sorted out for this fix
     to work out.

   * The ca-certificates and debian-installer builds
     have been done in a PPA using all architectures,
     and testing has been done with the amd64 images.

   * This fix is requested for Bionic, Cosmic, Disco
 at least.

   * The fix for Trusty and Xenial needed a little
     bit more work to build/ship the (new) udeb.
 (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])

     It would be good to have them too if at all possible.

  [1] 
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
  [2] 
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4

  [Debugging]

  For debugging purposes, one can install strace-udeb in the installer
  to verify wget's stat() calls to /usr/lib/ssl/certs.

  ~ # anna-install strace-udeb

  ~ # strace -e stat wget -O- https://github.com >/dev/null
  ...
  Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=20, ...}) = 0
  140.82.118.3, 140.82.118.4
  Connecting to github.com|140.82.118.3|:443... connected.
  stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or 

[Touch-packages] [Bug 401823]

2018-12-14 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/380.

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

Title:
  Gdk-WARNING **: XID collision, trouble ahead

Status in Chromium Browser:
  Invalid
Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Expired
Status in xlibs:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-3.5 package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in firefox source package in Lucid:
  Invalid
Status in firefox-3.5 source package in Lucid:
  Invalid
Status in gtk+2.0 source package in Lucid:
  Invalid
Status in firefox source package in Karmic:
  Invalid
Status in firefox-3.5 source package in Karmic:
  Won't Fix
Status in gtk+2.0 source package in Karmic:
  Fix Released

Bug description:
  karmic testing

  in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble 
ahead
  previously, have had this one: (nautilus:3572):
   GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' 
failed (bug report 401822)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions

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


[Touch-packages] [Bug 401823]

2018-12-14 Thread Jeremy Huddleston
This seems more like a server issue.  I think it could easily be possible for 
the server to guarantee that XIDs are not reused within a certain time period 
since it issued a DestroyNotify.  That won't guarantee that clients are happy, 
but it can certainly help.  We just need to store a timestamp of the time the 
XID was destroyed and if the head of the recycle queue is too recent, we 
allocate a new XID rather than recycling.

Tracking for 1.12, but I'd consider this for 1.11.x if the change is simple 
enough.

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

Title:
  Gdk-WARNING **: XID collision, trouble ahead

Status in Chromium Browser:
  Invalid
Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Expired
Status in xlibs:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-3.5 package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in firefox source package in Lucid:
  Invalid
Status in firefox-3.5 source package in Lucid:
  Invalid
Status in gtk+2.0 source package in Lucid:
  Invalid
Status in firefox source package in Karmic:
  Invalid
Status in firefox-3.5 source package in Karmic:
  Won't Fix
Status in gtk+2.0 source package in Karmic:
  Fix Released

Bug description:
  karmic testing

  in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble 
ahead
  previously, have had this one: (nautilus:3572):
   GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' 
failed (bug report 401822)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions

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


  1   2   >