Synaptic Crashes when Clicking apply (Dapper)

[essexman]

On Dapper Fl3 Fully dist upgraded to 6pm GMT 06/02/06

Start Synaptic System>>Administration>>Synaptic Package Manager

Mark a programme for installation>>Apply

On the 'Summary' dialog >> Apply

Synaptic crashes.

On Ubuntu Forums a solution of: Disabling /desktop/gnome/interface/accessibility via gconf-editor has been given. But this is already diabled on my system.

[Jeffrey Knockel (jeff250)]

Have you tried logging out and logging in after disabling accessibility? Or even rebooting if that doesn't work?

For some background, this bug is popular because enabling:
/apps/metacity/general/reduced_resources
...disables Metacity's cheezy minimize effect. Unfortunately, it also enables another: windows on move will appear in wireframe. However, it was discovered that this can in turn be disabled by enabling this in addition to the above:
/desktop/gnome/interface/accessibility
which grants the best of both worlds: no cheezy minimize effects and no cheezy wireframe window move.

Granted, this might be considered a "hack" to deal with Metacity's special effects problems, but I doubt that it is supposed to crash Synaptic, so it is still a legitimate bug.

A reference:
http://ubuntuforums.org/showthread.php?t=124951

[Michael Vogt (mvo)]

Thanks for your bugreport.

Can you please open a gnome-terminal and run:
$ sudo gdb synaptic
(gdb) run
[make it crash]
(gdb) backtrace
and send me the result? Please also include any startup messages from synaptic that it prints on the terminal.

Thanks,
 Michael

[Geert Altena (ge2rt)]

Backtrace with a debug enabled synaptic:

$ sudo dpkg -i synaptic_0.57.6ubuntu3_amd64.deb
Password:
(Reading database ... 99121 files and directories currently installed.)
Preparing to replace synaptic 0.57.6ubuntu3 (using synaptic_0.57.6ubuntu3_amd64.deb) ...
Unpacking replacement synaptic ...
Setting up synaptic (0.57.6ubuntu3) ...

$ sudo gdb synaptic
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/sbin/synaptic
[Thread debugging using libthread_db enabled]
[New Thread 46912557839088 (LWP 6832)]
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
GTK Accessibility Module initialized

(synaptic:6832): Gtk-WARNING **: Theme directory 16x16/status16x16/stock/chart of theme gnome has no size field

** ERROR **: file gailtreeview.c: line 3601 (garbage_collect_cell_data): assertion failed: (GAIL_IS_TREE_VIEW (data))
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 46912557839088 (LWP 6832)]
0x00002aaaacb6b12e in g_logv () from /usr/lib/libglib-2.0.so.0
(gdb) backtrace
#0 0x00002aaaacb6b12e in g_logv () from /usr/lib/libglib-2.0.so.0
#1 0x00002aaaacb6b393 in g_log () from /usr/lib/libglib-2.0.so.0
#2 0x00002aaaacb6b416 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#3 0x00002aaaaea3dcfb in gail_tree_view_new () from /usr/lib/gtk-2.0/modules/libgail.so
#4 0x00002aaaacb62a8d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#5 0x00002aaaacb65d55 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#6 0x00002aaaacb66204 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#7 0x00002aaaab0bd9c1 in gtk_main_iteration () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x0000000000433357 in RGMainWindow::setInterfaceLocked (this=0x63e460,
    flag=<value optimized out>) at rgmainwindow.cc:1752
#9 0x000000000043ca72 in RGMainWindow::cbProceedClicked (self=<value optimized out>,
    data=<value optimized out>) at rgmainwindow.cc:2556
#10 0x00002aaaac7fe8d0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#11 0x00002aaaac80ec95 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#12 0x00002aaaac810426 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#13 0x00002aaaac813c61 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#14 0x00002aaaac7fe8d0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#15 0x00002aaaac80ec95 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#16 0x00002aaaac810426 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#17 0x00002aaaac8107b3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#18 0x00002aaaab007bb7 in _gtk_button_set_depressed () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x00002aaaac7fe...

[Geert Altena (ge2rt)]

Note: the above backtrace is with
_enabled_ /desktop/gnome/interface/accessibility
and
_enabled_ /apps/metacity/general/reduced_resources

Note2: It may not be a Synaptic specific bug as e.g. gnome-terminal can also be crashed in a similar way. See http://bugzilla.gnome.org/show_bug.cgi?id=329702

[essexman (ralphsmail)]

Jeff250

Thanks, but this thread http://ubuntuforums.org/showthread.php?t=124951
was one of the fixes I had tried.

I test Dapper but I run my day-to-day on Breezy, so I regularly reboot.
I'll reboot and try to make the backtrace report

[essexman (ralphsmail)]

Synaptic now works - may be today's upgrade (?), I have made no other changes except daily upgrade.

gdb gives no backtrace and programme exited normally.

Now I know how to post a bug.

Thanks for your help folks

[Jeffrey Knockel (jeff250)]

Unfortunately, the bug is still there if
/desktop/gnome/interface/accessibility
is enabled.

Here are my startup messages:
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
GTK Accessibility Module initialized

Here's the backtrace:
(gdb) backtrace
#0 0xb7811c87 in g_logv () from /usr/lib/libglib-2.0.so.0
#1 0xb7811f44 in g_log () from /usr/lib/libglib-2.0.so.0
#2 0xb7811fb0 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#3 0xb720a5e9 in gail_tree_view_new ()
   from /usr/lib/gtk-2.0/modules/libgail.so
#4 0xb780ba62 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#5 0xb7809747 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#6 0xb780c806 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#7 0xb780cc8e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8 0xb7d59b79 in gtk_main_iteration () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x08077f95 in std::__introsort_loop<__gnu_cxx::__normal_iterator<std::string*, std::vector<std::string, std::allocator<std::string> > >, int> ()
#10 0x08081f9c in std::__introsort_loop<__gnu_cxx::__normal_iterator<std::string*, std::vector<std::string, std::allocator<std::string> > >, int> ()
#11 0xb7886663 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#12 0xb7879798 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#13 0xb7889715 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#14 0xb788b238 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#15 0xb788e730 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#16 0xb7dfe22e in gtk_tool_button_get_type () from /usr/lib/libgtk-x11-2.0.so.0
#17 0xb7886663 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0

[essexman (ralphsmail)]

Yes - Bug is still ther when Accessability is checked.

Following report generated by gdb:
From: Ralph <email address hidden>
To: <email address hidden>
X-Mailer: bug-buddy 2.13.0
Subject: Unexpected crash

Distribution: Ubuntu 6.04 (dapper)
Package: gnome-applets
Severity: critical
Version: GNOME2.13.90 2.13.x
Gnome-Distributor: Ubuntu
Synopsis: Unexpected crash
Bugzilla-Product: gnome-applets
Bugzilla-Component: trash applet
Bugzilla-Version: 2.13.x
BugBuddy-GnomeVersion: 2.0 (2.13.3)
Description:
Description of the crash:
after installing apps on Ubuntu Dapper Flt 3, used killall gnome-panel
to refresh menu

Steps to reproduce the crash:
1.
2.
3.

Expected Results:

How often does this happen?

Additional Information:

Debugging Information:

Backtrace was generated from '/usr/libexec/trashapplet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223522624 (LWP 5265)]
[New Thread -1226126416 (LWP 5266)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debuggi...

[Pierre Slamich (pierre-slamich)]

Same problem on 02/21/06 on a fresh Dapper upgrade (from Breezy,via Internet)
Interestingly enough i could install part of the updates thanks to update notifier..

[Pierre Slamich (pierre-slamich)]

this is my gdb output i've removed a few (no debugging symbols found) for convenience

Starting program: /usr/sbin/synaptic
(no debugging symbols found)
(.......)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1221658944 (LWP 20356)]
(no debugging symbols found)
(.........)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou répertoire de ce type
GTK Accessibility Module initialized

(no debugging symbols found)
(no debugging symbols found)

** ERROR **: file gailtreeview.c: line 3604 (garbage_collect_cell_data): assertion failed: (GAIL_IS_TREE_VIEW (data))
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1221658944 (LWP 20356)]
0xffffe410 in __kernel_vsyscall ()

[Michael Vogt (mvo)]

Thanks, I just tried to reproduce it (setting accessability=true) and it seems to be working here. Is this still a problem on dapper for others?

Thanks,
 michael

[Alexandre Otto Strube (surak)]

essexman, can you please give us some update on this bug? I can't reproduce it here anymore with latest dapper.

[essexman (ralphsmail)]

I've just tried it.
Enable Assistive technology - Synaptic crashes.
Disable again - then install gok with Synaptic
Then Enable Assistive technology - Synaptic works.

Without gok installed the Assistive technology are greyed out. With gok installed the Assistive technology are available but do not have to be checked.

So maybe gok could be installed by default?

[Michael Vogt (mvo)]

Hm, I just tried to reproduce this on a current dapper and was unable to. I first removed gok and then enabled assistive technology - but no crash. Could you please test it again (and if it crashs check if the crash produces a similar backtrace)? I have a idea for a quick-n-dirty fix but if it is already fixed in libgail even better.

[Daniel Holbach (dholbach)]

Can't reproduce either.

[Michael Vogt (mvo)]

I mark this as fix commited because two people where unable to reproduce it. If it still happens, please reopen.

[essexman (ralphsmail)]

Agreed.
Looks OK now - I have retested with both a clean beta2 install and an upgraded breezy.