/usr/lib/packagekit/packagekitd:11:strlen:__add_to_environ:__setenv:AptIntf::init:backend_get_updates_thread

Bug #1572778 reported by errors.ubuntu.com bug bridge on 2016-04-20
148
This bug affects 35 people
Affects Status Importance Assigned to Milestone
packagekit (Ubuntu)
High
Unassigned
Xenial
High
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with version 0.8.17-4ubuntu6~gcc5.4ubuntu1, the problem page at https://errors.ubuntu.com/problem/b61d4f35571d067e050e834a7e1dd822f85aaadf contains more details.

Launchpad Janitor (janitor) wrote :

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

Changed in packagekit (Ubuntu):
status: New → Confirmed
Changed in packagekit (Ubuntu):
importance: Undecided → High
Changed in packagekit (Ubuntu Xenial):
milestone: none → xenial-updates
Matthias Klumpp (ximion) wrote :

I really wonder why this issue appears now, especially since Ubuntu isn't using PK itself...
Might be due to the backported patches, or even some non-backported stuff in combination with changes in APT (the aptcc backend evolved a lot in the last 3 years).

Changed in packagekit (Ubuntu):
milestone: xenial-updates → none
Pascal (pascalchap) wrote :

Same problem with

ubuntu LTS16.04.
pureadmin version(0.4-0ubuntu2)

I noticed that on all reports I found concerning this bug, the architecture is amd64.
I havn't packagekit installed

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers