Thread Previous • Date Previous • Date Next • Thread Next |
On 08/25/2016 04:14 AM, Matthias Apitz wrote:
El día Thursday, August 25, 2016 a las 08:43:58AM +0200, Alfonso Sanchez-Beato escribió:On Thu, Aug 25, 2016 at 7:01 AM, Matthias Apitz <guru@xxxxxxxxxxx> wrote:Hello, Me and my wife we both have a BQ E4.5, OTA-12. Yesterday my wife called me and terminated the call after 2:45 min (I checked this in the evening in her device). I was lazy and watched in my BQ E4.5 the call continuing until 3:45 minutes, then it terminated by its own. I even called her from a landline phone to her BQ, while the call was still active on my side, i.e. her device was not busy... What does this mean? I will check in the call list of her provider what the provider says about the duration.It might by a temporary network glitch, it might be a bug in the phone stack. Please open a bug against ofono including /var/log/syslog and ~/.cache/upstart/telephony* from the phone that registered the 3:45 minutes call./var/log/syslog turned over today night at 02:18
Did you check for syslog.1[.gz]?
and the time corresponding ~/.cache/upstart/telephony* file does not show much information, not even timestamps: # ls -l telephony-service-indicator.log.1 -rw-r----- 1 phablet phablet 573 Aug 24 21:14 telephony-service-indicator.log.1 # cat telephony-service-indicator.log.1 void CallManager::onCallEnded() void CallManager::onCallEnded() "No such interface 'org.freedesktop.DBus.Properties' on object at path /" void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() "No such interface 'org.freedesktop.DBus.Properties' on object at path /" void CallManager::onCallEnded() "No such interface 'org.freedesktop.DBus.Properties' on object at path /" "No such interface 'org.freedesktop.DBus.Properties' on object at path /" "No such interface 'org.freedesktop.DBus.Properties' on object at path /" Who implemented such a useless log file? :-(
Well, this is generally how much of the session software on touch logs messages; by leveraging upstart's logging facility. Anything written to stdout/stderr by an a session upstart job is automatically logged to a job-specific log file in /home/phablet/.cache/upstart. It doesn't look like upstart ever grew support for timestamps in these log files.
That said, I agree, the actual log messages here aren't very helpful.In this case it looks like a requested DBus interface doesn't exist for a particular object ( perhaps a CallEntry inside telephony-service )?
Can you check /var/crash to see if there are any crash files present? Regards, /tony
Thread Previous • Date Previous • Date Next • Thread Next |