I have the same exact thing in Win32! I have gone through the whole process, I have tried disabling every plugin I have running, as well as Completely uninstalling GTK+ and Pidgin, and reinstalling, and even renaming and using a fresh .purple directory with all my preferences and such set at default, except for my account. I even tried it on my laptop that's running Kubuntu 7.04, except I dont get the runtime errors, instead Pidgin just closes. Some new thing AIM servers are doing? I hate this, I can't stay logged in on Gaim for more than 15 minutes, and I'm stuck with using plain old AIM :/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wow, I'm sorry to include all this information in my posts and I have to keep adding...I'm at work and keep typing and hitting post when I have to answer to a customer. The problem started for me about 24 hours ago exactly like you guys as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I took a little more time, and decided to try and trace back the proble through the debug window and reviewing its logs, and on both Win32 and Kubuntu 7.04 there are no logs.
In Kubuntu on 2.0 Pidgin build I get a complete crash and exit of Pidgin, if I run it from Terminal window I get this:
"erik@erik-laptop:~$ pidgin
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
Aborted (core dumped)
erik@erik-laptop:~$"
In Win32 on Xp 32bit here are my screen shots. Instead of just exiting, I get these two error messages, then Pidgin closes completely.
<a href="http://erik.warpfactor10.com/pidgin1.JPG">http://erik.warpfactor10.com/pidgin1.JPG</a>
and then
<a href="http://erik.warpfactor10.com/pidgin2.JPG">http://erik.warpfactor10.com/pidgin2.JPG</a>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found the problem. It has nothing to do with Pidgin itself I think... I think it seems to be the CurrentTrack plugin. I saw you said you used CurrentTrack as well, and I use it on my Kubuntu laptop and Win32 Desktop. Disabling the plugin is apparently not enough. Once i actually removed the plugin from my Plugin directory the problem went away. Before I did this, the maxium time I would get before a crash was about 20 minutes, MAX, usually about 5 minutes. I'm currently going on 2 hours with the plugin removed. Apparently a new version was released 2 days ago as well, http://software.johnroark.net/ I'm not sure if they fixed the bug or what, but I have an output from Pidgin finally with the error, before I wasn't running the Debug build (Stupid me!) and that why I wasn't getting an output of the debug code. It happens when CurrentTrack goes to check for an update of itself, you can see in the code, and I think it only started 2 days ago for all of us since the new version was only released 2 days ago! So apparently the CurrentTrack author has to fix either the scripting on his site or the program for when there is an update to CurrentTrack. Here's the output from debug I get.
util: requested to fetch (http://currenttrack.sourceforge.net/update/update.ini), full=0, user_agent=(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1), http11=1
dnsquery: Performing DNS lookup for currenttrack.sourceforge.net
dnsquery: IP resolved for currenttrack.sourceforge.net
proxy: Attempting connection to 66.35.250.209
proxy: Connecting to currenttrack.sourceforge.net:80 with no proxy
proxy: Connection in progress
proxy: Connected to currenttrack.sourceforge.net:80.
util: Request: 'GET /update/update.ini HTTP/1.1
Connection: close
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept: */*
Host: currenttrack.sourceforge.net
'
util: Response headers: 'HTTP/1.1 200 OK
Date: Thu, 24 May 2007 11:50:36 GMT
Server: Apache/1.3.33 (Unix) PHP/4.3.10
Last-Modified: Tue, 22 May 2007 07:31:54 GMT
ETag: "35393f6-7f-46529c6a"
Accept-Ranges: bytes
Content-Length: 127
Connection: close
Content-Type: text/plain
'
util: parsed 127
GLib: gmem.c:154: failed to allocate 2389941944 bytes
I am going to try updating to the latest version of CurrentTrack and see what happens.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Once updating to CurrentTrack 1.2 I have yet to experience the problem, so far half hour, but I'm not sure if they fixed the problem or not since it seems to be only when a newer version than the version of the plugin you are running is out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alright guys... I tracked down the update bug. It is not fixed in 1.2 so I would suggest everyone turn the check for updates option off. Turns out the Pidgin plugin API docs haven't been fully updated and I was passing the wrong args to a pidgin API that is incorrectly documented... but I digress. The fix is in SVN and will be in the next release which you will know about when Pidgin starts crashing ;)
Anyone that is feeling brave and is comfortable building from source can checkout the source and build (easiest from linux).
I downloaded the source, edited the version to think its 1.19 and compiled, installed, and Whammy! I get a popup message asking me to update to 1.2 like I should, no crash. I tried this on my Kubuntu laptop. I used to Cygwin on my Desktop awhile ago.. but alas I got rid of it so I'll just leave my Windows box with auto-update disabled for now. Great work, awsome improvement with version 1.2! Keep up the good work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
just started getting this today. im not actually doing anything in pidgin when it happens. any ideas?
screenshot: http://www.blinque.co.uk/pidgin_runtime.jpg
thought it could be currenttrack but turned that off and its still behaving the same... :(
these are the plugins i have running:
buddy state
extpos
history
idlemaker
message notification
message timestamp formats
offline message emulation
psychic mode
release notification
text replacement
i don't know, but i'm having exactly the same issue, even beginning at the same time. yuck.
I have the same exact thing in Win32! I have gone through the whole process, I have tried disabling every plugin I have running, as well as Completely uninstalling GTK+ and Pidgin, and reinstalling, and even renaming and using a fresh .purple directory with all my preferences and such set at default, except for my account. I even tried it on my laptop that's running Kubuntu 7.04, except I dont get the runtime errors, instead Pidgin just closes. Some new thing AIM servers are doing? I hate this, I can't stay logged in on Gaim for more than 15 minutes, and I'm stuck with using plain old AIM :/
Er whoops refered to Pidgin as Gaim, O:-). I'm running 2.0 Pidgin final on both machines.
Wow, I'm sorry to include all this information in my posts and I have to keep adding...I'm at work and keep typing and hitting post when I have to answer to a customer. The problem started for me about 24 hours ago exactly like you guys as well.
I took a little more time, and decided to try and trace back the proble through the debug window and reviewing its logs, and on both Win32 and Kubuntu 7.04 there are no logs.
In Kubuntu on 2.0 Pidgin build I get a complete crash and exit of Pidgin, if I run it from Terminal window I get this:
"erik@erik-laptop:~$ pidgin
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
Aborted (core dumped)
erik@erik-laptop:~$"
In Win32 on Xp 32bit here are my screen shots. Instead of just exiting, I get these two error messages, then Pidgin closes completely.
<a href="http://erik.warpfactor10.com/pidgin1.JPG">http://erik.warpfactor10.com/pidgin1.JPG</a>
and then
<a href="http://erik.warpfactor10.com/pidgin2.JPG">http://erik.warpfactor10.com/pidgin2.JPG</a>
ok im not alone then. i get exactly the same two error dialogs as erik on win32.
I just started getting the same error about the same time as previous posters. Does anyone know if the developers are aware of this issue?
I found the problem. It has nothing to do with Pidgin itself I think... I think it seems to be the CurrentTrack plugin. I saw you said you used CurrentTrack as well, and I use it on my Kubuntu laptop and Win32 Desktop. Disabling the plugin is apparently not enough. Once i actually removed the plugin from my Plugin directory the problem went away. Before I did this, the maxium time I would get before a crash was about 20 minutes, MAX, usually about 5 minutes. I'm currently going on 2 hours with the plugin removed. Apparently a new version was released 2 days ago as well, http://software.johnroark.net/ I'm not sure if they fixed the bug or what, but I have an output from Pidgin finally with the error, before I wasn't running the Debug build (Stupid me!) and that why I wasn't getting an output of the debug code. It happens when CurrentTrack goes to check for an update of itself, you can see in the code, and I think it only started 2 days ago for all of us since the new version was only released 2 days ago! So apparently the CurrentTrack author has to fix either the scripting on his site or the program for when there is an update to CurrentTrack. Here's the output from debug I get.
util: requested to fetch (http://currenttrack.sourceforge.net/update/update.ini), full=0, user_agent=(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1), http11=1
dnsquery: Performing DNS lookup for currenttrack.sourceforge.net
dnsquery: IP resolved for currenttrack.sourceforge.net
proxy: Attempting connection to 66.35.250.209
proxy: Connecting to currenttrack.sourceforge.net:80 with no proxy
proxy: Connection in progress
proxy: Connected to currenttrack.sourceforge.net:80.
util: Request: 'GET /update/update.ini HTTP/1.1
Connection: close
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept: */*
Host: currenttrack.sourceforge.net
'
util: Response headers: 'HTTP/1.1 200 OK
Date: Thu, 24 May 2007 11:50:36 GMT
Server: Apache/1.3.33 (Unix) PHP/4.3.10
Last-Modified: Tue, 22 May 2007 07:31:54 GMT
ETag: "35393f6-7f-46529c6a"
Accept-Ranges: bytes
Content-Length: 127
Connection: close
Content-Type: text/plain
'
util: parsed 127
GLib: gmem.c:154: failed to allocate 2389941944 bytes
I am going to try updating to the latest version of CurrentTrack and see what happens.
Ding Ding! Problem solved. Others have had this problem as well, http://sourceforge.net/forum/forum.php?thread_id=1740958&forum_id=506117
Once updating to CurrentTrack 1.2 I have yet to experience the problem, so far half hour, but I'm not sure if they fixed the problem or not since it seems to be only when a newer version than the version of the plugin you are running is out.
Alright guys... I tracked down the update bug. It is not fixed in 1.2 so I would suggest everyone turn the check for updates option off. Turns out the Pidgin plugin API docs haven't been fully updated and I was passing the wrong args to a pidgin API that is incorrectly documented... but I digress. The fix is in SVN and will be in the next release which you will know about when Pidgin starts crashing ;)
Anyone that is feeling brave and is comfortable building from source can checkout the source and build (easiest from linux).
svn co https://currenttrack.svn.sourceforge.net/svnroot/currenttrack/trunk/currenttrack currenttrack
cd currenttrack
vi configure.ac [change the version to something lower than 1.2]
./reconf
./configure && make
sudo make install
It's fun I promise
I downloaded the source, edited the version to think its 1.19 and compiled, installed, and Whammy! I get a popup message asking me to update to 1.2 like I should, no crash. I tried this on my Kubuntu laptop. I used to Cygwin on my Desktop awhile ago.. but alas I got rid of it so I'll just leave my Windows box with auto-update disabled for now. Great work, awsome improvement with version 1.2! Keep up the good work.