[Dx-packages] [Bug 1848969] [NEW] src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

2019-10-20 Thread Benjamin Drung
Public bug reported:

After upgrading to Ubuntu 19.10, indicator-datetime
15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

$ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
(process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
[...]
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
**
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

** Affects: indicator-datetime (Ubuntu)
 Importance: Critical
 Status: Confirmed

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1848969

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  [...]
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  **
  
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

2019-10-20 Thread Benjamin Drung
I am not the only one running into this bug: https://ubuntu-
mate.community/t/clock-indicator-wont-appear-19-10/20424

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1848969

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  [...]
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  **
  
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable

2019-10-20 Thread Rael Gugelmin Cunha
This is a serious security issue and it's fixed in Gnome upstream.
Probably should be backported.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1787867

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color

2019-10-20 Thread Norbert
** Tags removed: cosmic
** Tags added: focal

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1721955

Title:
  Human, Human-Clearlooks and other themes have incorrect gray window
  title color

Status in community-themes package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in human-theme package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
  2. Install Human theme from `human-theme` package
  3. Select Human theme from `mate-control-center` Appearance

  Expected results:
  window title color is set to Ubuntu's orange (#FFBE6B)

  Actual results:
  window title color is set to different gray/silver color (#a5a5a2)

  Note:
  other themes are affected too.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: human-theme 0.39.2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 15:43:03 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170925.1)
  PackageArchitecture: all
  SourcePackage: human-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2019-10-20 Thread Dave Pusey
This is still broken as of today.

Tried to upgrade a fully up-to-date 1604 LTS system to 1804 LTS using
"do-release-upgrade" and it failed with this exact issue.

Had to use the steps from comment #3 above to get it working...

mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
apt-get -f install
apt-get dist-upgrade

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2019-10-20 Thread WinEunuchs2Unix
It would be easier to delete comment #10 but I can't. `zeitgeist` wasn't
resetting screen brightness and gamma. It was simply logging error it
didn't know about application I was running to reset brightness and
gamma based on time of day.

I posted a solution to getting rid of zeitgeist error messages for
`~/Desktop/*.desktop` applications which zeitgeist understandably knows
nothing about:

- https://askubuntu.com/a/1182396/307523

In summary, open Gnome Activity Log Manager / Unity Security and
Privacy. Add the directory `~/Desktop` to the blacklist.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2019-10-20 Thread WinEunuchs2Unix
Received error on Ubuntu 16.04.6 LTS this morning. I've never noticed it
impacting me before but this time it reset my night time screen settings
to full daylight setting.

Results of `journalctl -xe | grep eyesome`:

Oct 19 21:40:55 alien eyesome[25582]: Wakeup: Creating 
/tmp/eyesome-is-suspending
Oct 20 05:21:17 alien eyesome[25788]: Wakeup: Called from suspend.
Oct 20 05:21:28 alien eyesome[26826]: Daemon: Resuming: Slept 2 seconds x 5 
times.
Oct 20 05:21:28 alien eyesome[26829]: Daemon: Removed file: 
/tmp/eyesome-is-suspending
Oct 20 05:29:52 alien eyesome[10076]: Sun Times: 
https://www.timeanddate.com/sun/canada/edmonton.
Oct 20 05:30:06 alien org.gnome.zeitgeist.SimpleIndexer[2098]: ** 
(zeitgeist-fts:4341): WARNING **: Unable to get info on 
application://eyesome-cfg.desktop
Oct 20 05:30:13 alien sudo[11668]: rick : TTY=unknown ; PWD=/home/rick ; 
USER=root ; COMMAND=/usr/local/bin/eyesome-cfg.sh
Oct 20 05:30:19 alien eyesome[12296]: Wakeup: Called from eyesome-cfg.sh.

Last night:
21:40:55 system suspends normally.

This morning:
05:21:17 system resumes normally.
05:29:52 cron.daily gets sunrise and sunset times from internet.
05:30:06 zeitgeist.SimpleIndexer error sets screen brightness & gamma to full.
05:30:13 I have to open ~/Desktop/eyesome-cfg.desktop with sudo.
05:30:19 I have to trigger eyesome wakeup to set screens based on time.

Possible Resolutions:
- All kinds of links on web and in Ask Ubuntu on removing zeitgeist.
- I have no need for speed improvements gained by removing.
- Suggestions that removing will break nautilus and gedit is a deal breaker.
- I would rather find out how to configure zeitgeist to play nicely with my 
data.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp