App won't start on desktop

Bug #1297712 reported by Alan Pope 🍺🐧🐱 πŸ¦„
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu Calendar App
Invalid
Critical
Unassigned
Ubuntu Clock App
Expired
Undecided
Unassigned
Ubuntu Music App
Invalid
Undecided
Unassigned

Bug Description

Running calendar from the core apps ppa or from trunk, the app doesn't actually appear. It starts, but nothing appears.

alan@deep-thought:~/phablet/code/coreapps/ubuntu-calendar-app$ qmlscene /usr/share/calendar-app/calendar.qml
unity::action::ActionManager::ActionManager(QObject*):
        Could not determine application identifier. HUD will not work properly.
        Provide your application identifier in $APP_ID environment variable.
file:///usr/share/calendar-app/calendar.qml:90: TypeError: Cannot call method 'isSameDay' of undefined
virtual QString QOrganizerEDSFactory::managerName() const
virtual QtOrganizer::QOrganizerManagerEngine* QOrganizerEDSFactory::engine(const QMap<QString, QString>&, QtOrganizer::QOrganizerManager::Error*) eds

** (qmlscene:10056): WARNING **: Unable to register app: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID

(qmlscene:10056): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(qmlscene:10056): libecal-CRITICAL **: e_cal_client_get_view: assertion 'E_IS_CAL_CLIENT (client)' failed

Changed in ubuntu-calendar-app:
importance: Undecided → Critical
Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

Getting same on clock app:-

alan@deep-thought:~/phablet/code/coreapps/ubuntu-clock-app$ qmlscene ubuntu-clock-app.qml
unity::action::ActionManager::ActionManager(QObject*):
        Could not determine application identifier. HUD will not work properly.
        Provide your application identifier in $APP_ID environment variable.
virtual QString QOrganizerEDSFactory::managerName() const
virtual QtOrganizer::QOrganizerManagerEngine* QOrganizerEDSFactory::engine(const QMap<QString, QString>&, QtOrganizer::QOrganizerManager::Error*) eds

** (qmlscene:24211): WARNING **: Unable to register app: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID

(qmlscene:24211): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(qmlscene:24211): libecal-CRITICAL **: e_cal_client_get_view: assertion 'E_IS_CAL_CLIENT (client)' failed

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

Further to this if I disable my canonical google account eds calendar sync in online accounts, the app starts immediately. I have removed the canonical google account and re-added it, and now the app starts but very slowly.

If I only have one account (my personal) active then the app starts quickly and I see (the very few I have) events.
With my canonical account active the app takes a very long time to start and no longer shows events.

Perhaps some timeout in EDS?

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

@Alan, the lag that you notice in the start up, does it apply to both the clock and calendar? or just calendar? I believe that the clock app alarms are being stored in a different database. So calendar events shouldn't technically affect clock start up.

Changed in ubuntu-clock-app:
status: New → Incomplete
Revision history for this message
brian larochelle (larochelle-brian) wrote :

@alan
do you have a rough idea how many events are in your canonical google account?

-would it be possible to export and 'sanitize' your data to share, or better create similar dummy data?
if i could reproduce it, i would try to find the cause and fix.

Revision history for this message
brian larochelle (larochelle-brian) wrote :
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

I can't start the clock app on my Ubuntu 14.04 LTS 64-bit install on my laptop under the regular desktop, either. Similar output to comment #1:

christopher@christopher-LIFEBOOK-T900:~$ ubuntu-clock-app
unity::action::ActionManager::ActionManager(QObject*):
 Could not determine application identifier. HUD will not work properly.
 Provide your application identifier in $APP_ID environment variable.

** (qmlscene:3187): WARNING **: Unable to register app: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
Fail to connect with client Unable to connect to 'Calendar': Cannot open calendar: Timeout was reached

(qmlscene:3187): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(qmlscene:3187): libecal-CRITICAL **: e_cal_client_get_view: assertion 'E_IS_CAL_CLIENT (client)' failed

Revision history for this message
Alexander Langanke (alexlanganke) wrote :

Affects the music App as well

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

Hm, music-app starts here on a fairly clean install of Ubuntu. What are you seeing Alexander?

Revision history for this message
Victor Thompson (vthompson) wrote :

This shouldn't affect the Music app. The problems here appear to be EDS related.

Changed in music-app:
status: New → Incomplete
Changed in music-app:
status: Incomplete → Invalid
Changed in ubuntu-calendar-app:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu Clock App because there has been no activity for 60 days.]

Changed in ubuntu-clock-app:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.