GNOME Bugzilla – Bug 65068
Switching the setting of the toolbar buttons crash galeon after two or three switches
Last modified: 2004-12-22 21:47:04 UTC
Synopsis: Switching the setting of the toolbar buttons crash galeon after two or three switches
Bugzilla-Component: User interface
To reproduce, open the preference dialog at the UI tab. In the toolbar
option menu, select 'icon & text by side', then apply, then select 'icon
& text under' then apply, and again. after one or two, galeon will
[New Thread 1024 (LWP 32426)]
[New Thread 2049 (LWP 32432)]
[New Thread 1026 (LWP 32433)]
[New Thread 2051 (LWP 32434)]
[New Thread 3076 (LWP 32437)]
0x2b40ae39 in __wait4 () from /lib/libc.so.6
(Thread 1024 (LWP 32426))
------- Bug moved to this database by firstname.lastname@example.org 2001-11-21 18:40 -------
Reassigning to the default owner of the component, email@example.com.
The same bug seems to appears in CVS head (galeon 1.1). This is why i
added it in version details.
i cant reproduce this
its probably realated to the toolbar arrangement(what and where is
in/on it) could you please give us the toolbar arrangement using
which you can reproduce this
Yes. I attach two shots, one of the preference window and one of the
Created attachment 6057 [details]
Preference panel opened on UI tab
Created attachment 6058 [details]
Toolbar itself with 'by side' text
Created attachment 6059 [details]
and text under buttons
I tried by removing some of the buttons to get the basic ones. The
crash do not occurs anymore...
By adding back all buttons (according to the shots), the crash does
not appear again. I think it could be because of a desynchronization
between the preference file and the galeon version (buttons in
toolbars is not a setting I change everyday). By removing then adding
again the buttons, the bug origin might have been removed also ...
What do you think ?
i think i cant think(at least now) :) will leave the thinking to marco
(or somebody else)
toolbar code has changed a lot since this bug was filled, also noone
can reproduce, so marking this is as fixed. please reopen if someone
can still reproduce.