Summary: | net-im/pidgin-2.7.1-r1 does not work when executed, does not appear. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Francisco Javier Pinto <javiget> |
Component: | Current packages | Assignee: | Gentoo Net-im project <net-im> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | seraph |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | log of pidgin -d |
Description
Francisco Javier Pinto
2010-07-13 20:02:08 UTC
if: javi@shark ~ $ cd .purple/ javi@shark ~/.purple $ ls accels accounts.xml blist.xml certificates icons logs prefs.xml smileys status.xml javi@shark ~/.purple $ rm -rf * javi@shark ~/.purple $ rm -rf .* rm: cannot remove directory: «.» rm: cannot remove directory: «..» javi@shark ~/.purple $ cd .. javi@shark ~ $ rmdir .purple/ and run pidgin. pidgin works again but erases the accounts Are you able to reproduce this problem with 2.7.2? yes, equal. I have found that if I close the program with "quit", the process ends ok, and pidgin starts up again ok. but if I close with "x" of the window, the process continues (ps aux | grep pidgin) confirm. And even then: kill "process number". It does not work until to delete the directory. (In reply to comment #3) > but if I close with "x" of the window, the process continues (ps aux | grep > pidgin) confirm. Hm, I think this is expected behavior. Pressing 'X' just makes main window invisible, but you should be able to see pidgin icon in tray window and new messages should arrive. Do you see pidgin icon in tray?(In reply to comment #3) > And even then: kill "process number". > It does not work until to delete the directory. I don't understood this. Does this mean that even after you kill pidgin and there will be no pidgin processes available you are unable to start pidgin until you delete ~/.purple/ directory? Now, could you try to run pidgin from console like this: $ pidgin -d and attach output here? Created attachment 239843 [details]
log of pidgin -d
Comment: I close program with "quit" and proccess no finish. 1- I have ldxe, and when i press "x" in any program, this program terminate. 2- Yes. 3. log of pidgin -d when pidgin Window does not appear : attachment Summary: pidgin close sometimes the process is not finish. and when you open pidgin, the process always exists but no program window appears, but yes windows of messages. rm -rf in .purpple directory and pidgin work properly again. lxde fail? pidgin fail? I think this gives a hint of the error? (20:28:14) docklet: GTK+ created (20:28:14) util: Reading file blist.xml from directory /home/javi/.purple (20:28:14) pounce: Error reading pounces: Falló al abrir el archivo «/home/javi/.purple/pounces.xml»: No existe el fichero o el directorio (20:28:14) ui_main: Failed to load the default window icon (scalablepx version)! (20:28:14) Session Management: No SESSION_MANAGER found, aborting. (20:28:20) util: Writing file prefs.xml to directory /home/javi/.purple (20:28:20) util: Writing file /home/javi/.purple/prefs.xml (20:28:20) util: Writing file accounts.xml to directory /home/javi/.purple (20:28:20) util: Writing file /home/javi/.purple/accounts.xml Such errors are in lot's of reports upstream and nobody told this cause an error. Personally, I don't see anything evident in log. Probably anybody else will? Olivier is our pidgin guru but he is currently away... ) (In reply to comment #6) > 1- I have ldxe, and when i press "x" in any program, this program terminate. Window manager just sends some event to program. Program free to choose what to do with such event. But again, do you have pidgin icon in tray? > 2- Yes. 'Yes.' what? :) And few other ideas: have you tried to wait long enough (1-3 minutes)? What happened after "(19:24:38) msn: S: NS 000: QNG 40", was CPU busy doing something? If you start with empty profile and add your account another time will pidgin hang? Will you able to close/start it few times? Try to localize problem somehow. May be if you attach gdb to running process (remember you need symbols to get something useful from gdb output http://www.gentoo.org/proj/en/qa/backtraces.xml (rebuild at least glib/gtk+/pidgin/libxml2 with symbols)) and show us backtrace... >Window manager just sends some event to program. Program free to choose what to do with such event. But again, do you have pidgin icon in tray? No, no icon of pidgin, alt+tab = no pidgin show. >I don't understood this. Does this mean that even after you kill pidgin and there will be no pidgin processes available you are unable to start pidgin until you delete ~/.purple/ directory? Yes, if I don't delete directory pidgin not run again. >have you tried to wait long enough (1-3 minutes)? What happened after "(19:24:38) msn: S: NS 000: QNG 40", was CPU busy doing something? No problem of cpu usage, cpu is idle. >If you start with empty profile and add your account another time will pidgin hang? Will you able to close/start it few times? if I launch pidgin and pulse close, and not add, this window close but pidgin program no show. ok, i read and proved http://www.gentoo.org/proj/en/qa/backtraces.xml I had an issue with Pidgin quite similar to this, and probably related. Since I upgraded to 2.7.*, the main window of Pidgin would often fail to appear on startup. It seems that Pidgin 2.7.* expects some sort of system tray to be present, but not every WM supplies one by default. Window Maker, for example, does not. I was able to solve my problem by installing wmsystray. Pidgin appears there and clicking it opens the main window again. close bug, fails mainly when close pidgin with "x" and not with friends/quit I think this bug is pidgin / lxde and not gentoo. (In reply to comment #11) > It seems that Pidgin 2.7.* expects some sort of system tray to be present, but > not every WM supplies one by default. Window Maker, for example, does not. > > I was able to solve my problem by installing wmsystray. Pidgin appears there > and clicking it opens the main window again. Yup, I think this is a problem. Guys, please, report this issue upstream, since pidgin should detect that there is no tray available and avoid hiding in such case. Reopening bug to close with proper resolution. BTW, if once upstream bug report will be open, drop an URL here, please. Aaaargh! All old Pidgin-Version have been removed last week.. now you are FORCED to use the new pidgin-versions which don't work if you dont have a system-tray..>>FORCED<< to have a System tray!?? Are the pidgin-people mainly developing for full-blown crap-window-manager?? I'm switching to Psi.. Have you reported this upstream as was requested long time ago? If you do nothing I'm unable to help, since everything works find here. Old versions have security problems and thus were removed. (In reply to comment #16) > Have you reported this upstream as was requested long time ago? Yes > If you do nothing I'm unable to help, since everything works find here. Old versions have > security problems and thus were removed. Well..the solution is in short: disable tray-hiding entirely. But if Pidgin is allready gone, you have to edit prefs.xml... Full Bug Report: http://developer.pidgin.im/ticket/12824 And this bug was fixed in 2.7.8. Changing resolution accordingly. |