After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646813 - Printers panel crash when started
Printers panel crash when started
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Printers
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Marek Kašík
Control-Center Maintainers
: 646888 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-04-05 13:29 UTC by Vincent Untz
Modified: 2011-04-07 12:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2011-04-05 13:29:22 UTC
I just tried to open the printers panel, and the control center crashed:


Program received signal SIGSEGV, Segmentation fault.
g_permission_get_allowed (permission=0x0) at gpermission.c:252
252       return permission->priv->allowed;
(gdb) bt
  • #0 g_permission_get_allowed
    at gpermission.c line 252
  • #1 actualize_sensitivity
    at cc-printers-panel.c line 2054
  • #2 printer_selection_changed_cb
    at cc-printers-panel.c line 633
  • #3 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #4 g_closure_invoke
    at gclosure.c line 767
  • #5 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #6 g_signal_emit_valist
    at gsignal.c line 2983
  • #7 g_signal_emit
    at gsignal.c line 3040
  • #8 _gtk_tree_selection_emit_changed
    at gtktreeselection.c line 1545

Comment 1 Vincent Untz 2011-04-05 13:30:02 UTC
(I'm smoketesting GNOME 3.0.0, so it's really the latest tarballs of everything)
Comment 2 Marek Kašík 2011-04-05 15:17:37 UTC
Hi Vincent,

thank you for this report. The problem was that there was no check of result of getting permission for "org.opensuse.cupspkhelper.mechanism.all-edit" policy (e.g. when the cups-pk-helper is not installed). I've fixed it in git.

Regards

Marek
Comment 3 Marek Kašík 2011-04-06 06:52:38 UTC
*** Bug 646888 has been marked as a duplicate of this bug. ***
Comment 4 Vincent Untz 2011-04-06 07:19:29 UTC
Do we need a 3.0.0.1 release with the fix? It seems like many people could hit this...
Comment 5 Marek Kašík 2011-04-06 17:38:41 UTC
Hi Vincent,

yeah, we probably need something like that. And I see that Matthias did that. I'm sorry about it.

Marek
Comment 6 Matthias Clasen 2011-04-07 12:10:39 UTC
*** Bug 646888 has been marked as a duplicate of this bug. ***