![]() |
2010-11-07
, 01:25
|
Posts: 838 |
Thanked: 292 times |
Joined on Apr 2010
|
#632
|
The Following User Says Thank You to extendedping For This Useful Post: | ||
![]() |
2010-11-07
, 02:00
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#633
|
|
2010-11-08
, 19:59
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#634
|
The Following User Says Thank You to For This Useful Post: | ||
![]() |
2010-11-08
, 20:15
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#635
|
![]() |
2010-11-10
, 13:31
|
Posts: 462 |
Thanked: 550 times |
Joined on Sep 2008
@ Moscow
|
#636
|
python /usr/lib/hildon-desktop/advanced_power.py 1
The Following User Says Thank You to 412b For This Useful Post: | ||
![]() |
2010-11-11
, 03:46
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#637
|
![]() |
2010-11-19
, 08:37
|
|
Posts: 12 |
Thanked: 6 times |
Joined on Nov 2010
@ Florida
|
#638
|
python /usr/lib/hildon-desktop/advanced_power.py 1 process 2173: 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 2173: 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
The Following User Says Thank You to vebulous For This Useful Post: | ||
![]() |
2010-11-28
, 14:14
|
Posts: 262 |
Thanked: 206 times |
Joined on May 2010
|
#639
|
Ok. I've reread posts. Somehow upstart doesn't start Advanced Power Monitor, which is quite strange.
For now just run as root
And attach output.Code:start apmonitord
Anyway it should help me to figure out, why apmonitord isn't starting at startup (crossed fingers)
![]() |
2010-11-28
, 15:33
|
Posts: 262 |
Thanked: 206 times |
Joined on May 2010
|
#640
|
That's odd... It should write it, if loaded properly.
I got a mistype in upstart script.
As root edit /etc/event.d/apmonitord:
Change line starting withtoCode:stop on ...And post the results. It should help.Code:stop on starting shutdown
If people could give a list of what they had installed on their N900's when they installed it (in detail. Everything app manager lists when you press uninstall, please), and whether or not you had the battery bar/"candle"(as some of you call it) vanish after installing, that would would be wonderful. That's the only way someone with my limited technical knowledge can think of to truly narrow down what the cause of the problem might be.