Your message dated Mon, 3 Jun 2013 23:35:22 +1000
with message-id <[email protected]>
and subject line Done: attempting to access cell format menu causes an infinite
loop of error messages and hangs gnumeric
has caused the Debian Bug report #621034,
regarding attempting to access cell format menu causes an infinite loop of
error messages and hangs gnumeric
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
621034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621034
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: gnumeric
Version: 1.10.13-1
Severity: important
*** Please type your report below this line ***
When running gnumeric on a gnumeric-formatted spreadsheet, I wished to change
the background color of one of the cells, so I selected the cell, right-clicked
on it, and chose the "Format 1 Cell" option. At this point, the program became
unresponsive, and on the console from which I was running it the following error
message repeated indefinitely until I killed the program:
(gnumeric:24701): Gtk-CRITICAL **: IA__gtk_widget_show: assertion `GTK_IS_WIDGET
(widget)' failed
This also happens if I try to format multiple cells simultaneously, or if I
select the Format>Cells>Format... command from the top menu instead of the
right-click menu. It's not clear to me whether the problem is with gnumeric or
gtk, but something is badly wrong, that's fer shore.
- Anne
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.37-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnumeric depends on:
ii debconf [de 1.5.38 Debian configuration management sy
ii gconf2 2.28.1-6 GNOME configuration database syste
ii gnumeric-co 1.10.13-1 spreadsheet application for GNOME
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript interpre
ii libatk1.0-0 1.32.0-3 The ATK accessibility toolkit
ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib
ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra
ii libglib2.0- 2.28.4-1 The GLib library of C routines
ii libgoffice- 0.8.13-1 Document centric objects library -
ii libgsf-1-11 1.14.20-1 Structured File Library - runtime
ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface
ii libpango1.0 1.28.3-5 Layout and rendering of internatio
ii libxml2 2.7.8.dfsg-2 GNOME XML library
ii procps 1:3.2.8-10 /proc file system utilities
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages gnumeric recommends:
ii evince 2.30.3-3 Document (PostScript, PDF) viewer
ii lp-solve 5.5.0.13-7 Solve (mixed integer) linear progr
Versions of packages gnumeric suggests:
pn epiphany-browser <none> (no description available)
pn gnumeric-doc <none> (no description available)
pn gnumeric-plugins-extra <none> (no description available)
ii ttf-liberation 1.06.0.20100721-1 Fonts with the same metrics as Tim
ii ttf-mscorefonts-instal 3.3 Installer for Microsoft TrueType c
- -- debconf information:
gnumeric/existing-process: false
gnumeric/existing-process-title:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2boXsACgkQwi82URPCSX4vRQCfYxeFV677KQdmSscvL8xfAWPg
g00An0W7wU6o6lJRtyavDf4fQFOHqLRe
=/KRt
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Package: gnumeric
Version: 1.10.17-1.1
We believe that the bug you reported was fixed in one of the previous
versions of gnumeric which was installed in the Debian FTP archive.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--- End Message ---
