OSMO not working/starting in lighthouse pup

[tuxy]

hi.
i want to use osmo for organising contacts and stuff in lighthouse pup but its not working. even in the fresh install on usb.
osmo works in basic puppy linux version with no problems . But i want to use lighthouse . any suggestions ? what should i do ?

[ttuuxxx]

Hi just run osmo from the terminal and it should give you a clue also read /tmp/xerrs.log that might help.
ttuuxxx

[tuxy]

(osmo:11801): Gtk-WARNING **: cannot open display:
<root> ~
and here is the xerrs.log after running the command:(the log was in /tmp/root dir)


X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux Mariner 2.6.30.5 #1 SMP Tue Sep 1 15:48:26 GMT-8 2009 i686
Build Date: 28 November 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 19 10:15:14 2010
(==) Using config file: "/etc/X11/xorg.conf"
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) AIGLX error: dlopen of /usr/X11R7/lib/dri/i915_dri.so failed (/usr/X11R7/lib/dri/i915_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
Synaptics DeviceInit called
SynapticsCtrl called.
expected keysym, got XF86KbdLightOnOff: line 69 of pc
expected keysym, got XF86KbdBrightnessDown: line 70 of pc
expected keysym, got XF86KbdBrightnessUp: line 71 of pc
Synaptics DeviceOn called
expected keysym, got XF86KbdLightOnOff: line 69 of pc
expected keysym, got XF86KbdBrightnessDown: line 70 of pc
expected keysym, got XF86KbdBrightnessUp: line 71 of pc
Warning: Only changing the first 5 of 9 buttons.
/usr/bin/starticewm
usage: absvolume -bg is no longer supported, ignoring.
Try restarting X to pickup new gtk background colour.
6830
IceWM: using /root/.icewm for private configuration files
IceWM: Unknown key name [ in Alt+[
IceWM: Unknown key name ] in Alt+]
test: /usr/share/backgrounds/himalaya_1600x1200.jpg
option: -stretch
stretching: /usr/share/backgrounds/himalaya_1600x1200.jpg
killall: rsaver: no process killed
icewmtray: using /root/.icewm for private configuration files
Using /root/.wbar config file.
Using a Super Bar.
Pathname: /usr/share/audio/login.wav
Device: /dev/dsp
Sampling Rate: 8000 Hz
Mode: Mono
Samples: 3732
Bits: 8

** Message: Error loading saved channels' values !!!

IceWM: Warning: latency: 0.194266
IceWM: Warning: latency: 0.084708
IceWM: Warning: latency: 0.095621
IceWM: Warning: latency: 0.080450
IceWM: Warning: latency: 0.089684
IceWM: Warning: latency: 0.056036
IceWM: Warning: latency: 0.122781
Timeout: file:///usr/share/doc/home.htm
IceWM: Warning: latency: 0.234498
IceWM: Warning: latency: 0.100849
IceWM: Warning: latency: 0.054861
rxvt: XError: Request: 18 . 0, Error: 2
IceWM: Warning: latency: 0.050706
/bin/sh: /usr/bin/esd: No such file or directory

[ttuuxxx]

doesn't look like you ran osmo first, couldn't see anything related, try the terminal.
ttuuxxx

[tuxy]

i installed the basic puppy on the pen drive thru unetbootin.
osmo ran perfectly well on it before making a pupsave file. after making the pupsave file and loading the gooffice sfs on bootup the problem appears again. in terminal on giving OSMO command it replies "segmentation fault"
i deleted the pupsave and osmo worked again.

so what now?

[ttuuxxx]

i installed the basic puppy on the pen drive thru unetbootin.
osmo ran perfectly well on it before making a pupsave file. after making the pupsave file and loading the gooffice sfs on bootup the problem appears again. in terminal on giving OSMO command it replies "segmentation fault"
i deleted the pupsave and osmo worked again.

so what now?

make a new pupsave and see if it stops working again.
ttuuxxx

[tuxy]

yes . i did try that . making another pupsave . didn't work . no osmo.

[ttuuxxx]

yes . i did try that . making another pupsave . didn't work . no osmo.

maybe copy /root/.osmo folder (hidden folder) to your pupsave and see if that works.
ttuuxxx

[tuxy]

osmo is working . here's whet i did.
1.Formatted the pendrive
2.installed lighthouse through unetbootin.
3.copied the /root/.osmo to harddrive.
4.made the pupsave and configured the system.(this time osmo didn't work after reboot)
So deleted the one and tried again with the pupsave and configured again.put the .osmo from/root/ in mounted pupsave's /root dir.
this time it worked after reboot . to be sure i checked doing several reboots. OSMO was working fine.


THANKS a lot ttuuxxx.

[ttuuxxx]

no problem glad I could help, its still strange that the .osmo file wasn't being copied over.
ttuuxxx

[tuxy]

yes . there was a .osmo dir in pupsave root dir but it didn't had all the files in it when compared to the one in the sfs.
ONE MOre Thing .
is there a log file for problems occuring during puppy bootup. IF yes then where is it saved.i need to solve another problem but i need the log for that to post whatever is in the log about the prob.

[tazoc]

Hi tuxy,
The logs can all be found in /var/log/. var/log/BootLogs has links to the bootkernel and bootsysinit and more.

The ones I look at the most are /var/log/rootlogs which is a symlink to /tmp/root/xerrs.log and the other is the Xorg log at /var/log/Xorg.0.log.

If you were looking for xerrs.log in /tmp, it is in a subdirectory /tmp/root because Lighthouse is multi-user and each user including 'root' has his/her own folder in /tmp.
-TazOC

[Pelo]

maybe copy /root/.osmo folder (hidden folder) to your pupsave and see if that works. Nice idea. I come back