After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640490 - dasher crashed with SIGSEGV in Dasher::CDasherModel::HandleOutput()
dasher crashed with SIGSEGV in Dasher::CDasherModel::HandleOutput()
Status: RESOLVED INCOMPLETE
Product: dasher
Classification: Applications
Component: gtk
4.11
Other Linux
: Normal critical
: ---
Assigned To: Patrick Welche
Patrick Welche
Depends on:
Blocks:
 
 
Reported: 2011-01-24 23:26 UTC by Charlie Kravetz
Modified: 2013-05-06 23:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stacktrace (1.11 KB, text/plain)
2011-01-24 23:26 UTC, Charlie Kravetz
Details

Description Charlie Kravetz 2011-01-24 23:26:24 UTC
Created attachment 179251 [details]
stacktrace

This bug was reported on Ubuntu Launchpad as:
https://bugs.launchpad.net/bugs/637747

Forwarded from the launchpad report:

tried it on gedit & it crashed

DistroRelease: Ubuntu 10.10
Package: dasher 4.11-1
Uname: Linux 2.6.35-20-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
ExecutablePath: /usr/bin/dasher
ProcCmdline: dasher --appstyle=direct
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
 LANGUAGE=en_GB:en
SegvAnalysis:
 Segfault happened at: 0x8097cb6 <_ZN6Dasher12CDasherModel12HandleOutputEPSt6vectorINS_10SymbolProbESaIS2_EEPi+102>: mov (%eax),%edx
 PC (0x08097cb6) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: dasher

StacktraceTop:
 Dasher::CDasherModel::HandleOutput ()
 Dasher::CDasherModel::OneStepTowards ()
 Dasher::CDefaultFilter::Timer ()
 Dasher::CDasherInterfaceBase::NewFrame ()
 CDasherControl::TimerEvent ()

XsessionErrors: (polkit-gnome-authentication-agent-1:2404): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
Comment 1 Fabio Durán Verdugo 2011-01-25 02:45:00 UTC
paste here the traceback

  • #0 Dasher::CDasherModel::HandleOutput
  • #1 Dasher::CDasherModel::OneStepTowards
  • #2 Dasher::CDefaultFilter::Timer
  • #3 Dasher::CDasherInterfaceBase::NewFrame
  • #4 CDasherControl::TimerEvent
  • #5 timer_callback
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #10 IA__gtk_main
    at /build/buildd/gtk+2.0-2.21.7/gtk/gtkmain.c line 1237
  • #11 main

Comment 2 Patrick Welche 2011-01-25 10:29:49 UTC
I was unable to reproduce with the following attempt:

Ubuntu 10.04.2 LTS x86_64
grabbed dasher-4.11.tar.bz2 from download.gnome.org
./configure --prefix /tmp/foo
gedit 2.30.3
cd /tmp/foo; bin/dasher --appstyle=direct

I was able to write into gedit without problems with

System / Preferences / Assistive Technologies / assistive technologies

both enabled and disabled.

I'm not sure what to try next - maybe you could try building from that tarball
and try the same tests I did?
Comment 3 Charlie Kravetz 2011-01-26 18:38:18 UTC
Okay, I installed Ubuntu 10.10, updated it, then installed dasher. I can not reproduce this issue with

System / Preferences / Assistive Technologies / assistive technologies

enabled. With assistive technologies disabled, I can not make dasher write to gedit or any other application.

Errors from terminal when running dasher without Assistive Technologies enabled:

vbadmin@number70:~$ dasher --appstyle=direct
** Message: Opening GUI file: /usr/share/dasher/dasher.direct.ui
** Message: Opening GUI file: /usr/share/dasher/dasher.preferences.ui

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

** (dasher:2928): WARNING **: AT_SPI_REGISTRY was not started at session startup.

** (dasher:2928): WARNING **: Could not locate registry
** Message: Could not initialise SPI - accessibility options disabled

(dasher:2928): Gtk-CRITICAL **: IA__gtk_paned_set_position: assertion `GTK_IS_PANED (paned)' failed

(dasher:2928): Gtk-CRITICAL **: IA__gtk_paned_get_position: assertion `GTK_IS_PANED (paned)' failed
Segmentation fault
Comment 4 Akhil Laddha 2011-03-10 10:09:42 UTC
Can you provide us trace of crash as i see 'Segmentation fault' at the end of comment#3 ?
Comment 5 Charlie Kravetz 2011-03-10 14:04:22 UTC
I would be happy to get another stacktrace, if you could tell me how to get one with debug symbols included. There is no -dbg nor -dbgsym package for dasher that lets me get a better trace than the one attached to this report.
Comment 6 Patrick Welche 2011-03-10 16:37:13 UTC
Why not try building from source - cf comment 2? (or even grab had with

git clone git://git.gnome.org/dasher
cd dasher
sh autogen.sh
make
make install
Comment 7 C de-Avillez 2011-05-13 06:32:03 UTC
reopening. Bug is still unresolved, per contact with OP.
Comment 8 Patrick Welche 2013-01-25 17:30:50 UTC
Direct mode has been revamped - could you try the version in git-head please as per Comment 6 and let us know how it goes?
Comment 9 Tobias Mueller 2013-05-06 23:15:26 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!