Bug#909621: anjuta hangs on startup
Andrea Calì
el_gato75 at libero.it
Tue Oct 23 21:48:06 BST 2018
Package: anjuta
Followup-For: Bug #909621
Dear Maintainer,
after installing the debug symbols for anjuta, the full gdb backtrace at the
moment of hangup (before the splashscreen loading) is the following:
********
#0 0xb69daf30 in g_hash_table_foreach (hash_table=0x15d8ae0, func=0xb6ae8fb0
<pool_depth_list>, user_data=0xbfb4b854) at ././glib/ghash.c:1605
#1 0xb6aeac6b in g_param_spec_pool_list (pool=0x15dc470, owner_type=24117760,
n_pspecs_p=0xbfb4b898) at ././gobject/gparam.c:1306
#2 0xb6ae4f94 in g_object_class_list_properties (class=0x16e0c00,
n_properties_p=0xbfb4b904) at ././gobject/gobject.c:918
#3 0xb7668509 in gdl_dock_layout_setup_object (after_params=<synthetic
pointer>, n_after_params=<synthetic pointer>, node=0xf5c2ca8, master=0x17184a8
[GdlDockMaster]) at gdl-dock-layout.c:312
#4 0xb7668509 in gdl_dock_layout_recursive_build
(master=master at entry=0x17184a8 [GdlDockMaster],
parent_node=parent_node at entry=0xc32bb48, parent=parent at entry=0x0) at gdl-dock-
layout.c:410
#5 0xb76690c6 in gdl_dock_layout_load (node=0xc32bb48, master=0x17184a8
[GdlDockMaster]) at gdl-dock-layout.c:473
#6 0xb76690c6 in gdl_dock_layout_load_layout (layout=0x16ccbc8
[GdlDockLayout], name=0x0) at gdl-dock-layout.c:691
#7 0x004e26fc in anjuta_window_layout_load (win=win at entry=0x17301a8
[AnjutaWindow], layout_filename=layout_filename at entry=0x1a65c00
"/home/murdock/.cache/anjuta/session/dock-layout.xml", name=0x0) at anjuta-
window.c:957
#8 0x004e2975 in on_session_load (shell=0x17301a8,
phase=ANJUTA_SESSION_PHASE_LAST, session=0x16e4e10 [AnjutaSession],
win=0x17301a8 [AnjutaWindow]) at anjuta-window.c:513
#12 0xb6afa394 in <emit signal 0xb6952aba "load_session" on instance 0x17301a8
[AnjutaWindow]> (instance=0x17301a8, detailed_signal=0xb6952aba "load_session")
at ././gobject/gsignal.c:3487
#9 0xb6adec3b in g_closure_invoke (closure=0x1832ca8, return_value=0x0,
n_param_values=3, param_values=0xbfb4bb20, invocation_hint=0xbfb4bac4) at
././gobject/gclosure.c:804
#10 0xb6af101e in signal_emit_unlocked_R (node=node at entry=0x16d8348,
detail=detail at entry=0, instance=instance at entry=0x17301a8, emission_return=0x0,
instance_and_params=0xbfb4bb20) at ././gobject/gsignal.c:3635
#11 0xb6af9bb6 in g_signal_emit_valist (instance=0x17301a8, signal_id=230,
detail=0, var_args=0xbfb4bd20 "\250\001s\001P") at ././gobject/gsignal.c:3391
#13 0xb69051f2 in anjuta_shell_session_load () at /usr/lib/i386-linux-
gnu/libanjuta-3.so.0
#14 0x004de054 in on_profile_scoped (profile=0x16e32d0 [AnjutaProfile],
win=0x17301a8 [AnjutaWindow]) at anjuta-application.c:253
#18 0xb6afa394 in <emit signal 0xb695567e "scoped" on instance 0x16e32d0
[AnjutaProfile]> (instance=0x16e32d0, detailed_signal=0xb695567e "scoped") at
././gobject/gsignal.c:3487
#15 0xb6adec3b in g_closure_invoke (closure=0x1834bb0, return_value=0x0,
n_param_values=1, param_values=0xbfb4bf00, invocation_hint=0xbfb4bea4) at
././gobject/gclosure.c:804
#16 0xb6af101e in signal_emit_unlocked_R (node=node at entry=0x1835af0,
detail=detail at entry=0, instance=instance at entry=0x16e32d0, emission_return=0x0,
instance_and_params=0xbfb4bf00) at ././gobject/gsignal.c:3635
#17 0xb6af9bb6 in g_signal_emit_valist (instance=0x16e32d0, signal_id=305,
detail=0, var_args=0xbfb4c0d8 "\360v~\001\001") at ././gobject/gsignal.c:3391
#19 0xb691328f in anjuta_profile_load () at /usr/lib/i386-linux-
gnu/libanjuta-3.so.0
#20 0xb6913948 in () at /usr/lib/i386-linux-gnu/libanjuta-3.so.0
#21 0x004defae in anjuta_application_create_window (app=0x15e5090
[AnjutaApplication]) at anjuta-application.c:820
#22 0x004df435 in anjuta_application_open (application=0x15e5090
[AnjutaApplication], files=0x0, n_files=0, hint=0x16bd970 ";") at anjuta-
application.c:525
#23 0xb5dd3e3a in ffi_call_SYSV () at /usr/lib/i386-linux-gnu/libffi.so.6
#24 0xb5dd3aac in ffi_call () at /usr/lib/i386-linux-gnu/libffi.so.6
#25 0xb6adf830 in g_cclosure_marshal_generic_va (closure=0x15e1ff8,
return_value=0x0, instance=<optimized out>, args_list=0xbfb4c5dc "",
marshal_data=0x4df160 <anjuta_application_open>, n_params=3,
param_types=0x15e3df0) at ././gobject/gclosure.c:1604
#26 0xb6adee5f in _g_closure_invoke_va (closure=0x15e1ff8, return_value=0x0,
instance=0x15e5090, args=0xbfb4c5dc "", n_params=3, param_types=0x15e3df0) at
././gobject/gclosure.c:867
#27 0xb6af991e in g_signal_emit_valist (instance=0x15e5090, signal_id=9,
detail=0, var_args=0xbfb4c5dc "") at ././gobject/gsignal.c:3300
#28 0xb6af9ed5 in g_signal_emit (instance=0x15e5090, signal_id=9, detail=0) at
././gobject/gsignal.c:3447
#29 0xb6bc7709 in g_application_open (application=0x15e5090
[AnjutaApplication], files=0x0, n_files=0, hint=0x171eb68 ";") at
././gio/gapplication.c:2192
#30 0x004de985 in anjuta_application_local_command_line (application=0x15e5090
[AnjutaApplication], arguments=0xbfb4c7d0, exit_status=0xbfb4c7d4) at anjuta-
application.c:499
#31 0xb6bc8036 in g_application_run (application=0x15e5090 [AnjutaApplication],
argc=1, argv=0xbfb4c8e4) at ././gio/gapplication.c:2350
#32 0x004dd052 in main (argc=1, argv=0xbfb4c8e4) at main.c:38
********
but following your suggestion, using another (newly created) account I found
that anjuta runs normally without hanging.
So I tried running again anjuta from my usual account, after hiding the cached
data:
$ cd ~/.cache && mv anjuta anjuta__hide
and this time anjuta started normally and quickly without hanging.
So I think this was the cause of the hangup. Sorry for bothering with improper
bug filing...
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-8-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages anjuta depends on:
ii anjuta-common 2:3.22.0-3
ii libanjuta-3-0 2:3.22.0-3
ii libapr1 1.5.2-5
ii libc6 2.24-11+deb9u3
ii libdevhelp-3-2 3.22.0-1+b1
ii libgcc1 1:6.3.0-18+deb9u1
ii libgda-5.0-4 5.2.4-3
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii libgdl-3-5 3.22.0-1
ii libgladeui-2-6 3.20.0-2+deb9u1
ii libglib2.0-0 2.50.3-2
ii libgtk-3-0 3.22.11-1
ii libgtksourceview-3.0-1 3.22.2-1
ii libpango-1.0-0 1.40.5-1
ii libpython2.7 2.7.13-2+deb9u3
ii libstdc++6 6.3.0-18+deb9u1
ii libsvn1 1.9.5-1+deb9u2
ii libvala-0.34-0 0.34.7-1
ii libvte-2.91-0 0.46.1-1
ii libwebkit2gtk-4.0-37 2.18.6-1~deb9u1
ii libxml2 2.9.4+dfsg1-2.2+deb9u2
Versions of packages anjuta recommends:
ii autoconf 2.69-10
ii autogen 1:5.18.12-3
ii automake 1:1.15-6
ii g++ 4:6.3.0-4
ii gcc 4:6.3.0-4
ii gdb 7.12-6
pn intltool <none>
ii liblocale-gettext-perl 1.07-3+b1
ii libtool 2.4.6-2
ii make 4.1-9.1
pn valac <none>
ii yelp 3.22.0-1
Versions of packages anjuta suggests:
ii gjs 1.46.0-1+b2
ii glade 3.20.0-2+deb9u1
ii libgtk-3-dev 3.22.11-1
ii libgtkmm-3.0-dev 3.22.0-1
pn python-distutils-extra <none>
pn python-rope <none>
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list