[Zesty] No default apps shown on first start in kvm oem end user

Bug #1666495 reported by Dave Morley on 2017-02-21
This bug affects 5 people
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
Marco Trevisan (Treviño)

Bug Description

1. Install the latest iso in kvm
2. Click on Ubuntu button

I expect to see Thunderbird, rhythmbox, totem, etc. There are normally 5 default apps shown.

I get what you see in the attached screenshot.
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-02-21 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Tags: zesty
Uname: Linux 4.10.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Dave Morley (davmor2) wrote :
summary: - [Zesty] No default apps shown on first start in kvm
+ [Zesty] No default apps shown on first start in kvm oem end user
Sebastien Bacher (seb128) wrote :

thank you for your bug report, is that specific to the oem mode? Also could you report the bug using ubuntu-bug or at least manually attach the syslog/journal log to the bug?

Changed in unity-lens-applications:
importance: Undecided → High
status: New → Incomplete

apport information

tags: added: apport-collected zesty
description: updated

apport information

apport information

Changed in unity-lens-applications:
status: Incomplete → Invalid
Changed in zeitgeist (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)

Zeitgeist service didn't start because of pre-start script failing on missing activity db.

The attachment "zeitgeist-service-optional-prestart.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Iain Lane (laney) wrote :

Trevinho disagrees with me, but I want to put on the record that I think comment #6's patch is wrong and that instead the VACUUM mode should explicitly check if the database exists and "return 0" in that case.


It's reasonable to say that it's okay to run without having run the main program first. The counter argument says that this is *not* reasonable and you would expect an error in this case. I think that there is no one true way here, and you should write programs with their intended usage in mind. In this case I think the intented use is that you could imagine a user writing a shell script such as:


  set -e

  zeitgeist-vacuum # or zeitgeist --vacuum

(of course this is a simplified version of the existing user unit's control flow)

and it's just silly to have to detect the DB not existing explicitly there. It's also a bit shady to ignore VACUUM failures that could point to a more severe problem.

For the record, I think the code to implement my change would look like this (untested).

    var file = File.new_for_path (db_path);
    if (!file.query_exists ())
        debug ("Database '%s' doesn't exist, but that's okay".printf (db_path));
        return 0;

With this change the unit file can remain unmodified.

Since there's disagreement, I won't unilaterally upload my suggestion.

As I wrote in IRC, unfortunately even using the new

  zeitgeist --vacuum

Would fail in such scenario, as it would return a non-zero value (see [1]), thus my idea of just changing the unit file.

Which also is due to the fact that a standalone tool is right to return an error in such cases, while it's up to script to handle these failures.

[1] https://cgit.freedesktop.org/zeitgeist/zeitgeist/tree/src/zeitgeist-daemon.vala#n478

corrado@corrado-z-feb27:~$ uname -a
Linux corrado-z-feb27 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

installed from: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
/home/corrado/.local/share/zeitgeist is empty.
copy /home/corrado/.local/share/zeitgeist from a different installation from:
Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
seems solving the problem

see: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1667898

Iain Lane (laney) wrote :

uploaded, please test tomorrow once it hits an image

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package zeitgeist - 1.0-0ubuntu1

zeitgeist (1.0-0ubuntu1) zesty; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (LP: #1665902)
  * debian/control:
    - Drop Build-Depends on intltool
  * Drop patches applied in new release
    - Give-the-D-Bus-service-files-the-correct-names.patch
    - Add-a-systemd-user-service-for-each-D-Bus-session-se.patch
    - fix_autocomplete.diff
    - fix-test-crash.patch
    - thread-default-context.patch
  * Refresh patches

  [ Iain Lane ]
  * Fix debian/patches/startup-database-vacuum.patch
    - The vacuum mode is now included upstream
    - Move the wrapper script to a file in debian/ and install that
    - Call the wrapper and allow it to fail so that zeitgeist starts for new
      users (LP: #1666495)
  * debian/patches/0001-Fix-placeholder-in-systemd-service-template.patch:
    Cherry-pick. Fix substitution in systemd unit file.

 -- Iain Lane <email address hidden> Wed, 01 Mar 2017 14:09:01 +0000

Changed in zeitgeist (Ubuntu):
status: In Progress → Fix Released
Mathew Hodson (mhodson) on 2017-03-02
affects: unity-lens-applications → ubuntu
no longer affects: ubuntu
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers