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

Bug #1118323 reported by Gleidson Galindo
80
This bug affects 22 people
Affects Status Importance Assigned to Milestone
cups-pk-helper (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ao tentar adicionar uma impressora, o sistema retorna uma mensagem de erro. Além do mais, não consegui localizar uma impressora em rede.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: cups-pk-helper 0.2.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Thu Feb 7 10:35:09 2013
ExecutablePath: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism
InstallationDate: Installed on 2013-02-06 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130206)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism
ProcEnviron:

Signal: 5
SourcePackage: cups-pk-helper
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/i386-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:

Revision history for this message
Gleidson Galindo (omggalindo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_valist_new_nnp (str=str@entry=0xbf8d9650, ptr=0x0) at /build/buildd/glib2.0-2.35.4/./glib/gvariant.c:4155
 g_variant_valist_new_leaf (app=0xbf8d966c, str=0xbf8d9650) at /build/buildd/glib2.0-2.35.4/./glib/gvariant.c:4311
 g_variant_valist_new (str=str@entry=0xbf8d9650, app=app@entry=0xbf8d966c) at /build/buildd/glib2.0-2.35.4/./glib/gvariant.c:4493
 g_variant_valist_new (str=str@entry=0xbf8d9650, app=app@entry=0xbf8d966c) at /build/buildd/glib2.0-2.35.4/./glib/gvariant.c:4545
 g_variant_new_va (format_string=0xb77865b0 "a{ss})", endptr=0x0, app=0xbf8d966c) at /build/buildd/glib2.0-2.35.4/./glib/gvariant.c:4702

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cups-pk-helper (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: saucy
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in cups-pk-helper (Ubuntu):
status: New → Confirmed
tags: added: trusty
Revision history for this message
Sebastien Bacher (seb128) wrote :
information type: Private → Public
Revision history for this message
ADFH (adfh) wrote (last edit ):

I went to add a Kyocera Mita FS-1030D+ with an IB-21E NIC.

1. Tapped Windows key
2. Searched for "printers"
3. Saw list of printers already added in settings app in printer section
(Two printers originally listed - one not connected, one auto-added by network detection)
4. Clicked "Add" button in the titlebar to add Kyocera
5. Add printer dialog appears, spinner shown briefly, then "System program problem detected"

I now get a similar system program problem detected every time I sign into my account.

I was able to add the printer through older looking Gnome printer dialog ("Additional Printer Settings" button), but still get a crash every time I sign in.

Revision history for this message
ADFH (adfh) wrote :

I've gotten around the bug by:
* Shutting down cups service
* Deleting
  * /etc/cups/printers.conf*
  * /etc/cups/classes.conf*
  * /etc/cups/subscriptions.conf*
* Rebooting
* Adding printer using the "Additional Printer Settings" button rather than the "Add" button on initial screen

All three sets of deleted files were auto-created again, and no crash dialog appeared.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.