cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()

[xcape77]

errors.u.c https://errors.ubuntu.com/problem/cfe6699cf6c2996d3524baf4cd65b73a4c35dc41

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: cups-pk-helper 0.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Mon Mar 10 20:49:28 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism
ExecutableTimestamp: 1370947295
InstallationDate: Installed on 2014-03-10 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140309)
ProcCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism
ProcCwd: /
ProcEnviron:

Signal: 5
SourcePackage: cups-pk-helper
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_variant_valist_new_nnp (str=0x7fff6383a748, ptr=0x0) at /build/buildd/glib2.0-2.39.91/./glib/gvariant.c:4688
 g_variant_valist_new_leaf (app=0x7fff6383a778, str=0x7fff6383a748) at /build/buildd/glib2.0-2.39.91/./glib/gvariant.c:4844
 g_variant_valist_new (str=str@entry=0x7fff6383a748, app=app@entry=0x7fff6383a778) at /build/buildd/glib2.0-2.39.91/./glib/gvariant.c:5026
 g_variant_valist_new (str=str@entry=0x7fff6383a748, app=app@entry=0x7fff6383a778) at /build/buildd/glib2.0-2.39.91/./glib/gvariant.c:5078
 g_variant_new_va (format_string=0x7f090fe1a770 "a{ss})", endptr=0x0, app=0x7fff6383a778) at /build/buildd/glib2.0-2.39.91/./glib/gvariant.c:5254

[Launchpad Janitor (janitor)]

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

[Edson T. Marques (edsontmarques)]

A similar issue happened here in the cosmic. I was trying to install the Epson L355 printer and the crash happened early on after locating the printer on my network.

[Willem Hobers (whobers)]

Testing Xubuntu 18.10. Printer installation went fine. First print job started fine as well. Then the crash occurred and the print job stopt halfway through.

[Derk Willem te Bokkel (dtebokkel)]

canon pixma mx492 printer which was working before in artful and bionic now will not print .. constantly restarting print jobs is the proper driver being loaded/installed in cosmic

[Derk Willem te Bokkel (dtebokkel)]

determined that printer installs and works fine in xenial but drivers are missing from bionic and cosmic .. now gutenprint is supposed to supply these any idea why they went missing? or the communication fails to the printer under bionic/cosmic currently

[Derk Willem te Bokkel (dtebokkel)]

With the latest updates, I can now see that the printer is low on ink but the job continually restarts ..

[Derk Willem te Bokkel (dtebokkel)]

latest updates .. installed today still job restarts

printer was deleted then reinstalled network search detected printer tried to install w/o a driver but install still wanted to search for a driver for the canon pixima mx492 ..that failed

tried to print but it keeps saying that the printer is not connected ..
computers using cups (namely an apple mac air can printer to it)

[Derk Willem te Bokkel (dtebokkel)]

tried another install attempt .. I remembered that on an other distribution is worked with gutenprint but this seems unavailable in cosmic?? apt install gutenprint fails ..

[Derk Willem te Bokkel (dtebokkel)]

added libgutenprintui2-2 then used localhost:631 via browser to modify the printer driver to point to the gutenprint driver then it works .. will not select this via set-up printer module by default so you have to over ride manually .. test page printed fine even tough it was slow..

[Till Kamppeter (till-kamppeter)]

This is already 3 years old and there are no similar complaints. So the probability is low that the bug is still there. Closing ...