date:20190213

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

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

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

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

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

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

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 1814613] Re: qmlscene -style material file.qml says "QApplication: invalid style override passed"

2019-02-13 Thread jimav

Upstream bug: https://bugreports.qt.io/browse/QTBUG-73818

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

Title:
  qmlscene -style material file.qml says "QApplication: invalid style
  override passed"

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

Bug description:
  qmlscene -qt=5 -style material file.qml
  prints
QApplication: invalid style override passed, ignoring it.
  on the terminal.

  This does not happen when using the environment variable method, e.g.
QT_QUICK_CONTROLS_STYLE=material qmlscene -qt=5 file.qml

  The documentation for how this is supposed to work is at

https://doc.qt.io/qt-5/qtquickcontrols2-styles.html#using-styles-in-qt-quick-controls-2

  I'm reporting this to ubuntu because it might be due to packaging or
  patching done for Ubuntu.  I can not conveniently try a pristine
  upstream version of Qt, so hoping the Qt Ubuntu maintainer can quickly
  determine if this is an upstream bug or not.

  I'll attach a trivial test file which demonstrates the problem

  STEPS TO REPRODUCE:
qmlscene -style material test.qml  # test.qml attached

  ACTUAL RESULTS:
Prints warning about invalid style on the terminal

  EXPECTED RESULTS:
Silent obedience

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

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

[Touch-packages] [Bug 1598814] Re: tracker-miner-fs syslog spam: Could not execute sparql

2019-02-13 Thread bizmate

Almost one year and zillion of logs entries later, has anyone got any
clue if this will be fixed?

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

Title:
  tracker-miner-fs syslog spam: Could not execute sparql

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I noticed tracker-miner-fs spamming syslog on every reboot.

  Because there are too many messages i created a github gist at
  https://gist.github.com/CrazyLemon/14a54c58efcd0839a4e990a49da9b303

  As you can see thats a lot of messages.

  I'm on Ubuntu 16.04 with latest updates.
  ii  tracker-miner-fs 1.6.2-0ubuntu1amd64  
   metadata database, indexer and search tool - filesystem 
indexer

  This kind of syslog spamming has been happening at least since june
  27th '16.

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

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

[Touch-packages] [Bug 1732530] Re: Dejadup is not working b/c duplicity is not installed

2019-02-13 Thread handsome_feng

** Changed in: ubuntukylin-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Dejadup is not working b/c duplicity is not installed

Status in ubuntu-mate:
  Invalid
Status in deja-dup package in Ubuntu:
  Won't Fix
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in ubuntukylin-meta package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu Mate 17.10

  Dejadup is not working b/c duplicity is not installed. After a manual
  install, Deja-Dup works as expected.

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

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

[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

Deleting seems only required if the migration fail. We are going to
update ews, maybe you can keep your system is the buggy state and test
if that update resolves the problem for you?

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

** Changed in: evolution-data-server (Ubuntu)
   Status: New => In Progress

** Package changed: evolution-data-server (Ubuntu) => evolution-ews
(Ubuntu)

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-ews package in Ubuntu:
  In Progress

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

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

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

2019-02-13 Thread Jeremy Bicha

** Changed in: gnome-online-accounts (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

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

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

[Touch-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo

2019-02-13 Thread Doug McMahon

Is a newer intel-vaapi-driver package planed? 
(- currently in Debian Sid & does fix the issue in a wayland session..

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

Title:
  i965_drv_video.so doesn't load any more if a Wayland server is present
  [failed to resolve wl_drm_interface(): /lib/x86_64-linux-
  gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface]

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Fix Released

Bug description:
  If a Wayland server is present (anywhere on the system including even
  the gdm3 login screen) then i965_drv_video.so fails to initialize:

  $ vainfo 
  libva info: VA-API version 1.3.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_2
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  $ mpv bbb_sunflower_2160p_60fps_normal.mp4 
  Playing: bbb_sunflower_2160p_60fps_normal.mp4
   (+) Video --vid=1 (*) (h264 3840x2160 60.000fps)
   (+) Audio --aid=1 (*) (mp3 2ch 48000Hz)
   Audio --aid=2 (*) (ac3 6ch 48000Hz)
  File tags:
   Artist: Blender Foundation 2008, Janus Bager Kristensen 2013
   Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net
   Composer: Sacha Goedegebure
   Genre: Animation
   Title: Big Buck Bunny, Sunflower version
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

  Meanwhile, it continues to work after you have logged into a Xorg
  session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: i965-va-driver 2.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  Date: Thu Jan 24 16:54:21 2019
  InstallationDate: Installed on 2018-12-04 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco

The pointed commit is in 2.32 (see
https://sourceware.org/bugzilla/show_bug.cgi?id=23919 for details) but
that seems not enough since the disco-proposed version seems to not fix
the issue from local testing

** Bug watch added: Sourceware.org Bugzilla #23919
   https://sourceware.org/bugzilla/show_bug.cgi?id=23919

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco

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

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco

** Changed in: binutils (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => 
(unassigned)

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

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2019-02-13 Thread Jason Cecil

The author discusses the drawbacks here: https://github.com/jonathanio
/update-systemd-resolved (one can still leak under certain
circumstances, and we shouldn't only be concerned with the minority who
realize this is even happening/a problem and who can hack together a
workaround themselves). Not that you implied that by sharing your
solution; I'm just speaking generally.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-13 Thread Jill Manfield

Dell OEM image with updated kernel has the qca\qca6174 fix.  I reloaded
the dell image and have not been able to reproduce this issue with LE BT
mouses.  I will let it run and confirm.  So it looks like the issue is
just with the generic image not dell image.  non-oem.

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

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:748157 acl:263 sco:0 events:22281 errors:0
    TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

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

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

[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)

2019-02-13 Thread Khurshid Alam

** Merge proposal linked:
   
https://code.launchpad.net/~khurshid-alam/ubuntu/+source/gnome-session/+git/gnome-session/+merge/363153

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

Title:
  Use nemo-desktop to draw desktop icons under Unity (Disco)

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have
  the desktop any more. The alternate options are to use caja-desktop or
  nemo-desktop keeping nautilus default file manger for now. Since nemo-
  desktop does not require any extensive patching it is easy to use
  under unity.

  Nemo-desktop will only draw the icons, not the background. In absence of
  nautilus unity-settings-daemon draws the background, so nothing to do in 
u-s-d.

  There are few small patches (nemo action files) required from nemo. 
@fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship 
  these action files ourselves as recommended by upstream. Budgie is doing the 
same.
  
https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions

  
  Since nautilus still be default file-manager we disable auto-mount with nemo 
and various other cinnamon/nemo option in ubuntu-settings.gsettings-override

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

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

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  Confirmed
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

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

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  Confirmed
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco

2019-02-13 Thread Brian Murray

An example of apport's behavior in this situation can be found in
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1815703.

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco

2019-02-13 Thread Brian Murray

The retracers do not treat this as a failure because apport returns 0
when retracing the crash and that's because gdb also returns 0 as I
believe this is just a warning from gdb. That being said there is no
record of this failure in the retracers and it would not have been
noticed if not for seb128, so there is some room for improvement in how
the retracers / apport handle this situation.

** Also affects: apport
   Importance: Undecided
   Status: New

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in Apport:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

2019-02-13 Thread Sergio Callegari

Hi Dmitry,

thanks for your message and the work as volunteers on Qt packaging.
My message was merely to know if there was any need for a specific bug item
about the backporting and it is great to hear that you were already planning
the backport!
Also, great to hear that 19.04 is going to get the Qt LTS.

Reproducing the duplex issue is very easy.

1) Install a printer that can duplex and configure it to do duplex with
long-edge binding from the printer setup dialog.

2) Open a PDF with okular, and open the print dialog. Select the printer
above.

3) Press the "Options" button to enlarge the dialog to also present the
options. Select the "options" tab, right of "copies". Verify that Duplex
Printing is preset to "None"

This is wrong, because the printer was configured to do duplex with
long-edge binding.

4) Print and close okular.

5) Reopen okular (with the same or another PDF file). Open again the
print dialog and select the same printer.

6) Redo 3). Again see that Duplex Printing is preset to "None", instead
of being at the default or at the previously used setup.

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

Title:
qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Bionic:
New
Status in qtbase-opensource-src source package in Cosmic:
New

Bug description:
All kde applications shipped with ubuntu and particularly kubuntu
bionic print via the qt print dialog, that, unfortunately, does not
seem to respect the defaults set for the printer.

Specifically, every time one starts to print the "duplex" option gets
reset to "none" even for those printers that were configured for "long
edge" duplex by default.

This may lead to a huge *waste of paper*: people print, expecting the
duplex, do not get it, throw away the printout and reprint, for a
total of 3 times the paper usage if the print dialog respected the
default.

See also https://bugs.kde.org/show_bug.cgi?id=395150

As a final comment and in general, I think that Bionic should be
updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
possible (at least via a kubuntu ppa). The QT 5 print dialog has
always been extremely poor, with no possibility to provide information
about things like print quality and resolution, paper type, stapling
(for printers supporting it), etc. Now, QT 5.11 has finally a better
print dialog and it would be great if the bionic users could use it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
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.2
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jun 11 10:23:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1641 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
SourcePackage: qtbase-opensource-src
UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

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

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

2019-02-13 Thread Andrea Azzarone

** Merge proposal linked:
   
https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-online-accounts/+git/gnome-online-accounts/+merge/363144

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

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

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

[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-02-13 Thread Xavier Bestel

The bug was apparently a dupe of 
https://gitlab.gnome.org/GNOME/evolution-ews/issues/18 and should be fixed in 
"3.30.2+".  
However if I understood correctly if I already have a crashing addressbook, 
even with the bugfix it will keep on crashing unless I manually delete the 
cache file buried somewhere in $HOME/.cache/evolution/ - which is not very 
user-friendly ...

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+subscriptions

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

2019-02-13 Thread Andrea Azzarone

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => In Progress

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

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

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

[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)

This bug was fixed in the package ubuntu-themes - 19.04-0ubuntu1

---
ubuntu-themes (19.04-0ubuntu1) disco; urgency=medium

  [ Khurshid Alam ]
  * Don't use icon hover bg color on nemo desktop (LP: #1814506)

 -- Didier Roche   Wed, 13 Feb 2019 15:45:56 +0100

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Fix Released

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

Title:
  Use nemo-desktop to draw desktop icons under Unity (Disco)

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have
  the desktop any more. The alternate options are to use caja-desktop or
  nemo-desktop keeping nautilus default file manger for now. Since nemo-
  desktop does not require any extensive patching it is easy to use
  under unity.

  Nemo-desktop will only draw the icons, not the background. In absence of
  nautilus unity-settings-daemon draws the background, so nothing to do in 
u-s-d.

  There are few small patches (nemo action files) required from nemo. 
@fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship 
  these action files ourselves as recommended by upstream. Budgie is doing the 
same.
  
https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions

  
  Since nautilus still be default file-manager we disable auto-mount with nemo 
and various other cinnamon/nemo option in ubuntu-settings.gsettings-override

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

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

[Touch-packages] [Bug 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink

2019-02-13 Thread cement_head

Okay, my mistake...

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

Title:
  The last MESA updates (02/07/19) corrupted output to DisplayLink

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Prior to Thursday's "update" from Bionic-Proposed, the MESA was
  working fine; afterwards, gameplay on STEAM has become choppy and
  staccato; secondary display via a USB-C through DisplayPort UD3900
  (Pluggable) is completely corrupted. See attached picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Feb 11 16:50:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:1323]
  InstallationDate: Installed on 2019-01-15 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp3-c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: galp3-c
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: galp3-c
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2019-02-13 Thread dlotton

For those using OpenVPN, I discovered that there is a package named
'openvpn-systemd-resolvd' that finally resolved this issue for me.
Here's the synopsis for the package in the repo...

"This is a helper script designed to integrate OpenVPN with the
systemd-resolved service via DBus instead of trying to override
/etc/resolv.conf, or manipulate systemd-networkd configuration files.

Since systemd-229, the systemd-resolved service has an API available via DBus
which allows directly setting the DNS configuration for a link. This script
makes use of busctl from systemd to send DBus messages to systemd-resolved to
update the DNS for the link created by OpenVPN."

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink

2019-02-13 Thread Timo Aaltonen

that's the HWE kernel, not 4.15

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

Title:
  The last MESA updates (02/07/19) corrupted output to DisplayLink

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Prior to Thursday's "update" from Bionic-Proposed, the MESA was
  working fine; afterwards, gameplay on STEAM has become choppy and
  staccato; secondary display via a USB-C through DisplayPort UD3900
  (Pluggable) is completely corrupted. See attached picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Feb 11 16:50:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:1323]
  InstallationDate: Installed on 2019-01-15 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp3-c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: galp3-c
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: galp3-c
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-13 Thread Dave Chiluk

I uploaded the changes to disco this morning.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  In Progress

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1815774] [NEW] binutils 2.32 update breaks debug symbols in disco

Public bug reported:

Recently retracing started failing in disco, that seems to be due to the
binutils 2.32 update

example

$ gdb gnome-control-center
...
Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
(no debugging symbols found)...done.


Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

** Affects: binutils (Ubuntu)
 Importance: High
 Assignee: Canonical Foundations Team (canonical-foundations)
 Status: New


** Tags: rls-dd-incoming

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

Title:
  binutils 2.32 update breaks debug symbols in disco

Status in binutils package in Ubuntu:
  New

Bug description:
  Recently retracing started failing in disco, that seems to be due to
  the binutils 2.32 update

  example

  $ gdb gnome-control-center
  ...
  Reading symbols from gnome-control-center...BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges
  BFD: 
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: 
unable to initialize decompress status for section .debug_aranges

  warning: File 
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has 
no build-id, file skipped
  (no debugging symbols found)...done.

  
  Rebuilding the package with binutils 2.31 installed fixes the issue. Googling 
for the warning lead to an arch bug pointing out that upstream commit as fixing 
the issue
  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae

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

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

[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)

** Branch linked: lp:ubuntu-themes

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

Title:
  Use nemo-desktop to draw desktop icons under Unity (Disco)

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have
  the desktop any more. The alternate options are to use caja-desktop or
  nemo-desktop keeping nautilus default file manger for now. Since nemo-
  desktop does not require any extensive patching it is easy to use
  under unity.

  Nemo-desktop will only draw the icons, not the background. In absence of
  nautilus unity-settings-daemon draws the background, so nothing to do in 
u-s-d.

  There are few small patches (nemo action files) required from nemo. 
@fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship 
  these action files ourselves as recommended by upstream. Budgie is doing the 
same.
  
https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions

  
  Since nautilus still be default file-manager we disable auto-mount with nemo 
and various other cinnamon/nemo option in ubuntu-settings.gsettings-override

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

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

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

2019-02-13 Thread Dmitry Shachnev

Hi Robert and Sergio!

Sorry for the delay with fixing this. In Qt packaging team, we are all
volunteers and work in our free time.

Initially I hoped that one of my co-maintainers would take care of this
issue, but looks like they also didn’t have time, so I fixed it myself
for the development release.

I will look at backporting this change to Bionic and Cosmic soon.

Note that I applied only Robert’s patch that fixes duplex printing. For
Ubuntu 19.04 we are going to ship Qt 5.12, which should have much better
printing experience. If there are other patches that can be backported,
please let me know.

Also, if one of you adds a test case (steps to reproduce) for the duplex
issue to the bug description, it will speed up the stable update a bit.

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

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

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src source package in Cosmic:
  New

Bug description:
  All kde applications shipped with ubuntu and particularly kubuntu
  bionic print via the qt print dialog, that, unfortunately, does not
  seem to respect the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
  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.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun 11 10:23:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1641 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic   | source, ...
   apt | 1.7.0   | cosmic   | source, ...
   apt | 1.8.0~rc2   | disco| source, ...

  [Test Case]
  1) Deploy a Trusty (14.04 LTS) vm w/ 128M
  2) Fetch latest stress-ng src code
   2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
   2.2) cd stress-ng
   2.3) make clean
   2.4) make
  3) Stress the mmap() with stress-ng
   3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
  4) Disable swap (if any)
   4.1) swapoff -a
  5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
  ...
  vsftpd:
Installed: (none)
Candidate: 3.0.2-1ubuntu2.14.04.1
Version table:
   3.0.2-1ubuntu2.14.04.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   3.0.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  ...

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815187] Re: Fix crash when opening DepCache before Cache

Broken in security (ubuntu2.19), fixed in proposed (ubuntu2.20).

root@tt:~# apt search -o RootDir=/dev/null foobar
Segmentation fault (core dumped)
root@tt:~# apt install apt libapt-pkg4.12
[...]
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.20) over (1.0.1ubuntu2.19) ...
Unpacking apt (1.0.1ubuntu2.20) over (1.0.1ubuntu2.19) ...
[...]
root@tt:~# apt search -o RootDir=/dev/null foobar
W: Unable to read /dev/null/etc/apt/sources.list.d/ - DirectoryExists (20: Not 
a directory)
W: Unable to read /dev/null/etc/apt/sources.list - RealFileExists (20: Not a 
directory)
E: Could not open file /dev/null/var/lib/dpkg/status - open (20: Not a 
directory)
E: The package lists or status file could not be parsed or opened.


** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  Fix crash when opening DepCache before Cache

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

  [Test case]
  Run apt search -o RootDir=/dev/null foobar, make sure it does not crash.

  [Regression potential]
  There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

2019-02-13 Thread Heitor R. Alves de Siqueira

There are two armhf autopkgtest regressions for apt-1.0.1ubuntu2.20, in
tests for apt [0] and autopkgtest [1]. From the autopkgtest pages we can
see that these regressions were introduced long before this SRU, so it
seems like a long standing issue unrelated to this patch.

[0] http://autopkgtest.ubuntu.com/packages/a/apt/trusty/armhf
[1] http://autopkgtest.ubuntu.com/packages/a/autopkgtest/trusty/armhf

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic   | source, ...
   apt | 1.7.0   | cosmic   | source, ...
   apt | 1.8.0~rc2   | disco| source, ...

  [Test Case]
  1) Deploy a Trusty (14.04 LTS) vm w/ 128M
  2) Fetch latest stress-ng src code
   2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
   2.2) cd stress-ng
   2.3) make clean
   2.4) make
  3) Stress the mmap() with stress-ng
   3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
  4) Disable swap (if any)
   4.1) swapoff -a
  5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
  ...
  vsftpd:
Installed: (none)
Candidate: 3.0.2-1ubuntu2.14.04.1
Version table:
   3.0.2-1ubuntu2.14.04.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   3.0.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  ...

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815761] [NEW] Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked

Public bug reported:

[Impact]
Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to 
show some extra output even if no changes had been made. Imagine "the user 
disabled the security repo, and does not get any updates shown scenario" - we'd 
like to be able to tell them that there are security updates available after 
all.

[Test case]
To be updated once the mechanism is in place, but basically perform an upgrade 
w/o changes, and make sure the specified hook runs at the end.

[Regression potential]
No-change upgrades/install can now fail if this new hooks fail.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

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

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

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

** Affects: apt (Ubuntu Disco)
 Importance: Undecided
 Status: In Progress

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

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have
  to be invoked

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Cosmic:
  New
Status in apt source package in Disco:
  In Progress

Bug description:
  [Impact]
  Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able 
to show some extra output even if no changes had been made. Imagine "the user 
disabled the security repo, and does not get any updates shown scenario" - we'd 
like to be able to tell them that there are security updates available after 
all.

  [Test case]
  To be updated once the mechanism is in place, but basically perform an 
upgrade w/o changes, and make sure the specified hook runs at the end.

  [Regression potential]
  No-change upgrades/install can now fail if this new hooks fail.

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

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

[Touch-packages] [Bug 1815760] [NEW] Additional hooks for update

Public bug reported:

[Impact]
We want to write some scripts for apt that run on update if apt shows an update 
count, to provide further details about the new cache.

[Test case]

Specify a APT::Update-Post-Invoke-Stats script and check that

(1) it shows in apt update
(2) it does not show in apt-get update

[Regression potential]
More scripts may fail the update now, but there should not be any registered so 
far.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

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

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

** Affects: apt (Ubuntu Disco)
 Importance: Undecided
 Status: In Progress

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  Additional hooks for update

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Cosmic:
  New
Status in apt source package in Disco:
  In Progress

Bug description:
  [Impact]
  We want to write some scripts for apt that run on update if apt shows an 
update count, to provide further details about the new cache.

  [Test case]

  Specify a APT::Update-Post-Invoke-Stats script and check that

  (1) it shows in apt update
  (2) it does not show in apt-get update

  [Regression potential]
  More scripts may fail the update now, but there should not be any registered 
so far.

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

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

[Touch-packages] [Bug 1815750] Re: autopkgtest failure due to security update

2019-02-13 Thread Dan Streetman

** Changed in: apt (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  autopkgtest failure due to security update

Status in apt package in Ubuntu:
  New
Status in apt source package in Trusty:
  Invalid
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Invalid
Status in apt source package in Cosmic:
  Invalid

Bug description:
  [impact]

  the security update for:
  SECURITY UPDATE: content injection in http method (CVE-2019-3462)
  (LP: #1812353)

  causes an autopkgtest failure for:
  Failed tests:  test-cve-2019-3462-dequote-injection

  [test case]

  run autopkgtest on the security-patched version

  [regression potential]

  the test needs to be updated, so the regression potential is around
  the test continuing to fail.

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

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

[Touch-packages] [Bug 1815761] [NEW] Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked

You have been subscribed to a public bug:

[Impact]
Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to 
show some extra output even if no changes had been made. Imagine "the user 
disabled the security repo, and does not get any updates shown scenario" - we'd 
like to be able to tell them that there are security updates available after 
all.

[Test case]
To be updated once the mechanism is in place, but basically perform an upgrade 
w/o changes, and make sure the specified hook runs at the end.

[Regression potential]
No-change upgrades/install can now fail if this new hooks fail.

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

-- 
Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be 
invoked
https://bugs.launchpad.net/bugs/1815761
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt 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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename

Fixes for other releases are queued up in git for the next SRUs (which
include some more substantial changes)

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

Title:
  APT doc and manpage uses wrong ubuntu-codename

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Invalid
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Cosmic:
  In Progress
Status in apt source package in Disco:
  Fix Released

Bug description:
  [Impact]

  APT documentation/example/manpages isn't referencing the current release
  which could be misleading for certain users.

  ---
  APT src code:
  ---
  [GOOD ubuntu-codename]

  * trusty:
  apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent:

  [WRONG ubuntu-codename]

  * xenial:
  apt-1.2.29/doc/apt-verbatim.ent:

  * bionic:
  apt-1.6.7/doc/apt-verbatim.ent:

  * disco:
  apt-1.8.0~alpha3/doc/apt-verbatim.ent:
  ---

  * vendor/ubuntu/sources.list.in
  ---
  # See sources.list(5) manpage for more information
  # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool.
  deb http://us.archive.ubuntu.com/ubuntu  main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu  main restricted

  deb http://security.ubuntu.com/ubuntu -security main 
restricted
  deb-src http://security.ubuntu.com/ubuntu -security main 
restricted

  deb http://us.archive.ubuntu.com/ubuntu -updates main 
restricted
  deb-src http://us.archive.ubuntu.com/ubuntu -updates main 
restricted
  ---

  The ubuntu-codename variable for Xenial and late in APT points to
  'trusty or 'xenial' which generate the doc example & manpage with the
  wrong release instead of the actual ubuntu-codename.

  APT in Xenial point to 'trusty'.
  APT in Bionic and late to 'xenial'

  It also affect the man page:

  Example took from Bionic:
  http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html
  http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html

  [Test Case]

  With Xenial and late:

   * Look sources.list(5) manpage
  Ex:
  http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html

   * Look apt_preferences(5) manpage
  Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html

   * Look /usr/share/doc/apt/examples/sources.list

  $ lsb_release -cs
  bionic

  $ cat /usr/share/doc/apt/examples/sources.list
  
  # See sources.list(5) manpage for more information
  # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool.
  deb http://us.archive.ubuntu.com/ubuntu xenial main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted

  deb http://security.ubuntu.com/ubuntu xenial-security main restricted
  deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted

  deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted
  --

  You'll notice they all point to the wrong release.

  While we understand it's not a "bug' and only a reference/example...
  I think it's for the best interest of all if the examples/manpage reference 
the current release.

  [Regression Potential]

   * None, it only affect documentation/examples and manpages. No
  behavior change in the APT code.

  [Other Info]

  [Original Description]
  From APT src code :

  ---
  [GOOD ubuntu-codename]
  * trusty:
  apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent:

  [WRONG ubuntu-codename]
  * xenial:
  apt-1.2.29/doc/apt-verbatim.ent:

  * bionic:
  apt-1.6.7/doc/apt-verbatim.ent:

  * disco:
  apt-1.8.0~alpha3/doc/apt-verbatim.ent:
  ---

  * vendor/ubuntu/sources.list.in
  ---
  # See sources.list(5) manpage for more information
  # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool.
  deb http://us.archive.ubuntu.com/ubuntu  main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu  main restricted

  deb http://security.ubuntu.com/ubuntu -security main 
restricted
  deb-src http://security.ubuntu.com/ubuntu -security main 
restricted

  deb http://us.archive.ubuntu.com/ubuntu -updates main 
restricted
  deb-src http://us.archive.ubuntu.com/ubuntu -updates main 
restricted
  ---

  The ubuntu-codename variable for Bionic and late in APT points to
  Xenial which generate the doc example with Xenial instead of the
  actual codename.

  * ./doc/sources.list.5.xml
  ---
   %aptverbatiment;
  ---

  It also seems to affect the man page by mentionning 'xenial'.
  Example took from Bionic:
  http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html
  http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html

To manage notifications about this bug go to:

[Touch-packages] [Bug 1359486] Re: "Use LibreOffice Dialogs" setting is ignored in KDE

2019-02-13 Thread Adolfo Jayme

LibreOffice has moved to Qt5 in 6.2.

** Changed in: qt4-x11 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  "Use LibreOffice Dialogs" setting is ignored in KDE

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Won't Fix

Bug description:
  Kubuntu 14.04 (KDE Desktop Environment)

  [update]
  This is now affecting packages from main ubuntu (trusty) repositories:
  libreoffice Version: 4.2.8-0ubuntu2 0
  qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1
  [/update]

  LibreOffice uses it's native filepicker/save dialogs, regardless of
  whether the config option "Use LibreOffice Dialogs" is ticked or not.

  Related Bugs:
  https://bugreports.qt-project.org/browse/QTBUG-38585
  https://bugreports.qt-project.org/browse/QTBUG-34614

  According to the LO team, both these bugs have patches that address
  the automatic disabling of Qt dialogs at runtime (if buggy Qt is
  detected.)

  Initial report/discussion on LO bugtracker (now closed) here:
  https://bugs.freedesktop.org/show_bug.cgi?id=82598

  [obsolete]
  Packages from this ppa:
  https://launchpad.net/~libreoffice

  Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages 
as of about 1 hour ago)
  or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog.

  This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu 
security repository.
  [/obsolete]

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions

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

[Touch-packages] [Bug 1812095] Re: console login loop after entering username followed by RETURN

2019-02-13 Thread bygorka

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

I have the same problem of the enter in the password field send many
enters.

It happens to me in ubuntu 16.04.5 - 4.4.0-142

Tested that in 4.4.0-141 don't happen.

Also commented in this issue: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
(the one that current issue is marked as duplicated of)
that kernel 4.4.0-143 has a fix for this.

I tested the kernel 4.4.0-143, and i can't reproduce the issue, so looks
like fixed.

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

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

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

[Touch-packages] [Bug 1815750] Re: autopkgtest failure due to security update

Yes, I know they're broken in xenial, and it's fixed in git, and will be
part of the next SRU.

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

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

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

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

Title:
  autopkgtest failure due to security update

Status in apt package in Ubuntu:
  New
Status in apt source package in Trusty:
  Invalid
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Invalid
Status in apt source package in Cosmic:
  Invalid

Bug description:
  [impact]

  the security update for:
  SECURITY UPDATE: content injection in http method (CVE-2019-3462)
  (LP: #1812353)

  causes an autopkgtest failure for:
  Failed tests:  test-cve-2019-3462-dequote-injection

  [test case]

  run autopkgtest on the security-patched version

  [regression potential]

  the test needs to be updated, so the regression potential is around
  the test continuing to fail.

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

2019-02-13 Thread Heitor R. Alves de Siqueira

Tested on apt-1.0.1ubuntu2.20 from trusty-proposed. Tried reproducing
according to the test case from description, and verified that apt-cache
does not crash:

ubuntu@apt-stress:~/stress-ng$ dpkg -l | grep apt
ii  apt 1.0.1ubuntu2.20

(while having stress-ng running)
ubuntu@apt-stress:~/stress-ng$ for i in `seq 1 1`;do apt-cache policy 
vsftpd;done
E: Couldn't make mmap of 30021560 bytes - MMap-mmap (12: Cannot allocate memory)
E: The package lists or status file could not be parsed or opened.

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done-trusty

** Tags added: verification-needed

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic   | source, ...
   apt | 1.7.0   | cosmic   | source, ...
   apt | 1.8.0~rc2   | disco| source, ...

  [Test Case]
  1) Deploy a Trusty (14.04 LTS) vm w/ 128M
  2) Fetch latest stress-ng src code
   2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
   2.2) cd stress-ng
   2.3) make clean
   2.4) make
  3) Stress the mmap() with stress-ng
   3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
  4) Disable swap (if any)
   4.1) swapoff -a
  5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
  ...
  vsftpd:
Installed: (none)
Candidate: 3.0.2-1ubuntu2.14.04.1
Version table:
   3.0.2-1ubuntu2.14.04.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   3.0.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  ...

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink

2019-02-13 Thread cement_head

Sorry.  No, running the stock kernel now & no bug.  Running the stock
kernel and this video driver

$ sudo dpkg -l |grep xserver-xorg-core
ii  xserver-xorg-core-hwe-18.04   2:1.20.1-3ubuntu2.1~18.04.1  amd64   Xorg X 
server - core server

$ uname -a
Linux -XX 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  The last MESA updates (02/07/19) corrupted output to DisplayLink

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Prior to Thursday's "update" from Bionic-Proposed, the MESA was
  working fine; afterwards, gameplay on STEAM has become choppy and
  staccato; secondary display via a USB-C through DisplayPort UD3900
  (Pluggable) is completely corrupted. See attached picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Feb 11 16:50:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:1323]
  InstallationDate: Installed on 2019-01-15 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp3-c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: galp3-c
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: galp3-c
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-13 Thread Nenad Antic

** Attachment added: "What it looks like when the machine freezes up"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5238322/+files/IMG_20190212_204350.jpg

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1583801] Re: [XPS 15 9550] [ALC3266] No sound via headphones (headset) when Ubuntu boots with them plugged in

2019-02-13 Thread Paolo Montesel

Don't know if it's related, but sometimes I don't get headphones audio when my 
XPS boots.
Disabling "Auto-Mute Mode" from alsamixer seems to fix the problem.

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

Title:
  [XPS 15 9550] [ALC3266] No sound via headphones (headset) when Ubuntu
  boots with them plugged in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1815750] [NEW] autopkgtest failure due to security update

2019-02-13 Thread Dan Streetman

Public bug reported:

[impact]

the security update for:
SECURITY UPDATE: content injection in http method (CVE-2019-3462)
(LP: #1812353)

causes an autopkgtest failure for:
Failed tests:  test-cve-2019-3462-dequote-injection

[test case]

run autopkgtest on the security-patched version

[regression potential]

the test needs to be updated, so the regression potential is around the
test continuing to fail.

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

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

** Affects: apt (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: apt (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  autopkgtest failure due to security update

Status in apt package in Ubuntu:
  New
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  New
Status in apt source package in Cosmic:
  New

Bug description:
  [impact]

  the security update for:
  SECURITY UPDATE: content injection in http method (CVE-2019-3462)
  (LP: #1812353)

  causes an autopkgtest failure for:
  Failed tests:  test-cve-2019-3462-dequote-injection

  [test case]

  run autopkgtest on the security-patched version

  [regression potential]

  the test needs to be updated, so the regression potential is around
  the test continuing to fail.

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

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

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-13 Thread Toru Ikezoe

** Description changed:

  Dear Maintainer.
  
  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
  
  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2
  
  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2
  
  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails
  
  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
- https://bit.ly/2BtN52W
+ 
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
  
  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user
  
  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_DISP 
msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  
- Thanks regards. https://bit.ly/2BtN52W
+ Thanks regards.

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam package in Debian:
  Fix Released

Bug description:
  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error

[Touch-packages] [Bug 1607696] Re: Version string missing in libjpeg.pc

2019-02-13 Thread Matthias Klose

** Changed in: libjpeg-turbo (Ubuntu)
 Assignee: Matthias Klose (doko) => (unassigned)

** Tags added: rls-dd-incoming

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

Title:
  Version string missing in libjpeg.pc

Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  Proper pkg-config files are installed if I build libjpeg-turbo myself.

  The description in the pkg-config file shipped by Ubuntu is also
  different from what is in upstream so I assume this is caused by
  Ubuntu (/Debian?) patching in a custom pkg-config file before they
  were included upstream in https://github.com/libjpeg-turbo/libjpeg-
  turbo/pull/53 .

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

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

[Touch-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-13 Thread Nenad Antic

** Description changed:

  Suddenly sometimes during the past two weeks my kubuntu installation has
  started to freeze up. I can't remember what apt upgrade that caused it,
  and I have done several the last few days hoping for it to be resolved.
  
  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within hours.
  Even without doing anything, just leaving the computer alone. However,
  yesterday I accidentally discovered that my RAM was filled up. More than
  filled up, even all swap was full. And before I could close anything
  down it froze up again.
  
  So TLDR; I have today logged the memory consumption while I was handling
  some bills and linked is a log of constantly increasing Xorg memory
  usage. So it goes until it chokes the machine and only a hard reboot is
  possible.
  
  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
- https://www.dropbox.com/s/nf1ev2dxdl..._leak.log?dl=0
+ https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0
  
  Please advise what additional information I should post to have this
  resolved.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
-Subsystem: VMware SVGA II Adapter [15ad:0405]
+  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
+    Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within

[Touch-packages] [Bug 1815742] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1815742/+attachment/5238269/+files/RfKill.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1813432] Re: Specific PDF file fails to print to HP m551dn printer

2019-02-13 Thread Till Kamppeter

I have added this case to upstream discussion now:

https://github.com/OpenPrinting/cups-filters/issues/65

** Bug watch added: github.com/OpenPrinting/cups-filters/issues #65
   https://github.com/OpenPrinting/cups-filters/issues/65

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

Title:
  Specific PDF file fails to print to HP m551dn printer

Status in cups package in Ubuntu:
  New

Bug description:
  One particular PDF file is failing to print. I have no idea why. When
  I say failing to print I mean that my computer thinks the file printed
  but the printer shows no sign of ever having received it. The display
  of the printer never changes to show that it is receiving or printing
  a file, and the job log of the printer doesn't show that it was
  received either. I also checked the printer event log and it doesn't
  show any events at the time I attempted to print the file.

  Unfortunately I can't attach the PDF file itself because it contains
  private information, and I can't find another PDF that exhibits this
  problem. I even tried generating a new PDF exactly the same way the
  old one was generated -- with the scan to email PDF function on my
  scanner -- and the new PDF prints just fine.

  I tried uploading the PDF directly to the printer with FTP and it
  prints just fine that way.

  I enabled CUPS debug mode before attempting to print the file.
  Attached is the resulting contents of /var/log/cups/error_log.

  I wish I knew what was going on here but honestly I have no idea.
  Perhaps you can learn something from the error_log. I hope so.

  Other files, including other PDFs, do print.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-3
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 17:47:49 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA_: 
ipps://m551dn.local:443/ipp/print
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', 
'/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1815742] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238272/+files/nmcli-con.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238273/+files/nmcli-dev.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238270/+files/WifiSyslog.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] modified.conffile..etc.NetworkManager.NetworkManager.conf.txt

apport information

** Attachment added: 
"modified.conffile..etc.NetworkManager.NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238271/+files/modified.conffile..etc.NetworkManager.NetworkManager.conf.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

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

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238265/+files/NetworkManager.conf.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

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

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238266/+files/PciNetwork.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.virbr1-nic.txt

apport information

** Attachment added: "NetDevice.virbr1-nic.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238262/+files/NetDevice.virbr1-nic.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.wlan0.txt

apport information

** Attachment added: "NetDevice.wlan0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238264/+files/NetDevice.wlan0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.vnet0.txt

apport information

** Attachment added: "NetDevice.vnet0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238263/+files/NetDevice.vnet0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.virbr1.txt

apport information

** Attachment added: "NetDevice.virbr1.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238261/+files/NetDevice.virbr1.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.virbr0-nic.txt

apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238260/+files/NetDevice.virbr0-nic.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.ovpn-surf.txt

apport information

** Attachment added: "NetDevice.ovpn-surf.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238257/+files/NetDevice.ovpn-surf.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.tinc0.txt

apport information

** Attachment added: "NetDevice.tinc0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238258/+files/NetDevice.tinc0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.virbr0.txt

apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238259/+files/NetDevice.virbr0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238252/+files/IwConfig.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238256/+files/NetDevice.lo.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] Dependencies.txt

apport information

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

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.eth0.txt

apport information

** Attachment added: "NetDevice.eth0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238255/+files/NetDevice.eth0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.docker0.txt

apport information

** Attachment added: "NetDevice.docker0.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238254/+files/NetDevice.docker0.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] NetDevice.br-2c9cac607cd8.txt

apport information

** Attachment added: "NetDevice.br-2c9cac607cd8.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238253/+files/NetDevice.br-2c9cac607cd8.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] IpRoute.txt

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238251/+files/IpRoute.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1815742/+attachment/5238250/+files/IpAddr.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] IfupdownConfig.txt

apport information

** Attachment added: "IfupdownConfig.txt"
   
https://bugs.launchpad.net/bugs/1815742/+attachment/5238249/+files/IfupdownConfig.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1815742/+attachment/5238247/+files/CRDA.txt

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1815742] [NEW] latest network-manager segfaults in disco