[Touch-packages] [Bug 1645687] Re: 50unattended-upgrades.ucf-dist

2017-05-27 Thread Walter L Cullars
upgrade from 14.04 to 16.04 did this.  I copy file to documents. I removed said 
file from apt dir.
  sudo rm...  ok, then apt worked with no more N: msg

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

Title:
  50unattended-upgrades.ucf-dist

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  During a refresh procedure of Ubuntu-Mate 16.04 (on 29th November,
  2016) the following notice appeared in the first line of the terminal.
  (Refreshing among others the linux-
  image-4.4.0-51-generic_4.4.0-51.72_i386.deb package):

  N: "50unattended-upgrades.ucf-dist" file(s) has/have been left out of
  consideration in the "/etc/apt/apt.conf.d/ map having invalid file
  extension.

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

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


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

2017-05-27 Thread Jarno Suni
Because the code can be applied in many kernel post-installation
scripts, I have attached it in Bug #1501884 and further updates go
there.

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:

2017-05-27 Thread Launchpad Bug Tracker
[Expired for unity-system-compositor (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b
  contains more details.

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

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


[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:

2017-05-27 Thread Launchpad Bug Tracker
[Expired for mir (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b
  contains more details.

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

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


[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish

2017-05-27 Thread Launchpad Bug Tracker
[Expired for unity-system-compositor (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unity-system-compositor crashes with SIGABRT in
  google::protobuf::internal::LogMessage::Finish

Status in Unity System Compositor:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.10.20150722-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1479030/+subscriptions

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


[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:

2017-05-27 Thread Launchpad Bug Tracker
[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b
  contains more details.

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

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


[Touch-packages] [Bug 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob

2017-05-27 Thread Launchpad Bug Tracker
[Expired for mir (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a
  contains more details.

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

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


[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish

2017-05-27 Thread Launchpad Bug Tracker
[Expired for Unity System Compositor because there has been no activity
for 60 days.]

** Changed in: unity-system-compositor
   Status: Incomplete => Expired

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

Title:
  unity-system-compositor crashes with SIGABRT in
  google::protobuf::internal::LogMessage::Finish

Status in Unity System Compositor:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.10.20150722-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1479030/+subscriptions

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


[Touch-packages] [Bug 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob

2017-05-27 Thread Launchpad Bug Tracker
[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a
  contains more details.

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

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


[Touch-packages] [Bug 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob

2017-05-27 Thread Launchpad Bug Tracker
[Expired for unity-system-compositor (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  /usr/sbin/unity-system-
  
compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in unity-system-compositor package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a
  contains more details.

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

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


[Touch-packages] [Bug 1587326] Re: package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de dépendances - actions différées non exécutées

2017-05-27 Thread Launchpad Bug Tracker
[Expired for gconf (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de
  dépendances - actions différées non exécutées

Status in gconf package in Ubuntu:
  Expired

Bug description:
  When I was upgrading the system (with do-release-upgrade), I've encountered 
the following error:
  dpkg: des problèmes de dépendances empêchent le traitement des actions 
différées pour gconf2 :
   gconf2 dépend de python3 ; cependant :
   Le paquet python3 n'est pas encore configuré.

  dpkg: erreur de traitement du paquet gconf2 (--configure) :
   problèmes de dépendances - actions différées non exécutées
  Error in function:

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 480, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 433, in write
  block = f.read(1048576)
File "/usr/lib/python3.4/codecs.py", line 319, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was: 
  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gconf2.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue May 31 10:05:41 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu5:problèmes de dépendances - 
actions différées non exécutées
  ErrorMessage: problèmes de dépendances - actions différées non exécutées
  InstallationDate: Installed on 2016-01-12 (139 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu5 failed to install/upgrade: problèmes de 
dépendances - actions différées non exécutées
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (0 days ago)

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

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


[Touch-packages] [Bug 1568364] Re: it fails to install set some modem setups to help me access the internet connectivity easily

2017-05-27 Thread Launchpad Bug Tracker
[Expired for fontconfig (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  it fails to install set some modem setups to help me access the
  internet connectivity easily

Status in fontconfig package in Ubuntu:
  Expired

Bug description:
  it fails to install setups for moderation demoderation which will help
  me full access to the internet easily.

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

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


[Touch-packages] [Bug 1648982] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

2017-05-27 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in cups package in Ubuntu:
  Expired

Bug description:
  not update successfully and package is bad

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 10 20:41:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-10  20:41:13
   Requested-By: ajinkya-im-possible (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), 
python3-apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), apport-gtk:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), python3-problem-report:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.1), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.1), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  DuplicateSignature:
   package:cups-daemon:2.1.3-4
   Removing cups-core-drivers (2.1.3-4ubuntu0.1) ...
   dpkg: error processing package cups-daemon (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2016-12-03 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Sony Corporation VPCCB45FN
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2110V2
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2110V2:bd09/27/2011:svnSonyCorporation:pnVPCCB45FN:pvrC60A1P3G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCB45FN
  dmi.product.version: C60A1P3G
  dmi.sys.vendor: Sony Corporation

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

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


[Touch-packages] [Bug 1676854] Re: apps launched from the launcher menu doesn't seem to work

2017-05-27 Thread Launchpad Bug Tracker
[Expired for unity8 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  apps launched from the launcher menu doesn't seem to work

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  apps launched from the launcher menu doesn't seem to work

  at least on my pc (ubuntu 17.04 Unity8 + silo 2626)
  right click on some random app from the launcher, click on the apps name to 
launch
  does nothing here

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676854/+subscriptions

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


[Touch-packages] [Bug 1694093] [NEW] VPN passwords save when they shouldn't

2017-05-27 Thread BloodyIron
Public bug reported:

I use network-manager to connect to openVPN servers.

First, when adding a new VPN config, entering a login is required, and
we are unable to save if we do not enter a username. This is a security
flaw as we need the ability to enter login and password each and every
time as an option.

Second, I enter a login username, but not a password. On first
connection it asks for a password, but never again. I have never been
asked for a password on the same VPN after entering it the first time.
This persists across reboots also. This is a substantial security flaw,
and this should be an option, not the default behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.6-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 27 21:35:10 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-18 (99 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 tun0 tun   connected/org/freedesktop/NetworkManager/Devices/4  
tun03337e7b3-7794-4539-a5a3-0a534f60800f  
/org/freedesktop/NetworkManager/ActiveConnection/6 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
notforyou   e8f5ba42-91e9-4755-b1b7-0c030961f69e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --  
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  VPN passwords save when they shouldn't

Status in network-manager package in Ubuntu:
  New

Bug description:
  I use network-manager to connect to openVPN servers.

  First, when adding a new VPN config, entering a login is required, and
  we are unable to save if we do not enter a username. This is a
  security flaw as we need the ability to enter login and password each
  and every time as an option.

  Second, I enter a login username, but not a password. On first
  connection it asks for a password, but never again. I have never been
  asked for a password on the same VPN after entering it the first time.
  This persists across reboots also. This is a substantial security
  flaw, and this should be an option, not the default behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 27 21:35:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-18 (99 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   tun0 tun   connected/org/freedesktop/NetworkManager/Devices/4  
tun03337e7b3-7794-4539-a5a3-0a534f60800f  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
notforyou   e8f5ba42-91e9-4755-b1b7-0c030961f69e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   

[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system

2017-05-27 Thread atom
Me too.

Turns out the problem for me is updating *while* copying a hard-drive
(in another terminal).

The "update-initramfs" script calls "sync" in the "generate_initramfs"
function. For me, copying hard-drives at the same time caused "sync" to
hang: Then the whole thing hangs.

I CTRL-Z'd (TSTP) my rsync process (doing the copying), and a few
seconds later update-initramfs un-hung. Finished without a problem.

Proposed workarounds:
1- stop/pause large disk i/o operations while updating, or
2- edit "/usr/sbin/update-initramfs": comment out the "sync" command in the 
"generate_initramfs" function

This is why Ubuntu (and other Linux distros) needs a user-space "fsync"
command; so instead of trying to sync busy drives that could be busy for
days, it can just "fsync ${file}" and get on with the day.

Not sure if this will fix anyone else's problems, but it's all unicorns
and rainbows over here, now.

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

Title:
  update-initramfs hangs on upgrade, dpkg unusable, unbootable system

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  At least four users, including myself, are having an issue with
  update-initramfs hanging while updating ubuntu 16.04. The bug has been
  documented while attempting an update to multiple kernel versions (
  4.4.0-24, 4.4.0-62,  4.4.0-63). The bug causes any apt-get update or
  install to fail, and may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)   
  
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for cracklib-runtime (2.9.2-1build2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic

   Uh oh! Let's try to troubleshoot.

  $ sudo killall dpkg
  $ sudo dpkg --configure -a
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Setting up base-files (9.4ubuntu4.4) ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  initrd.img(/boot/initrd.img-4.4.0-63-generic
  ) points to /boot/initrd.img-4.4.0-63-generic
   (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  vmlinuz(/boot/vmlinuz-4.4.0-63-generic
  ) points to /boot/vmlinuz-4.4.0-63-generic
   (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
  ^CFailed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-63-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.4.0-63-generic; however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-signed-image-4.4.0-63-generic:
   linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic 
(= 4.4.0-63.84); however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent 

[Touch-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

2017-05-27 Thread Jeremy Bicha
** Also affects: gnome-bluetooth (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** No longer affects: bluez (Ubuntu Xenial)

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

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

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in blueman source package in Xenial:
  New
Status in gnome-bluetooth source package in Xenial:
  New
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings 
(the correct device's options don't appear in the right pane). Hence no 
Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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


[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

2017-05-27 Thread Jeremy Bicha
** No longer affects: bluez (Ubuntu Xenial)

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

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

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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


[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-05-27 Thread Jeremy Bicha
** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: bluez (Ubuntu Xenial)

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To 

[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

2017-05-27 Thread Jeremy Bicha
** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in bluez source package in Xenial:
  New
Status in pulseaudio source package in Xenial:
  New

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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


[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-05-27 Thread Çağatay Yüksel
On Ubuntu 17.04, I could get this working with the following steps:

1. rm -rf /etc/resolv.conf

This will tell systemd-resolved not to manage resolve.conf file. Simply
disabling systemd-resolved service does not work because of some other
depending service is enabled and starts systemd-resolved anyway.

2. Add this line to the [main] section of 
/etc/NetworkManager/NetworkManager.conf
dns=dnsmasq

Appeartently network manager manages its own instance of dnsmasq so if
you have dnsmasq package installed, you should make sure the dnsmasq
service is not enabled otherwise this will not work. You can also
install dnsmasq-base package instead, which does not include a systemd
unit.

A reboot probably is also necessary, I did these via ansible playbooks
to create bootable images so this was the case for me. Restarting
network manager service might also work.

Hope this helps, best

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Expired
Status in openvpn package in Ubuntu:
  Expired

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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


[Touch-packages] [Bug 1694084] [NEW] package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to install/upgrade: package libqt5script5:amd64 is not ready for configuration cannot configure (current stat

2017-05-27 Thread mario munoz
Public bug reported:

software center is crashing.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5script5:amd64 5.5.1+dfsg-2build1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libqt5script5: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat May 27 19:49:52 2017
DpkgTerminalLog:
 dpkg: error processing package libqt5script5:amd64 (--configure):
  package libqt5script5:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-10-13 (226 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: qtscript-opensource-src
Title: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to 
install/upgrade: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtscript-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to
  install/upgrade: package libqt5script5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

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

Bug description:
  software center is crashing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5script5:amd64 5.5.1+dfsg-2build1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libqt5script5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 27 19:49:52 2017
  DpkgTerminalLog:
   dpkg: error processing package libqt5script5:amd64 (--configure):
package libqt5script5:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-13 (226 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: qtscript-opensource-src
  Title: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to 
install/upgrade: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1694083] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-27 Thread Robby Suhardis
Public bug reported:

i stuck in ubuntu sofware center for downloading aplication

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sun May 28 06:28:38 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-23 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  i stuck in ubuntu sofware center for downloading aplication

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sun May 28 06:28:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 988144] Re: Getting error message: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

2017-05-27 Thread Peter Grandi
> the remote 'rsync' process takes too long to send back the
> list of block checksums to the local 'rsync' in some situations

As to that a quick web search indicates previous reports:

https://unix.stackexchange.com/questions/68775/rsync-timed-out 3
«It looks like the server times out on the SSH connection level.»
«Since the timeout appears to happen when rsync is creating the checksums»

https://bugzilla.samba.org/show_bug.cgi?id=7195
«it seems - in my case at least - to be related to the delta-xfer algorithm»

** Bug watch added: Samba Bugzilla #7195
   https://bugzilla.samba.org/show_bug.cgi?id=7195

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

Title:
  Getting error message:  error in rsync protocol data stream (code 12)
  at io.c(605) [sender=3.0.9]

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Precise 12.04LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 3.0.9-1ubuntu1
Candidate: 3.0.9-1ubuntu1
Version table:
   *** 3.0.9-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen

  I was using rsync to backup my Home DIrectorys' contents and at one
  point in the backup it gave me this error:

   Downloads/Windows.7.Ultimate.32-64Bit.(2011-02-09).iso
3809312768  83%   21.03MB/s0:00:35  
   rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: 
Broken pipe (32)
   rsync: connection unexpectedly closed (70735 bytes received so far) 
[sender]
   rsync error: error in rsync protocol data stream (code 12) at io.c(605) 
[sender=3.0.9]
   

  This only came about when it was trying to copy my Windows ISO from my
  directory over to my backup drive that I have formatted in EXT4 - so
  I'm not sure of the issue it's having.

  This is the command I used to backup:

  rsync --progress -rEog --exclude Videos/ --exclude converted_music/
  --exclude VirtualBox\ VMs/ --exclude virtual-drives/ --exclude
  Backup_of_boot_sectors/ --exclude examples.desktop --exclude Music/
  --exclude .ecryptfs --exclude .VirtualBox/ --exclude .thumbnails/
  --exclude .thunderbird/ --exclude .vidalia/ --exclude .teamviewer/
  --exclude Templates/ --exclude sources.list --exclude wary-5.3.iso
  --exclude Public/ --exclude .cache/ /home/alex/ /media/backup/12.04
  -Precise-backup_4.23.2012/

  
  Please look into this for me.

  Thank you

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

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


[Touch-packages] [Bug 1648077] Re: Support for Mozilla Location Service (A-GPS)

2017-05-27 Thread Marius Gripsgard 
** Also affects: ubports-meta
   Importance: Undecided
   Status: New

** Changed in: ubports-meta
   Status: New => Fix Released

** Changed in: ubports-meta
 Assignee: (unassigned) => Ricardo (ing-mendoza-ricardo)

** Changed in: location-service (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Support for Mozilla Location Service (A-GPS)

Status in UBports System Image:
  Fix Released
Status in location-service package in Ubuntu:
  Invalid

Bug description:
  Currently, A-GPS is only available on commercial UT-devices through
  Nokia HERE. This is a real problem for users of community ports (like
  those provided by ubports.com). Also, the HERE service is closed
  source and proprietary, that's kind of odd for the free operating
  system we all want Ubuntu Touch to be.

  I suggest that we try to implement the Mozilla Location Service, which
  is a free and open source location service:
  https://location.services.mozilla.com/

  There is a bounty on Bountysource on this:
  https://www.bountysource.com/issues/39808752-support-for-mozilla-
  location-service-a-gps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubports-meta/+bug/1648077/+subscriptions

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


[Touch-packages] [Bug 988144] Re: Getting error message: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

2017-05-27 Thread Peter Grandi
This happens for me too with files of a few GB sometimes on ULTS 14 with
RSYNC 3.1.0.

> It also works, when I try rsync with -W option at client side.

Same, and for me it works also when specifying '--block-size 4096'.

What this makes me suspect is that the remote 'rsync' process takes too
long to send back the list of block checksums to the local 'rsync' in
some situations, and a smaller checksum granularity, or asking for
checksums to not be computed avoids that.

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

Title:
  Getting error message:  error in rsync protocol data stream (code 12)
  at io.c(605) [sender=3.0.9]

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Precise 12.04LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 3.0.9-1ubuntu1
Candidate: 3.0.9-1ubuntu1
Version table:
   *** 3.0.9-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen

  I was using rsync to backup my Home DIrectorys' contents and at one
  point in the backup it gave me this error:

   Downloads/Windows.7.Ultimate.32-64Bit.(2011-02-09).iso
3809312768  83%   21.03MB/s0:00:35  
   rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: 
Broken pipe (32)
   rsync: connection unexpectedly closed (70735 bytes received so far) 
[sender]
   rsync error: error in rsync protocol data stream (code 12) at io.c(605) 
[sender=3.0.9]
   

  This only came about when it was trying to copy my Windows ISO from my
  directory over to my backup drive that I have formatted in EXT4 - so
  I'm not sure of the issue it's having.

  This is the command I used to backup:

  rsync --progress -rEog --exclude Videos/ --exclude converted_music/
  --exclude VirtualBox\ VMs/ --exclude virtual-drives/ --exclude
  Backup_of_boot_sectors/ --exclude examples.desktop --exclude Music/
  --exclude .ecryptfs --exclude .VirtualBox/ --exclude .thumbnails/
  --exclude .thunderbird/ --exclude .vidalia/ --exclude .teamviewer/
  --exclude Templates/ --exclude sources.list --exclude wary-5.3.iso
  --exclude Public/ --exclude .cache/ /home/alex/ /media/backup/12.04
  -Precise-backup_4.23.2012/

  
  Please look into this for me.

  Thank you

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

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


[Touch-packages] [Bug 1694063] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-27 Thread Theodore
Public bug reported:

i think this bug came up when i restarted my laptop after i tried to
install chrome from the official site and it got stuck saying installing
and it never installed

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat May 27 21:56:41 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-27 (0 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  i think this bug came up when i restarted my laptop after i tried to
  install chrome from the official site and it got stuck saying
  installing and it never installed

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat May 27 21:56:41 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-27 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1694047] [NEW] [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

2017-05-27 Thread Hemant Kumar
Public bug reported:

After upgrading from ubuntu 16.10 to 17.04, my laptop sound system is
not working. How to fix? Please give some solutions.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hemant 2325 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sat May 27 21:10:46 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-10-14 (225 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hemant 2325 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to zesty on 2017-05-26 (0 days ago)
dmi.bios.date: 06/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 07JM0H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug zesty

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

Title:
  [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading from ubuntu 16.10 to 17.04, my laptop sound system is
  not working. How to fix? Please give some solutions.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hemant 2325 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sat May 27 21:10:46 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-10-14 (225 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hemant 2325 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-05-26 (0 days ago)
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 07JM0H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1694036] [NEW] package python3-pkg-resources 33.1.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2017-05-27 Thread Gordon Ackley
Public bug reported:

New install of 16.4, then upgrade to 16.10, then 17.4 with this issue
and an error message about the graphics environment.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-pkg-resources 33.1.1-1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat May 27 08:53:06 2017
Dependencies:
 
DuplicateSignature:
 package:python3-pkg-resources:33.1.1-1
 Setting up python3-pkg-resources (33.1.1-1) ...
 Segmentation fault
 dpkg: error processing package python3-pkg-resources (--configure):
  subprocess installed post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2017-05-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: python-setuptools
Title: package python3-pkg-resources 33.1.1-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to zesty on 2017-05-27 (0 days ago)

** Affects: python-setuptools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package python3-pkg-resources 33.1.1-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  New install of 16.4, then upgrade to 16.10, then 17.4 with this issue
  and an error message about the graphics environment.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-pkg-resources 33.1.1-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat May 27 08:53:06 2017
  Dependencies:
   
  DuplicateSignature:
   package:python3-pkg-resources:33.1.1-1
   Setting up python3-pkg-resources (33.1.1-1) ...
   Segmentation fault
   dpkg: error processing package python3-pkg-resources (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-05-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python-setuptools
  Title: package python3-pkg-resources 33.1.1-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to zesty on 2017-05-27 (0 days ago)

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

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


[Touch-packages] [Bug 1693986] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat May 27 09:14:36 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-15 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-05-27 Thread Bug Watch Updater
** Changed in: cracklib2 (Debian)
   Status: New => Fix Released

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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


[Touch-packages] [Bug 1694017] [NEW] nvidia driver installation causing X.org to freeze

2017-05-27 Thread A K Singh
Public bug reported:

Hi,
Please let me know if you need any other info than the attached information.
Thanks
Br
aksgaur

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat May 27 14:01:19 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:050e]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e]
InstallationDate: Installed on 2017-05-01 (26 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Dell Inc. Dell System XPS L502X
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e35ef27e-882a-4ccf-9430-7246671359cb ro rootflags=subvol=@ quiet 
splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug possible-manual-nvidia-install ubuntu xenial

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

Title:
  nvidia driver installation causing X.org to freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Please let me know if you need any other info than the attached information.
  Thanks
  Br
  aksgaur

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 27 14:01:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e]
  InstallationDate: Installed on 

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

2017-05-27 Thread Tim
May 27 13:06:23 mbpr15 tracker-extract[11638]: Could not insert metadata
for item "file:///home/wolf/Documents/books/it-vertrage-kurz-und-
praktisch.pdf": 42.33: invalid UTF-8 character

Is it always that same file that causes it?

May 27 13:06:23 mbpr15 tracker-extract[11638]: If the error above is
recurrent for the same item/ID, consider running "tracker-extract" in
the terminal with the TRACKER_VERBOSITY=3 environment variable, and
filing a bug with the additional information

if so run the following on your problematic file and file an upstream bug at 
bugs.gnome.org with the output. If you do so please provide a link to the 
upstream bug, so we can add it onto this bug report.
tracker extract -v debug 

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

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

Status in tracker package in Ubuntu:
  New

Bug description:
  By default Budgie installs tracker.

  $ tracker status

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

  in syslog:

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

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

  

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

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

[Touch-packages] [Bug 1691695] Re: package bash 4.3-14ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-05-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  the problem appeared when i tried to install the latest updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 18 11:35:37 2017
  DpkgTerminalLog:
   dpkg: error processing package bash (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-17 (212 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-05-27 Thread Wolf Rogner
Public bug reported:

By default Budgie installs tracker.

$ tracker status

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

in syslog:

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


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



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

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

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


** Tags: amd64 apport-bug zesty

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

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

Status in tracker package in Ubuntu:
  New

Bug description:
  By default Budgie installs tracker.

  $ tracker status

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

  in syslog:

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

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

2017-05-27 Thread Wolf Rogner
Some more detail:

sudo tracker daemon --get-log-verbosity 
Components:
  Store: errors
  Extract  : errors
  Writeback: errors

Miners (Only those with config listed):
  Files: errors


(tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

(tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

(tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

(tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

(tracker daemon:12598): Tracker-WARNING **: (tracker-
daemon.c:1708):daemon_run: code should not be reached

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

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

Status in tracker package in Ubuntu:
  New

Bug description:
  By default Budgie installs tracker.

  $ tracker status

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

  in syslog:

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

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

  

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

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

[Touch-packages] [Bug 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-05-27 Thread Heikki Savolainen
** Changed in: debconf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  package linux-image-4.8.0-53-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in debconf package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Fix Committed

Bug description:
  it show there's bug in my system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-53-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu May 25 08:42:40 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-03 (51 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-53-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-05-27 Thread meeck
I have this problem too. With mysql-workbench, connecting to remote
servers from file manager and  other programs. The workaround from some
upper posts restores functionality.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1689565] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-05-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: shared-mime-info (Ubuntu)
   Status: New => Confirmed

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  Says that "usr" is full, though I should have space. I've fixed broken
  packages but I can't install anything.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May  9 18:21:21 2017
  DpkgTerminalLog:
   Setting up shared-mime-info (1.5-2ubuntu0.1) ...
   I/O error : No space left on device
   Failed to write XML file; For permission problems, try rerunning as root
   dpkg: error processing package shared-mime-info (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-18 (21 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1689565/+subscriptions

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


[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-05-27 Thread TenLeftFingers
Opera is also affected by this issue. Takes almost a minute to load
whereas Firefox loads in under five seconds.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1693992] Re: /usr/lib/gdm3/gdm-session-worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch

2017-05-27 Thread Tim
** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
Milestone: None => artful

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

Title:
  /usr/lib/gdm3/gdm-session-
  
worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed

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

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

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


[Touch-packages] [Bug 1669995] Re: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', que está tam

2017-05-27 Thread Andreas Moog
DistroRelease: Kali 2016.2 - Kali Linux has its own bugtracker at
https://bugs.kali.org/main_page.php - The Ubuntu community can't provide
support for a different distribution.

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

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

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/gconf/2
  /libgconfbackend-evoldap.so', que está también en el paquete gconf-
  service-backend 3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  problem with menu katoolin

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Mar  4 12:22:55 2017
  DpkgTerminalLog:
   Preparando para desempaquetar .../gconf-service_3.2.6-4+b1_amd64.deb ...
   Desempaquetando gconf-service (3.2.6-4+b1) sobre (3.2.6-3ubuntu6) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/gconf-service_3.2.6-4+b1_amd64.deb (--unpack):
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', que está 
también en el paquete gconf-service-backend 3.2.6-3ubuntu6
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', que está 
también en el paquete gconf-service-backend 3.2.6-3ubuntu6
  InstallationDate: Installed on 2017-02-09 (22 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.22kali1
   apt  1.4~rc2
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', que está 
también en el paquete gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1693986] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-27 Thread Adrien Marion
Public bug reported:

package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
128

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat May 27 09:14:36 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-15 (11 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat May 27 09:14:36 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-15 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 612249] Re: Wrong error when mounting vfat filesystem with invalid mount option

2017-05-27 Thread Adolfo Jayme
** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Wrong error when mounting vfat filesystem with invalid mount option

Status in util-linux package in Ubuntu:
  New

Bug description:
  Binary package hint: util-linux

  /etc/fstab has the following line:

  LABEL=IAUDIO /media/audioplayer/ vfat
  uid=1000,gid=1000,noatime,nls=utf8,sync,user  0 0

  if you run:

  mount /media/audioplayer

  then it gives you the error:

  mount: can't find /media/audioplayer in /etc/fstab or /etc/mtab

  However, the problem is actually the nls=utf8, which vfat doesn't
  support.

  In dmesg it says:

  [11610.081002] FAT: Unrecognized mount option "nls=utf8" or missing
  value

  Is it possible to get this error corrected? It's not that it can't
  find /media/audioplayer in fstab (clearly it can), but it's an option
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: util-linux 2.17.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Sun Aug  1 22:24:49 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux

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

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