Errors from gtk+ interface of timidity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
timidity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: timidity-
Gtk+ is one of the better GUI interfaces available for timidity. Here are errors that I observed from invoking timidity using
timidity -ig directory/
I realize timidity is not maintained so this bug report is probably irrelevant.
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
(<unknown>:2485): Gtk-WARNING **: Invalid text buffer iterator: either the iterator is uninitialized, or the characters/
You must use marks, character numbers, or line numbers to preserve a position across buffer modifications.
You can apply tags and insert marks without invalidating your iterators,
but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset)
will invalidate all outstanding iterators
(<unknown>:2485): Gtk-CRITICAL **: gtk_text_
ProblemType: Bug
Architecture: lpia
Date: Sat Oct 17 23:32:39 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: timidity 2.13.2-36
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: timidity
Uname: Linux 2.6.31-14-lpia i686
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:1916): Eel-CRITICAL **: eel_preferences
(nautilus:2096): Eel-CRITICAL **: eel_preferences
Thanks for the report. Many Gtk+ programs I see display various assertion failures on stderr; this usually does not cause any practical problems. Have you seen any actual issues with the interface, or are you just reporting the messages?
It's certainly worth fixing the causes of these messages, but it's much lower-priority than fixing actual problems.