Active Topics

 


Reply
Thread Tools
Posts: 388 | Thanked: 842 times | Joined on Sep 2009 @ Finland
#11
Try
Code:
export DISPLAY=:0.0
before starting GUI apps...
 
Posts: 10 | Thanked: 0 times | Joined on Feb 2010
#12
putting

export DISPLAY=:0.0

before running mauku using

export DISPLAY=:0.0
>/home/user/mauku.log
/usr/bin/mauku >/home/user/mauku.log 2>&1

outputting the log i get


$ cat mauku.log
process 1438: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 1438: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
Aborted
using the same for gpodder

export DISPLAY=:0.0
>/home/user/gpodder.log
/usr/bin/python2.5 /usr/bin/gpodder --fremantle >/home/user/gpodder.log 2>&1

then exporting the log i get

~ $ cat gpodder.log
Traceback (most recent call last):
File "/usr/bin/gpodder", line 138, in <module>
session_bus = dbus.SessionBus()
File "/usr/lib/pymodules/python2.5/dbus/_dbus.py", line 219, in __new__
mainloop=mainloop)
File "/usr/lib/pymodules/python2.5/dbus/_dbus.py", line 108, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/pymodules/python2.5/dbus/bus.py", line 125, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException
~ $
 
Posts: 388 | Thanked: 842 times | Joined on Sep 2009 @ Finland
#13
Originally Posted by craigcii View Post
putting

export DISPLAY=:0.0

before running mauku using

export DISPLAY=:0.0
>/home/user/mauku.log
/usr/bin/mauku >/home/user/mauku.log 2>&1

outputting the log i get



using the same for gpodder

export DISPLAY=:0.0
>/home/user/gpodder.log
/usr/bin/python2.5 /usr/bin/gpodder --fremantle >/home/user/gpodder.log 2>&1

then exporting the log i get
So the apps can't get dbus session bus address. Now this is a really ugly hack, but try putting this in the script before starting the apps...

Code:
PATH="/bin/:/usr/bin"
pids=`pgrep dbus-daemon`
for pid in $pids; do
    FILE=`cat /proc/$pid/environ | perl -pe 's/\x0/\n/g'|grep SESSION_BUS_ADDRESS_FILE \
    |sed -e 's/SESSION_BUS_ADDRESS_FILE=//g'`
done
eval `cat $FILE`
This works for me, I don't know if there is a cleaner/better way...

Last edited by hqh; 2010-02-28 at 14:47.
 
Posts: 10 | Thanked: 0 times | Joined on Feb 2010
#14
i actually did a search for the error message and cae across this

http://talk.maemo.org/showthread.php?t=37423

where they suggested putting run-standalone.sh before the the program call as below

cd /home/user

>/home/user/mauku.log
/usr/bin/run-standalone.sh /usr/bin/mauku >/home/user/mauku.log 2>&1 &

>/home/user/gpodder.log
/usr/bin/run-standalone.sh /usr/bin/python2.5 /usr/bin/gpodder --fremantle >/ho

date > /home/user/q.txt
anyway this has worked. just had to remember to background the script wirh & otherwise both will not run till the other ends.

i don't know what the script does but but am assuming the script sets up its own memory area or something.

i will do some more searches on it so i understand.

thanks for the help.
 
Posts: 10 | Thanked: 0 times | Joined on Feb 2010
#15
 
Reply


 
Forum Jump


All times are GMT. The time now is 05:04.