gtick core dumps, GThread-ERROR

[SirSiggi]

andreas@notebook:~$ gtick
GTK Accessibility Module initialized
GThread-ERROR **: GThread system may only be initialized once.
aborting...
[1] 7478 abort (core dumped) gtick

Core-Dump:
http://www.sirsiggi.net/~andreas/core

strace:
http://www.sirsiggi.net/~andreas/gtick.strace

/e: Sorry, shouldn't be assigned to gnome-baker, gtick is a separate package and has nothing to do with it. Is there a move or delete function? This was my first report.

[Michael Bienia (geser)]

Which Ubuntu version are you using? Dapper?

Can you create a backtrace? https://wiki.ubuntu.com/Backtrace explains how to do it.

Your links lead only to empty files. Please attach them to this bug report.

Thanks.

[Vincenzo Ciancia (vincenzo-ml)]

I am using edgy, there is no gtick-dbgsym package, however I can provide an "ltrace" which might suffice to identify the problem since it's very short; seems like gtk_init already calls gthread_init?

vincenzo@frattaglia:~$ ltrace gtick
__libc_start_main(0x804b920, 1, 0xbf8550d4, 0x8059421, 0x805941c <unfinished ...>
memcpy(0xbf854fd4, "\031\225\005\b", 80) = 0xbf854fd4
setlocale(6, "") = "it_IT.UTF-8"
bindtextdomain("gtick", "/usr/share/locale") = "/usr/share/locale"
textdomain("gtick") = "gtick"
gtk_init(0xbf855050, 0xbf855054, 80, 0, 0GTK Accessibility Module initialized
) = 1
getopt_long(1, 0xbf8550d4, "hvd::", 0xbf854fd4, 0xbf855024) = -1
bind_textdomain_codeset(0x80594fa, 0x8059513, 0x805950d, 0xbf854fd4, 0xbf855024) = 0x80d5bf0
g_thread_init(0, 0x80d5bf0, 0x805950d, 0xbf854fd4, 0xbf855024
GThread-ERROR **: GThread system may only be initialized once.
aborting...
 <unfinished ...>
--- SIGABRT (Aborted) ---
+++ killed by SIGABRT +++

[Aldo Nogueira (aldo-nogueira)]

I've tested on an Edgy 64. The same happens here.

Though, turning off accessibility solves this problem. If you don't need it, just turn it off on System / Preferences / Assistive Technology Preferences.

[Vincent Legout (vlegout)]

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

I can't reproduce it with gutsy.

[wolfger (wolfger)]

4+ months without a response. We are closing this bug report because we cannot confirm the problem still exists, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!