设为首页收藏本站

LinuxSir.cn，穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
LinuxSir.cn，穿越时空的Linuxsir!»论坛 › Linux 发行版讨论区 —— LinuxSir.cn › Debian Linux › linux 下的飞信2010年8月2日更新 Fedora000特供V4版本。 ...
1 ...242526272829303132... 76下一页
返回列表 发新帖
楼主: gradetwo

linux 下的飞信2010年8月2日更新 Fedora000特供V4版本。 解决飞信协议升级问题

[复制链接]
CatOO
发表于 2008-2-26 10:17:43 | 显示全部楼层
正在使用 虽然还有点小问题 不过万分感谢楼主
回复 支持 反对

使用道具 举报

snrreihc
发表于 2008-2-26 10:54:02 | 显示全部楼层
太谢谢了!牛人
回复 支持 反对

使用道具 举报

JackyBox
发表于 2008-2-26 12:31:02 | 显示全部楼层
这两天我发飞信怎么手机收不到了，大家有没有这个问题
回复 支持 反对

使用道具 举报

发表于 2008-2-26 17:24:30 | 显示全部楼层
在我这台lenovo的机器运行不了。
一启用fetion帐号，pidgin就自动退出。

机器配置是
AMD64 ubuntu 7.10 pidgin2.3.1-1~getdeb1
cpu:Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz（4核）
内存: 4G
显卡: ATI Technologies Inc RV516 [Radeon X1550 Series]





  1. pidgin
  2. Pidgin 2.3.1 has segfaulted and attempted to dump a core file.
  3. This is a bug in the software and has happened through
  4. no fault of your own.

  6. If you can reproduce the crash, please notify the developers
  7. by reporting a bug at:
  8. http://developer.pidgin.im/simpleticket/

  10. Please make sure to specify what you were doing at the time
  11. and post the backtrace from the core file.  If you do not know
  12. how to get the backtrace, please read the instructions at
  13. http://developer.pidgin.im/wiki/GetABacktrace

  15. If you need further assistance, please IM either SeanEgn or
  16. LSchiere (via AIM).  Contact information for Sean and Luke
  17. on other protocols is at
  18. http://developer.pidgin.im/wiki/DeveloperPages
  19. 忽略 (core dumped)
  20. lijt@lijt-buptnu:~$
复制代码




在另外一台2Gram,amd 2200+ amd64 ubuntu 7.10的机器上运行很正常。
回复 支持 反对

使用道具 举报

tjpm
发表于 2008-2-27 10:31:58 | 显示全部楼层
非常感谢LZ的贡献阿
回复 支持 反对

使用道具 举报

 楼主| 发表于 2008-2-27 10:34:11 | 显示全部楼层
Post by lijiangt;1820303
在我这台lenovo的机器运行不了。
一启用fetion帐号，pidgin就自动退出。

机器配置是
AMD64 ubuntu 7.10 pidgin2.3.1-1~getdeb1
cpu:Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz（4核）
内存: 4G
显卡: ATI Technologies Inc RV516 [Radeon X1550 Series]





  1. pidgin
  2. Pidgin 2.3.1 has segfaulted and attempted to dump a core file.
  3. This is a bug in the software and has happened through
  4. no fault of your own.

  6. If you can reproduce the crash, please notify the developers
  7. by reporting a bug at:
  8. http://developer.pidgin.im/simpleticket/

  10. Please make sure to specify what you were doing at the time
  11. and post the backtrace from the core file.  If you do not know
  12. how to get the backtrace, please read the instructions at
  13. http://developer.pidgin.im/wiki/GetABacktrace

  15. If you need further assistance, please IM either SeanEgn or
  16. LSchiere (via AIM).  Contact information for Sean and Luke
  17. on other protocols is at
  18. http://developer.pidgin.im/wiki/DeveloperPages
  19. 忽略 (core dumped)
  20. lijt@lijt-buptnu:~$
复制代码




在另外一台2Gram,amd 2200+ amd64 ubuntu 7.10的机器上运行很正常。

推荐你用源代码编译下，如果还有问题可以调试跟踪下。
回复 支持 反对

使用道具 举报

发表于 2008-2-27 12:34:13 | 显示全部楼层
不太会用gdb, 我尝试着用了一下，不知道下面的输出信息有没有作用，我一会儿在重新编译试试。


  2. lijt@lijt-buptnu:~$  gdb pidgin
  3. GNU gdb 6.6-debian
  4. Copyright (C) 2006 Free Software Foundation, Inc.
  5. GDB is free software, covered by the GNU General Public License, and you are
  6. welcome to change it and/or distribute copies of it under certain conditions.
  7. Type "show copying" to see the conditions.
  8. There is absolutely no warranty for GDB.  Type "show warranty" for details.
  9. This GDB was configured as "x86_64-linux-gnu"...
  10. (no debugging symbols found)
  11. Using host libthread_db library "/lib/libthread_db.so.1".
  12. (gdb) run
  13. Starting program: /usr/bin/pidgin
  14. (no debugging symbols found)
  15. (no debugging symbols found)
  16. (no debugging symbols found)
  17. (no debugging symbols found)
  18. (no debugging symbols found)
  19. (no debugging symbols found)
  20. (no debugging symbols found)
  21. (no debugging symbols found)
  22. (no debugging symbols found)
  23. (no debugging symbols found)
  24. (no debugging symbols found)
  25. (no debugging symbols found)
  26. (no debugging symbols found)
  27. (no debugging symbols found)
  28. (no debugging symbols found)
  29. (no debugging symbols found)
  30. (no debugging symbols found)
  31. (no debugging symbols found)
  32. (no debugging symbols found)
  33. (no debugging symbols found)
  34. [Thread debugging using libthread_db enabled]
  35. [New Thread 46939100363712 (LWP 6434)]
  36. (no debugging symbols found)
  37. (no debugging symbols found)
  38. ---Type <return> to continue, or q <return> to quit---
  39. (no debugging symbols found)
  40. (no debugging symbols found)
  41. (no debugging symbols found)
  42. (no debugging symbols found)
  43. (no debugging symbols found)
  44. (no debugging symbols found)
  45. (no debugging symbols found)
  46. (no debugging symbols found)
  47. (no debugging symbols found)
  48. (no debugging symbols found)
  49. (no debugging symbols found)
  50. (no debugging symbols found)
  51. (no debugging symbols found)
  52. (no debugging symbols found)
  53. (no debugging symbols found)
  54. (no debugging symbols found)
  55. (no debugging symbols found)
  56. (no debugging symbols found)
  57. (no debugging symbols found)
  58. (no debugging symbols found)
  59. (no debugging symbols found)
  60. (no debugging symbols found)
  61. (no debugging symbols found)
  62. ---Type <return> to continue, or q <return> to quit---
  63. (no debugging symbols found)
  64. (no debugging symbols found)
  65. (no debugging symbols found)
  66. (no debugging symbols found)
  67. (no debugging symbols found)
  68. (no debugging symbols found)
  69. (no debugging symbols found)
  70. (no debugging symbols found)
  71. (no debugging symbols found)
  72. (no debugging symbols found)
  73. (no debugging symbols found)
  74. (no debugging symbols found)
  75. (no debugging symbols found)
  76. (no debugging symbols found)
  77. (no debugging symbols found)
  78. (no debugging symbols found)
  79. (no debugging symbols found)
  80. (no debugging symbols found)
  81. (no debugging symbols found)
  82. (no debugging symbols found)
  83. (no debugging symbols found)
  84. (no debugging symbols found)
  85. (no debugging symbols found)
  86. ---Type <return> to continue, or q <return> to quit---
  87. (no debugging symbols found)
  88. (no debugging symbols found)
  89. (no debugging symbols found)
  90. (no debugging symbols found)
  91. (no debugging symbols found)
  92. (no debugging symbols found)
  93. (no debugging symbols found)
  94. (no debugging symbols found)
  95. (no debugging symbols found)
  96. (no debugging symbols found)
  97. (no debugging symbols found)
  98. (no debugging symbols found)
  99. (no debugging symbols found)
  100. (no debugging symbols found)
  101. (no debugging symbols found)
  102. (no debugging symbols found)
  103. (no debugging symbols found)
  104. (no debugging symbols found)
  105. (no debugging symbols found)
  106. (no debugging symbols found)
  107. (no debugging symbols found)
  108. (no debugging symbols found)
  109. (no debugging symbols found)
  110. ---Type <return> to continue, or q <return> to quit---
  111. (no debugging symbols found)
  112. (no debugging symbols found)
  113. (no debugging symbols found)
  114. (no debugging symbols found)
  115. (no debugging symbols found)
  116. (no debugging symbols found)
  117. (no debugging symbols found)
  118. (no debugging symbols found)
  119. (no debugging symbols found)
  120. (no debugging symbols found)
  121. (no debugging symbols found)
  122. (no debugging symbols found)
  123. (no debugging symbols found)
  124. (no debugging symbols found)
  125. (no debugging symbols found)
  126. (no debugging symbols found)
  127. (no debugging symbols found)
  128. (no debugging symbols found)
  129. (no debugging symbols found)
  130. (no debugging symbols found)
  131. (no debugging symbols found)
  132. (no debugging symbols found)
  133. (no debugging symbols found)
  134. ---Type <return> to continue, or q <return> to quit---
  135. (no debugging symbols found)
  136. (no debugging symbols found)
  137. (no debugging symbols found)
  138. (no debugging symbols found)
  139. (no debugging symbols found)
  140. (no debugging symbols found)
  141. (no debugging symbols found)
  142. (no debugging symbols found)
  143. (no debugging symbols found)
  144. (no debugging symbols found)
  145. (no debugging symbols found)
  146. (no debugging symbols found)
  147. (no debugging symbols found)
  148. (no debugging symbols found)
  149. (no debugging symbols found)
  150. (no debugging symbols found)
  151. (no debugging symbols found)
  152. (no debugging symbols found)
  153. (no debugging symbols found)
  154. (no debugging symbols found)
  155. (no debugging symbols found)
  156. (no debugging symbols found)
  157. (no debugging symbols found)
  158. ---Type <return> to continue, or q <return> to quit---
  159. (no debugging symbols found)
  160. (no debugging symbols found)
  161. (no debugging symbols found)
  162. (no debugging symbols found)
  163. (no debugging symbols found)
  164. (no debugging symbols found)
  165. (no debugging symbols found)
  166. (no debugging symbols found)
  167. (no debugging symbols found)
  168. (no debugging symbols found)
  169. (no debugging symbols found)
  170. (no debugging symbols found)
  171. (no debugging symbols found)
  172. (no debugging symbols found)
  173. (no debugging symbols found)
  174. (no debugging symbols found)
  175. (no debugging symbols found)
  176. (no debugging symbols found)
  177. (no debugging symbols found)
  178. (no debugging symbols found)
  179. (no debugging symbols found)
  180. (no debugging symbols found)
  181. (no debugging symbols found)
  182. ---Type <return> to continue, or q <return> to quit---
  183. (no debugging symbols found)
  184. (no debugging symbols found)
  185. (no debugging symbols found)
  186. (no debugging symbols found)
  187. (no debugging symbols found)
  188. (no debugging symbols found)
  189. [New Thread 1082132816 (LWP 6437)]
  190. [New Thread 1090525520 (LWP 6494)]
  191. [New Thread 1098918224 (LWP 6495)]
  192. [New Thread 1107310928 (LWP 6496)]
  193. [New Thread 1115703632 (LWP 6497)]
  194. [Thread 1115703632 (LWP 6497) exited]
  195. [Thread 1107310928 (LWP 6496) exited]
  196. [Thread 1098918224 (LWP 6495) exited]
  197. [Thread 1090525520 (LWP 6494) exited]

  199. Program received signal SIGSEGV, Segmentation fault.
  200. [Switching to Thread 46939100363712 (LWP 6434)]
  201. 0x00002ab0d70a3be9 in purple_account_get_proxy_info ()
  202.    from /usr/lib/libpurple.so.0
  203. (gdb) c
  204. Continuing.
  205. Pidgin 2.3.1 has segfaulted and attempted to dump a core file.
  206. This is a bug in the software and has happened through
  207. no fault of your own.

  209. If you can reproduce the crash, please notify the developers
  210. by reporting a bug at:
  211. http://developer.pidgin.im/simpleticket/

  213. Please make sure to specify what you were doing at the time
  214. and post the backtrace from the core file.  If you do not know
  215. how to get the backtrace, please read the instructions at
  216. http://developer.pidgin.im/wiki/GetABacktrace

  218. If you need further assistance, please IM either SeanEgn or
  219. LSchiere (via AIM).  Contact information for Sean and Luke
  220. on other protocols is at
  221. http://developer.pidgin.im/wiki/DeveloperPages

  223. Program received signal SIGABRT, Aborted.
  224. 0x00002ab0d7f4a765 in raise () from /lib/libc.so.6
  225. (gdb) c
  226. Continuing.

  228. (gdb)
复制代码
回复 支持 反对

使用道具 举报

发表于 2008-2-27 13:02:05 | 显示全部楼层
这两天好像发出去的消息手机收不到。
回复 支持 反对

使用道具 举报

发表于 2008-2-28 13:19:54 | 显示全部楼层
为什么其他版本的pidgin就用不了呢？？？比如2.3.0？？
回复 支持 反对

使用道具 举报

发表于 2008-3-1 15:06:36 | 显示全部楼层
我的是2.3.1版的，下了插件用不了
回复 支持 反对

使用道具 举报

下一页 »
1 ...242526272829303132... 76下一页
返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

本版积分规则

快速回复 返回顶部 返回列表