[print-notifications] gnome-settings-daemon crashed with SIGFPE in g_hash_table_lookup_node()

[Seunghyuk Choi]

Nothing really happend but error message occured

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Sun Mar 25 14:15:32 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120325)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 LANG=ko_KR.UTF-8
Signal: 8
SourcePackage: gnome-settings-daemon
Title: gnome-settings-daemon crashed with SIGFPE in g_hash_table_lookup_extended()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x23f0a19, hash_table=0x23bcd80) at /build/buildd/glib2.0-2.31.22/./glib/ghash.c:407
 g_hash_table_lookup_extended (hash_table=0x23bcd80, lookup_key=0x23f0a19, orig_key=0x0, value=0x0) at /build/buildd/glib2.0-2.31.22/./glib/ghash.c:1110
 on_cups_notification (connection=<optimized out>, sender_name=<optimized out>, object_path=<optimized out>, interface_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, user_data=0x7f6a10008600) at gsd-print-notifications-manager.c:558
 emit_signal_instance_in_idle_cb (data=0x7f6a08005150) at /build/buildd/glib2.0-2.31.22/./gio/gdbusconnection.c:3665
 g_main_dispatch (context=0x2215a10) at /build/buildd/glib2.0-2.31.22/./glib/gmain.c:2515

[Robert Ancell (robert-ancell)]

The stack trace shows you received a message from your printer "Printer "psc-1200-series" state changed to idle." and gnome-settings-daemon crashed checking its internal printer table. Can't see any particular bug that would cause that.

[Launchpad Janitor (janitor)]

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