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 (Ubuntu)
Status: Confirmed = Won't Fix
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/6725215/CoreDump.gz
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://bugs.launchpad.net/bugs/91218
You received this bug notification because you are a member of Ubuntu
Bugs, which
dropping milestone and lowering importance since the crash has been
workarounded
** Changed in: gnome-cups-manager (Ubuntu)
Importance: High = Medium
Target: ubuntu-7.04 = None
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
This new update has the change:
gnome-cups-manager (0.31-3ubuntu5) feisty; urgency=low
.
* debian/rules:
- use -O0 on amd64, workaround launchpad #91218
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://bugs.launchpad.net/bugs/91218
You
** Summary changed:
- [apport] gnome-cups-manager crashed with SIGSEGV in g_signal_emit_valist()
+ MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
On 32-bit the problem does not occur.
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://launchpad.net/bugs/91218
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Description changed:
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
Looking at the trace, it might be a libegg problem:
#3 0x0040c0bf 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
The bug does not happen when building the packaging with 'noopt'. Maybe
a wrong variable initialization.
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://launchpad.net/bugs/91218
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
What means building the packaging with 'noopt'?
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://launchpad.net/bugs/91218
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Till Kamppeter [2007-03-28 13:07 -]:
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')
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
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.
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://launchpad.net/bugs/91218
--
Yes, you can. That's the workaround we should use until we track that
bug down.
--
MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in
g_signal_emit_valist()
https://launchpad.net/bugs/91218
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi,
Daniel Holbach [2007-03-28 14:49 -]:
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).
14 matches
Mail list logo
