MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in g_signal_emit_valist()

Bug #91218 reported by Ted
160
Affects Status Importance Assigned to Milestone
gnome-cups-manager (Ubuntu)
Won't Fix
Medium
Ubuntu Printing Team

Bug Description

Binary package hint: gnome-cups-manager

This problem occurs only on 64-bit PCs

Clicking two or more icons in the gnome-cups-manager having the "New Printer" icon in the sequence crashes the gnome-cups-manager.

New Printer -> New Printer ==> Crash
New Printer -> Printer ==> Crash
Printer -> New Printer ==> Crash
Printer -> Printer -> Printer -> New Printer ==> Crash
Printer -> Printer -> Printer -> Printer -> Printer -> Printer -> Printer ==> No Crash

It does not matter whether with "New Printer" a print queue was created or whether the add printer wizard was canceled or whether the second icon in the gnome-cups-manager was already clicked while the add printer wizard was still loading the printer database.

Original report:

My samsung ml-2250 worked fine as wireless printer in edgy eft. does not work in fiesty fawn.

ProblemType: Crash
Architecture: amd64
Date: Sat Mar 10 14:37:50 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-cups-manager
Package: gnome-cups-manager 0.31-3ubuntu3
PackageArchitecture: amd64
ProcCmdline: gnome-cups-manager
ProcCwd: /root
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-cups-manager
StacktraceTop:
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED ()
Uname: Linux ted-desktop 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux
UserGroups: admin

Revision history for this message
Ted (teb21) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in gnome-cups-manager:
assignee: nobody → ubuntu-printing
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_signal_emit_valist (instance=0x85f1c0, signal_id=<value optimized out>, detail=0, var_args=0x7ffff835b2e0) at gsignal.c:2174
IA__g_signal_emit (instance=0x873c10, signal_id=10168192, detail=4164268576) at gsignal.c:2243
egg_icon_list_button_press (widget=0x85f1c0, event=0xb8a400) at eggiconlist.c:850
_gtk_marshal_BOOLEAN__BOXED_BOXED (closure=0x678630, return_value=0x7ffff835b5b0, n_param_values=<value optimized out>, param_values=0x7ffff835b6a0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Till Kamppeter (till-kamppeter) wrote : Re: [apport] gnome-cups-manager crashed with SIGSEGV in g_signal_emit_valist()

Seems that gnome-cups-manager currently does not work for most of the 64-bit users, therefore setting to "High".

Changed in gnome-cups-manager:
importance: Medium → High
status: Unconfirmed → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

On 32-bit the problem does not occur.

description: updated
Revision history for this message
Daniel Holbach (dholbach) wrote :

Looking at the trace, it might be a libegg problem:

#3 0x000000000040c0bf in egg_icon_list_button_press (widget=0x8599a0, event=0x735800) at eggiconlist.c:850
        icon_list = (EggIconList *) 0x8599a0
        item = (EggIconListItem *) 0x0
        dirty = 0

The copy of libegg bits in gnome-cups-manager look very different from http://svn.gnome.org/viewcvs/libegg/trunk/

Revision history for this message
Daniel Holbach (dholbach) wrote :

The bug does not happen when building the packaging with 'noopt'. Maybe a wrong variable initialization.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

What means "building the packaging with 'noopt'"?

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 91218] Re: MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in g_signal_emit_valist()

Till Kamppeter [2007-03-28 13:07 -0000]:
> What means "building the packaging with 'noopt'"?

DEB_BUILD_OPTIONS=noopt,nostrip debuild -us -uc -b

builds with -O0 -g ('noopt') and does not strip debug symbols from the
.debs ('nostrip')

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can I also do this by putting something into the debian/rules file? Otherwise the next one who builds the package will forget to use these options and the bug occurs again.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Yes, you can. That's the workaround we should use until we track that bug down.

Revision history for this message
Martin Pitt (pitti) wrote :

Hi,

Daniel Holbach [2007-03-28 14:49 -0000]:
> Yes, you can. That's the workaround we should use until we track that
> bug down.

No, please by no means ever ever do this. DEB_BUILD_OPTIONS should not
be set in debian/rules. The proper thing to do here is to set CFLAGS
to -O0 (or -O1, or similar).

Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload workaround the bug:

 gnome-cups-manager (0.31-3ubuntu4) feisty; urgency=low
 .
   * debian/gnome-cups-manager.desktop, debian/gnome-cups-manager.desktop.in:
     - use system category
   * debian/patches/37_transparent_notification_icon.patch:
     - notification area works with transparency (Ubuntu: #70213)
   * debian/rules:
     - use "OPTFLAGS=-O0" on amd64 to workaround launchpad crash #91218

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Sebastien, unfortunately, your new package does not reliably work around this problem. See bug 102199.

Revision history for this message
Sebastien Bacher (seb128) wrote :

This new update has the change:

 gnome-cups-manager (0.31-3ubuntu5) feisty; urgency=low
 .
   * debian/rules:
     - use -O0 on amd64, workaround launchpad #91218

Revision history for this message
Sebastien Bacher (seb128) wrote :

dropping milestone and lowering importance since the crash has been workarounded

Changed in gnome-cups-manager:
importance: High → Medium
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

We have changed the default print management system in Ubuntu from gnome-cups-manager to system-config-printer because g-c-m is no longer maintained. Please report future printing bugs against system-config-printer.

Changed in gnome-cups-manager:
status: Confirmed → Won't Fix
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.