I was using 2.0.0beta5 and installed 2.0.0beta6. It's now impossible to display the properties panel for account. When I try to modify the properties for an MSN or Jabber account, gaim crashes instantaneously :/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you look in the c:\Program Files\gaim\plugins\ directory (or something roughly like that) you will probably find a liboscar.dll file, if you then look in the gaim\ directory itself (one level above plugins) you will likely find a second one. The one in the plugins\ directory is an old one and should be moved out of the way (if gaim works once you move it you can then delete it).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-02-28
I'm having the same problem in Linux..but there aren't dups of liboscar in /usr/local/lib/gaim and /usr/local/lib/gaim/plugins (dir doesn't exist). Know of anything else as to why this is happening?
I just tried uninstalling beta5 then re-installing beta6 but it still makes my cpu 100% when trying to open the Account Window.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
gaim taking up 100% of your cpu isn't the same as crashing, and the liboscar issue only happens on Windows (at least that I've ever seen). Does your gaim crash? Or does it just sit there spinning forever? Can you run gaim in gdb and hit ctrl-c when gaim is spinning and see what it is doing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm seeing the same problem on Linux (SUSE 10.1). Anytime I try to edit an account I get a segmentation fault. I do not see 100% CPU though. Any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I actually removed all of /usr/bin/gaim* and /usr/lib/gaim/* before rebuilding beta6 and that seemed to solve my problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-03-01
Etan,
Sorry, you're right. gaim wasn't crashing on me at all. I must have just skipped that part and read about the Account Window having problems..
I tried Ken Ringdahl's suggestion but it still has the same affect of 100CPU.
When running gaim under gdb, waiting it to log into all my accounts, and then hitting Control-A for the Account window, the CPU goes to 100 (approx). I hit Ctrl-C and the printed text under gdb is:
Program received signal SIGINT, Interrupt.
[Switching to Thread 1088041152 (LWP 24665)]
0x4061fdd0 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
Doing Backtrace:
#0 0x4061fdd0 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#1 0x40621048 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#2 0x4061ac50 in gdk_pixbuf_scale () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#3 0x4061ad32 in gdk_pixbuf_scale_simple () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#4 0x0806b564 in set_account (store=0x85f3fb0, iter=0xbf8a3014, account=0x452a3288) at gtkaccount.c:1999
#5 0x0806b8b1 in add_account_to_liststore (account=0x81172a0, user_data=0x0) at gtkaccount.c:2032
#6 0x0806beb3 in create_accounts_list (dialog=0x85f33f8) at gtkaccount.c:2045
#7 0x0806c18c in gaim_gtk_accounts_window_show () at gtkaccount.c:2273
#8 0x4039a848 in gtk_item_factory_get_type () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#9 0x40a035eb in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0
#10 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#11 0x40a06816 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#12 0x40a07e80 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#13 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#14 0x404a578d in gtk_widget_can_activate_accel () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#15 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#16 0x40a06816 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#17 0x40a07bee in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#18 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#19 0x402d2909 in gtk_accel_group_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#20 0x402d3363 in gtk_accel_groups_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#21 0x404bb4b8 in gtk_window_activate_key () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#22 0x404bb52c in gtk_window_activate_key () from /opt/gnome/lib/libgtk-x11-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#23 0x403b3e60 in gtk_marshal_VOID__UINT_STRING () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#24 0x409f6637 in g_cclosure_new_swap () from /opt/gnome/lib/libgobject-2.0.so.0
#25 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#26 0x40a069a7 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#27 0x40a07bee in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#28 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#29 0x404a63b4 in gtk_widget_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#30 0x403b2388 in gtk_propagate_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#31 0x403b26ff in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#32 0x405b8f8a in gdk_screen_get_setting () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#33 0x40a6935c in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#34 0x40a6c7cb in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0
#35 0x40a6cae7 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#36 0x403b1861 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#37 0x080a2cb0 in main (argc=1, argv=0xbf8a6284) at gtkmain.c:817
So I assume it's obviously something to do with the gdk_pixbuf lib. The installed version I have is:
gdk-pixbuf the package is the GTK+ 1.2 version of that library, and unrelated to GTK+ 2. What distribution are you using? What version of gaim? You said gaim hangs when opening the Accounts window? What version of GTK+?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-03-01
opensuse 10.0
gtk: gtk2-2.8.3-4.3
gaim: beta6
I guess I could get the gtk sources and all the src packages and compile it. Is there anything else I can do to find out what's causing this?
This happened to me before and I removed my ~/.gaim (suggestion from the forum) and then re-setup my accounts again (installed beta5 from beta4) and it worked. But after installing beta6, it happened once again..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was using 2.0.0beta5 and installed 2.0.0beta6. It's now impossible to display the properties panel for account. When I try to modify the properties for an MSN or Jabber account, gaim crashes instantaneously :/
If you look in the c:\Program Files\gaim\plugins\ directory (or something roughly like that) you will probably find a liboscar.dll file, if you then look in the gaim\ directory itself (one level above plugins) you will likely find a second one. The one in the plugins\ directory is an old one and should be moved out of the way (if gaim works once you move it you can then delete it).
It works ! Thanks !
I'm having the same problem in Linux..but there aren't dups of liboscar in /usr/local/lib/gaim and /usr/local/lib/gaim/plugins (dir doesn't exist). Know of anything else as to why this is happening?
I just tried uninstalling beta5 then re-installing beta6 but it still makes my cpu 100% when trying to open the Account Window.
gaim taking up 100% of your cpu isn't the same as crashing, and the liboscar issue only happens on Windows (at least that I've ever seen). Does your gaim crash? Or does it just sit there spinning forever? Can you run gaim in gdb and hit ctrl-c when gaim is spinning and see what it is doing?
I'm seeing the same problem on Linux (SUSE 10.1). Anytime I try to edit an account I get a segmentation fault. I do not see 100% CPU though. Any suggestions?
I actually removed all of /usr/bin/gaim* and /usr/lib/gaim/* before rebuilding beta6 and that seemed to solve my problem.
Etan,
Sorry, you're right. gaim wasn't crashing on me at all. I must have just skipped that part and read about the Account Window having problems..
I tried Ken Ringdahl's suggestion but it still has the same affect of 100CPU.
When running gaim under gdb, waiting it to log into all my accounts, and then hitting Control-A for the Account window, the CPU goes to 100 (approx). I hit Ctrl-C and the printed text under gdb is:
Program received signal SIGINT, Interrupt.
[Switching to Thread 1088041152 (LWP 24665)]
0x4061fdd0 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
Doing Backtrace:
#0 0x4061fdd0 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#1 0x40621048 in gdk_pixbuf_rotation_get_type () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#2 0x4061ac50 in gdk_pixbuf_scale () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#3 0x4061ad32 in gdk_pixbuf_scale_simple () from /opt/gnome/lib/libgdk_pixbuf-2.0.so.0
#4 0x0806b564 in set_account (store=0x85f3fb0, iter=0xbf8a3014, account=0x452a3288) at gtkaccount.c:1999
#5 0x0806b8b1 in add_account_to_liststore (account=0x81172a0, user_data=0x0) at gtkaccount.c:2032
#6 0x0806beb3 in create_accounts_list (dialog=0x85f33f8) at gtkaccount.c:2045
#7 0x0806c18c in gaim_gtk_accounts_window_show () at gtkaccount.c:2273
#8 0x4039a848 in gtk_item_factory_get_type () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#9 0x40a035eb in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0
#10 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#11 0x40a06816 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#12 0x40a07e80 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#13 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#14 0x404a578d in gtk_widget_can_activate_accel () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#15 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#16 0x40a06816 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#17 0x40a07bee in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#18 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#19 0x402d2909 in gtk_accel_group_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#20 0x402d3363 in gtk_accel_groups_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#21 0x404bb4b8 in gtk_window_activate_key () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#22 0x404bb52c in gtk_window_activate_key () from /opt/gnome/lib/libgtk-x11-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#23 0x403b3e60 in gtk_marshal_VOID__UINT_STRING () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#24 0x409f6637 in g_cclosure_new_swap () from /opt/gnome/lib/libgobject-2.0.so.0
#25 0x409f6d19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#26 0x40a069a7 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#27 0x40a07bee in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#28 0x40a081f5 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#29 0x404a63b4 in gtk_widget_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#30 0x403b2388 in gtk_propagate_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#31 0x403b26ff in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#32 0x405b8f8a in gdk_screen_get_setting () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#33 0x40a6935c in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#34 0x40a6c7cb in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0
#35 0x40a6cae7 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#36 0x403b1861 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#37 0x080a2cb0 in main (argc=1, argv=0xbf8a6284) at gtkmain.c:817
So I assume it's obviously something to do with the gdk_pixbuf lib. The installed version I have is:
gdk-pixbuf-0.22.0-72.3
gdk-pixbuf-devel-0.22.0-72.3
0.22, looking at the gnome site, is the latest version of pixbuf...
gdk-pixbuf the package is the GTK+ 1.2 version of that library, and unrelated to GTK+ 2. What distribution are you using? What version of gaim? You said gaim hangs when opening the Accounts window? What version of GTK+?
opensuse 10.0
gtk: gtk2-2.8.3-4.3
gaim: beta6
I guess I could get the gtk sources and all the src packages and compile it. Is there anything else I can do to find out what's causing this?
This happened to me before and I removed my ~/.gaim (suggestion from the forum) and then re-setup my accounts again (installed beta5 from beta4) and it worked. But after installing beta6, it happened once again..