On 01/01/2012 08:53 AM, John B. Egger wrote: > New problem with with new year... Clicking the Xlog desktop icon gets it > to bounce for a while, then nothing. Console "xlog" gives "Segmentation > fault." Following a suggestion from Google, I tried gdb: > >> (gdb) run xlog >> Starting program: /usr/bin/xlog xlog >> [Thread debugging using libthread_db enabled] >> >> ** (xlog:2457): WARNING **: Can not open log "xlog" > But xlog then starts, with the QSO pane but a warning that there was a > problem loading one of my logs. If I simply use "Open" and select my new > Log2012 it pops right up, as does (when I "Open" it) Log2011. I've > entered test data into them both and saved them, then quit and restarted > Xlog. No fix --- they're accessible only from gdb with each log opened > individually. (Hamlib polling and ctrl-K work fine.) > > Any suggestions? All I did last night was create a new log (Log2012) and > use adif to move about 5 QSOs from Log2011 to Log2012. This morning I > did note that Log2012 was owned by root, not john. I changed that... > didn't fix the problem. Also uninstalled xlog 2.0.5 and installed 2.0.3 > on this Kubuntu 10.10 system. > > [Oh... I also installed Google-earth...]
I now have a functioning 2.0.3 running. It seems that when the three logs that I watch are loaded alphabetically, it's OK... but when they're loaded by time of last modification I get the seg fault. Guess I'll stick with 2.0.3 for a while before reinstalling 2.0.5. It's been a little scary not to be able to open my logs :( -- ---John K3GHH Registered Linux User #291592 Kubuntu Maverick Meerkat (10.10) _______________________________________________ Xlog-discussion mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/xlog-discussion
