|
2010-08-08
, 19:13
|
Posts: 20 |
Thanked: 2 times |
Joined on Jun 2010
|
#612
|
|
2010-08-09
, 00:14
|
Posts: 6 |
Thanked: 0 times |
Joined on Apr 2010
|
#613
|
Segmentation fault means one of the libraries that witter uses did something bad with memory. In theory as a pure python app there is nothing I can do to cause a segmentation fault, so it's just that one of the libs I'm using has a bug.
I see this occasionally, but if you;re getting it every time, something very strange is happening. I guess you could try removing all the witter config files and cache files. but I have no idea why that would fix the issue.
does it give the same output every time you run it?
|
2010-08-09
, 09:19
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#614
|
Thanks for getting back so fast!
I've ran it about ten times or so and for all but one time it gave me that response. That other time, Witter tried to load continuosly; meaning the loading circle kept in motion. When tried to close, it responded with 'witter not responding'. Should I bother removing all config and cache files?
|
2010-08-09
, 11:57
|
Posts: 6 |
Thanked: 0 times |
Joined on Apr 2010
|
#615
|
|
2010-08-09
, 12:08
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#616
|
I can't seem to find these files or folders. I didn't find anything beginning with .witter. I think I'm looking in the wrong place. =s
The Following User Says Thank You to dwould For This Useful Post: | ||
|
2010-08-09
, 14:12
|
Posts: 6 |
Thanked: 0 times |
Joined on Apr 2010
|
#617
|
you need to do this from an x-term
rm -rf .witter*
be VERY CAREFUL executing this command. there is NO SPACE between the .witter and the *. if you accidentally do rm -rf * or rm -rf .witter * then you will completely erase everything in your home folder.
I take no responsibility for anything you do to your device.
Run correctly that will remove everything that witter stores in terms of state, and when you start it again it will be effectively the 'first time' it thinks it's run.
I would still be slightly surprised if this fixes segfault issues, though it might point the finger at image processing code.
|
2010-08-09
, 15:24
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#618
|
IT WORKED! WOW! Thank you SO much! I was beginning to die without Witter. It's my most used application. Even more than Conversations and Phone. =D
|
2010-08-12
, 21:23
|
Posts: 185 |
Thanked: 49 times |
Joined on Apr 2010
@ The Netherlands
|
#619
|
|
2010-08-12
, 21:31
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#620
|
Nice new features in the update. Only the width of the app now doens't fit the phone screen. Can you fix that?
I see this occasionally, but if you;re getting it every time, something very strange is happening. I guess you could try removing all the witter config files and cache files. but I have no idea why that would fix the issue.
does it give the same output every time you run it?
----------
N900
http://danielwould.wordpress.com
Check out Witter, a twitter client for N900
http://danielwould.wordpress.com/witter
If Witter isn't working for you, eg crashes/doesn't start, gives errors etc etc. Please run it from x-term using:
run-standalone.sh python2.5 /opt/witter/witter.py
This will generate diagnostic output. Without this I cannot help you.