pidgin crashes during file transfer

Bug #188464 reported by Taka
2
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Ubuntu release: 7.10
pidgin version: 1:2.2.1ubuntu4.1

debug-log entry during crash:
(16:37:15) oscar: Calculating checksum of /home/heil/Desktop/test.txt
(16:37:15) oscar: Checksum of /home/heil/Desktop/test.txt calculated
(16:37:15) network: Listening on port: 5190
(16:37:15) upnp: purple_upnp_set_port_mapping(): couldn't get local ip
(16:37:15) network: Couldn't create UPnP mapping
(16:37:15) util: requested to fetch (/control?WANPPPConnection), full=0, user_agent=((null)), http11=1
(16:37:15) g_log: purple_proxy_connect: assertion `port > 0' failed
(16:37:15) upnp: purple_upnp_set_port_mapping(): Failed HTTP_OK
(null)
(16:37:15) network: Couldn't create UPnP mapping
(16:37:15) stun: using server
(16:37:16) oscar: Sent message to 123456789.

Terminal message after crash: Segmentation fault (core dumped)

ProblemType: Bug
Architecture: i386
Date: Sat Feb 2 22:55:56 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: fglrx
Package: pidgin 1:2.2.1-1ubuntu4.1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/heil
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux FABIAN-HEIL 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
Taka (shayamango) wrote :
Revision history for this message
Marlon Cisternas Milla (mcisternas-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in pidgin:
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
Marlon Cisternas Milla (mcisternas-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in pidgin:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.