(xcdroast:18561): Gtk-CRITICAL **: file gtkwidget.c: line 3065 (gtk_widget_event): assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed xcdroast 0.98alpha15 gtk+ 2.2.4-r1 Reproducible: Always Steps to Reproduce: 1. start xcdroast 2. click 'create cd' 3. click 'master tracks' Actual Results: (xcdroast:18561): Gtk-CRITICAL **: file gtkwidget.c: line 3065 (gtk_widget_event): assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed Expected Results: should have been quiet ;-) this does not seem to cause any serious problems
Please provide your emerge info, along with the version of GTK you have installed.
could you please indicate how i should collect this information? sorry for my naivete.... eek. :-) specifically, i'm not sure what you mean by 'emerge info'. i've done emerge sync, emerge world -- still getting GTK widget problems. i suppose it would be more productive to give you some info and if it's correct, then great--otherwise please reprimand me as to wh at i should be doing. % emerge --version Portage 2.0.50-r6 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo-r1) % emerge -pv gtk+ xcdroast [ebuild R ] x11-libs/gtk+-2.4.1 -doc +jpeg +tiff 0 kB [ebuild R ] app-cdr/xcdroast-0.98_alpha15-r3 +dvdr +gnome +gtk2 -nls 0 kB more than a dozen of these spewing after i start xcdroast then choose create cd: (xcdroast:26285): Gtk-CRITICAL **: file gtkwidget.c: line 3359 (gtk_widget_event): assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
type: emerge info Provide that information to this bug... If you aren't having the problem anymore, please let us know so this can be closed.
Gentoo Base System version 1.4.10 Portage 2.0.50-r6 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 x86_64 4 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind:/usr/X11R6/lib/X11/xkb:/usr/kde/3.2/share/config:/usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/gconf:/etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib aim alsa amd64 apm arts avi cdr crypt dvd emacs encode esd foomaticdb gd gdbm gif gnome gpm gtk gtk2 imagemagick imap imlib imlib2 ipv6 java jikes jpeg junit kerberos krb4 libg++ libwww mad mikmod motif mozilla mpeg multilib ncurses nogcj oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl spell ssl tcltk tcpd tiff truetype usb xml xml2 xmms xv yahoo zlib"
Does xcdroast fail to work? I assume these messages are displayed in the xterm you started xcdroast from. If xcdroast still works fine, I'm going to close this bug. GTK apps gripe all the time like this.
yes the output is spewing into the xterm which started xcdroast program. you can close the bug if this is standard operating procedure, however i would make a request: please do not close the bug. :-) i feel this is a real problem, perhaps it is /only/ low severity but it should be treated as a bug.. if there is no problem, GTK should not issue these boy-crying-wolf messages.
Here,s what I suggest. Take a look at this page: http://www.xcdroast.org/faq/#6 Create a bug report and submit it to the upstream maintainers, since this doesn't seem to prevent use of the program.
