I just upgraded my Windows XP Pro machine to Vista Business (legit copy, fyi) and now when I open Gaim 2.0b6, it immediately crashes. I was able to use Gaim on a fresh-install of Vista on a different machine, but doesn't work on the upgraded box. Are there config files somewhere that may be causing the problem or perhaps a corrupted .dll? The error message is no more than a 'this program had a problem starting, close the program?' type message.
Any help would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That was very helpful, thanks - the problem was with the 'mystatusbox' plugin causing Gaim to crash. I'll still include the logfile below for future reference:
-------------------
Error occured on Friday, January 26, 2007 at 12:50:19.
C:\Program Files\Gaim\gaim.exe caused an Access Violation at location 65f416f1 in module C:\Program Files\Gaim\plugins\mystatusbox.dll Reading from location 00000038.
Registers:
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=012f99e0
eip=65f416f1 esp=0022f6d0 ebp=0022f708 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210246
Third party plugins are the first thing to check when seeing crashes after upgrading.
Upgrading that plugin to a version designed for beta6 should fix the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just upgraded my Windows XP Pro machine to Vista Business (legit copy, fyi) and now when I open Gaim 2.0b6, it immediately crashes. I was able to use Gaim on a fresh-install of Vista on a different machine, but doesn't work on the upgraded box. Are there config files somewhere that may be causing the problem or perhaps a corrupted .dll? The error message is no more than a 'this program had a problem starting, close the program?' type message.
Any help would be appreciated.
Follow the instructions at: http://gaim.sourceforge.net/win32#debug to obtain a crash report.
That was very helpful, thanks - the problem was with the 'mystatusbox' plugin causing Gaim to crash. I'll still include the logfile below for future reference:
-------------------
Error occured on Friday, January 26, 2007 at 12:50:19.
C:\Program Files\Gaim\gaim.exe caused an Access Violation at location 65f416f1 in module C:\Program Files\Gaim\plugins\mystatusbox.dll Reading from location 00000038.
Registers:
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=012f99e0
eip=65f416f1 esp=0022f6d0 ebp=0022f708 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210246
Call stack:
65F416F1 C:\Program Files\Gaim\plugins\mystatusbox.dll:65F416F1 attach_per_account_boxes C:/cygwin/home/jbailey/gaim-2.0.0beta5/gtk/plugins/gaim-plugin_pack-1.0beta5/mystatusbox/mystatusbox.c:188
65F41CEF C:\Program Files\Gaim\plugins\mystatusbox.dll:65F41CEF plugin_load C:/cygwin/home/jbailey/gaim-2.0.0beta5/gtk/plugins/gaim-plugin_pack-1.0beta5/mystatusbox/mystatusbox.c:442
68A227E9 C:\Program Files\Gaim\libgaim.dll:68A227E9 gaim_plugin_load c:/devel/gaim-devel/gaim-2.0.0beta6/libgaim/plugin.c:588
68A23D5C C:\Program Files\Gaim\libgaim.dll:68A23D5C gaim_plugins_load_saved c:/devel/gaim-devel/gaim-2.0.0beta6/libgaim/plugin.c:1279
62083A4F C:\Program Files\Gaim\gtkgaim.dll:62083A4F gaim_main c:/devel/gaim-devel/gaim-2.0.0beta6/gtk/gtkmain.c:724
004019A7 C:\Program Files\Gaim\gaim.exe:004019A7 WinMain c:/devel/gaim-devel/gaim-2.0.0beta6/gtk/win32/win_gaim.c:551
0040207A C:\Program Files\Gaim\gaim.exe:0040207A WinMain c:/devel/gaim-devel/gaim-2.0.0beta6/gtk/win32/win_gaim.c:244
00401237 C:\Program Files\Gaim\gaim.exe:00401237
004012A8 C:\Program Files\Gaim\gaim.exe:004012A8
75DE3833 C:\Windows\system32\kernel32.dll:75DE3833 BaseThreadInitThunk
76FFA9BD C:\Windows\system32\ntdll.dll:76FFA9BD LdrInitializeThunk
I forgot to mention: removing the mystatusbox.dll file from the plugins directory was the resolution.
Third party plugins are the first thing to check when seeing crashes after upgrading.
Upgrading that plugin to a version designed for beta6 should fix the problem.