[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-08-08 Thread dynaguy
I got this on my newly built 64-bit Ubuntu 16.04 as well:
Aug  8 06:25:32 tau systemd[1]: Started CUPS Scheduler.
Aug  8 06:25:32 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12313]: No such device or address
Aug  8 06:25:32 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12313]: No such device or address
Aug  8 06:38:33 tau systemd[1]: Started CUPS Scheduler.
Aug  8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12325]: No such device or address
Aug  8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12325]: No such device or address
Aug  8 06:51:33 tau systemd[1]: Started CUPS Scheduler.
Aug  8 06:51:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12337]: No such device or address
Aug  8 06:51:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12337]: No such device or address
Aug  8 07:04:34 tau systemd[1]: Started CUPS Scheduler.
Aug  8 07:04:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12349]: No such device or address
Aug  8 07:04:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12349]: No such device or address
Aug  8 07:17:01 tau CRON[12361]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Aug  8 07:17:35 tau systemd[1]: Started CUPS Scheduler.
Aug  8 07:17:35 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12364]: No such device or address
Aug  8 07:17:35 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12364]: No such device or address

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-02-02 Thread dynaguy
Fix confirm. Thanks a lot.

I notice I noticed this  updated network-manager is only available in
trusty-proposed repo now.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Triage Notes]

  This regression is caused by a libnl proposed update tracked in bug
  1511735. It has not been released as an update, only proposed as an
  update for early testing. If you volunteered to test proposed updates,
  then thank you. Your care and attention will stop this regression from
  hitting ordinary users, and we appreciate your contribution to Ubuntu.

  If you are not aware that you volunteered to test proposed updates,
  then please be aware that your system is configured to do so. In this
  case, you probably should turn this off. I'd appreciate if someone
  could explain how to do this in the comments.

  [Impact]

   * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
     libnl-route-3-200) and when libnl is updated to proposed
     3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
     validation packets.

     This affects the 0.98 release of NetworkManager and has already
     been fixed in newer releases.

   * Backporting fixes from upstream release is required to prevent
     NetworkManager from faulting which breaks networking on most
     Desktop releases.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

   * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
     libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

  [Test Case]

   * Reproduce crash test:
  1. Download 14.04.03 Desktop iso, amd64
  2. Launched in a VM, run from iso
  3. In terminal, enable proposed
  4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
  5. sudo restart network-manager
  #  note the nm-applet disappears as NM has now crashed, no network
     conn.
  6. dmesg to confirm network-manager crash
  7. sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
  8. sudo start network-manager
  #  nm-applet reappears, network connectivity restored

   * Successful upgrade test:
     1. Download 14.04.03 Desktop iso, amd64
     2. Launched in a VM, run from iso
     3. In a terminal, sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
     4. sudo restart network-manager  # NM still runs, no crash, net up
     5. enable trusty-proposed in /etc/apt/sources.list
     6. sudo apt-get update
     7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
     8. sudo restart network-manager  # NM still runs, no crash, net up.

  [Regression Potential]

   * NetworkManager is a highly visible package, so testing NetworkManager
     functionality is critical.  The patch does address the crash specificly
     introduced by the updated libnl SRU.

   * We need to ensure that users have installed this NetworkManager
     update before installing libnl3 update (special phasing needed).

  [Original Description]
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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