slytomcat / yandex-disk-indicator Goto Github PK

View Code? Open in Web Editor NEW

234.0 234.0 30.0 4.57 MB

Panel indicator (GTK+) for YandexDisk CLI client for Linux

License: GNU General Public License v3.0

Python 88.84% Shell 11.11% Makefile 0.05%

linux panel-indicator ppa python python-3 yandex-disk

yandex-disk-indicator's Introduction

yandex-disk-indicator

Desktop panel indicator for YandexDisk CLI client for Linux (GTK+)

NOTE:

If You are looking for YandexDisk indicator for KDE or other non-GTK based DE take a look on yd-go. yd-go is a little simpler indicator written in golang. It uses D-BUS to communicate with the desktop notification plugin, that's why yd-go is fully independent off Desktop Environment.

IMPORTANT:

Indicator responsible only for showing the synchronisation status in the desctop panel. All the synchronisation operations are perfomed by yandex-disk utility from Yandex.

INSTALLATION:

See installation instruction in Wiki

INTERFACE LANGUAGES

English, Russian, Greek, Bulgarian, Belorussian.

NOTES:

Indicator code assumes that:

yandex-disk-indicator is copied to /usr/bin/yandex-disk-indicator and marked as executable (chmod a+x ...)
fm-actions/ and icons/ folders, ya-setup and *.py files are located in /usr/share/yd-tools folder
*.desktop files were placed in /usr/share/applications folder
compiled language files (translations/*.mo) are located in the system depended folders (i.e. usr/share/locale/{LANG}/LC_MESSAGES/ in Linux)
ya-setup utility translations files (translations/ya-setup*.lang) are located in /usr/share/yd-tools/translation folder NOTE: All action above can be done via running of build/install.sh script
indicator settings are stored in ~/.config/yd-tools/yandex-disk-indicator.conf (file is automatically created on the first start).

build - everything that need to build the .deb package or source.changes file (only change key for signatures). Additional tools are required: devscripts, debhelper and dput (if you want to upload package, for example, to launchpad PPA).

install.sh - script to install the indicator
prepare.sh - creates the package build/instalation image in build/yd-tools/
clean.sh - clean build directory
build_deb.sh - creates DEB package
make_source.changes.sh - prepares sources for publication
publish_to_PPA.sh - prepares sources and publish it to my ppa

See the wiki page for details: https://github.com/slytomcat/yandex-disk-indicator/wiki.

yandex-disk-indicator's People

Contributors

Stargazers

Watchers

yandex-disk-indicator's Issues

Quatation marks in Russian Thunar action

Thunar actions (in russian) are written with quatatiton marks.

Status: error

Почему-то значек в трее все время красный и при открытии меню написано Status:error. В чем может быть проблема? Главное все файлы синхронизированны 100%

[Not critical] Выполнять операции в потоке

Недавно открыл для себя такую вещь, как потоки. Может быть пришло время их использовать?

Дело в том, что в некоторых случаях, например, после длительного неиспользования и последующего запуска — индикатор ненадолго подвисает (не вызывается контекстное меню, как минимум). Судя по всему он ожидает ответа от yandex-disk демона, когда тот испытывает долгое сканирование структуры файлов в облаке и, как я понял, время ожидания растягивается до тех пор, пока демон не решит свои задачи. Были случаи, когда из-за этого у меня полностью зависала панель (xfce4-panel)

На мой взгляд использование потоков решит эту проблему, если индикатор будет запускать дополнительный процесс, когда как основной процесс будет уведомлять пользователя об ожидании ответа от этого дополнительного процесса...

Запуск проверки с начала.

Здравствуйте.
Заметил странное поведение.
По несчастью пришлось зайти на win, а там тоже стоит яндекс диск.
В папках ничего не менялось. Единственное винда могла только загрузить себе что-то, но в win я ничего не удалял и не добавлял.
Так вот после возврата в lin запустился процесс проверки и уже два часа 180 гигов проверяется.
Заметил уже во второй раз это.
Если яндекс диск стоит на win и на win, то проверяются только новые файлы, а вот lin с начала все проверяет.
Подскажите как быть.

Выборочная синхронизация через GUI

Добавьте, пожалуйста, возможность выбирать синхронизируемые каталоги через GUI.

Я видел, что подобная возможность настройки есть в консоли и файле config.cfg, но это неудобно.
Хотелось бы видеть, что мы выбираем и галочками "протыкать" синхронизируемые каталоги (соответственно, оставшиеся будут добавлены в исключения).

Вот пример похожего функционала в клиенте Dropbox (v48.3.57) на Ubuntu 16.04

Настройки синхронизации:

Выбор папок для синхронизации:

Пишет статус: Не установлен, причем на английском

Дистрибутив Gentoo, версия yandex-disk-indicator v.1.9.10 (ставил с помощью самостоятельно написанного ебилда в режиме версии 9999, то есть напрямую с main ветки гитхаба)
Яндекс.Диск 0.1.5.940

yandex-disk-indicator

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:43:29: The :prelight pseudo-class is deprecated. Use :hover instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:216:21: The '-gtk-image-effect' property has been renamed to '-gtk-icon-effect'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:231:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:281:58: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:288:58: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:290:17: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:307:58: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:314:67: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:316:17: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:324:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:352:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:400:13: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:571:14: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:571:14: Expected a string.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:580:32: The style property GtkWidget:wide-separators is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:581:32: The style property GtkWidget:separator-width is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:609:68: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:617:69: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:619:19: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:639:62: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:647:71: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:649:21: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:858:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1261:20: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1279:20: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1638:19: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1655:62: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1662:71: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1664:21: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1681:62: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1688:71: Using one color stop with linear-gradient() is deprecated.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1690:21: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1720:12: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gtk-contained.css:1720:12: Expected a string.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:74:47: The :prelight pseudo-class is deprecated. Use :hover instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:113:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:117:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:120:35: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:121:44: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:122:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:195:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:215:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:225:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:349:39: The :focused pseudo-class is deprecated. Use :focus instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:356:46: The :focused pseudo-class is deprecated. Use :focus instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:357:47: The :prelight pseudo-class is deprecated. Use :hover instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:361:40: The :prelight pseudo-class is deprecated. Use :hover instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:366:55: The :focused pseudo-class is deprecated. Use :focus instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:370:49: The :prelight pseudo-class is deprecated. Use :hover instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:371:48: The :focused pseudo-class is deprecated. Use :focus instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:404:14: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:404:14: Expected a string.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:568:37: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:611:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:830:13: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:908:7: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:908:17: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:914:7: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:914:17: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:935:14: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:935:14: Expected a string.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:945:10: not a number

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:945:17: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1098:30: The style property GtkButton:image-spacing is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1099:29: The style property GtkButton:inner-border is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1130:11: Not using units is deprecated. Assuming 'px'.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1130:11: Expected a string.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1147:30: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(yandex-disk-indicator:4159): Gtk-WARNING **: Theme parsing error: gnome-applications.css:1226:42: The :insensitive pseudo-class is deprecated. Use :disabled instead.
2017-05-06 19:31:57,512 ERROR    Daemon initialization failed: NOTINSTALLED
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Daemon is not installed

А вот что выдает команда статуса
`$ yandex-disk status
Статус ядра синхронизации: ожидание команды
Путь к папке Яндекс.Диска: '/home/rarogcmex/Yandex.Disk'
Всего: 42 GB
Занято: 7.21 GB
Свободно: 34.79 GB
Максимальный размер файла: 10 GB
Размер корзины: 306.48 MB

Последние синхронизированные пути:
файл: 'Обмен файлами/Объединенные звуковые наработки (что успел на момент 06 апреля 17, облегченная версия).zip'
файл: 'Обмен файлами/modman.zip'
файл: 'Фотокамера/2017-05-02 22-40-23.JPG'
файл: 'Фотокамера/2017-05-02 22-41-41.JPG'
файл: 'Фотокамера/2017-05-02 22-42-03.JPG'
файл: 'Фотокамера/2017-05-02 22-42-23.JPG'
файл: 'Фотокамера/2017-05-02 22-43-01.JPG'
файл: 'Фотокамера/2017-05-02 22-43-09.JPG'
файл: 'Фотокамера/2017-05-02 22-43-54.JPG'
файл: 'Фотокамера/2017-05-02 22-45-31.JPG'
`

Из предыдущего отчета о баге команда, однако, выдает
~ $ env -i LANG='en_US.UTF8' yandex-disk status
env: «yandex-disk»: Нет такого файла или каталога
То есть в пустом окружении команды yandex-disk нет.

Openfl Yandex.Disk Folder bug

Hi. When I try to open folder of yandex disk via menu then will be opened several copies of filemanager with yandex.disk.

Linux Mint 18 x64

Window List:

Thanks

Не работает с yandex-disk 0.1.5.1010

Describe what happened with indicator
Перестал работать с yandex-disk 0.1.5.1010
Describe steps to recreate the issue
поставить новый yandex-disk из офф репы, запустить yandex-disk-indicator, будет видно, что он запустил yandex-disk (у меня так настроено), но не видит его.
Make debugging log:

close indicator if ir is running
start indicator in terminal by command line: yandex-disk-indicator -l10
recreate the issue
copy debug output to issue

$ yandex-disk-indicator -l10
2018-10-15 22:04:35,168 INFO     yandex-disk-indicator v.1.10.4
2018-10-15 22:04:35,168 DEBUG    Logging level: 10
2018-10-15 22:04:35,170 DEBUG    Config value read as: autostart = True
2018-10-15 22:04:35,170 DEBUG    Config value read as: theme = True
2018-10-15 22:04:35,170 DEBUG    Config value read as: notifications = True
2018-10-15 22:04:35,170 DEBUG    Config value read as: daemons = ~/.config/yandex-disk/config.cfg
2018-10-15 22:04:35,170 DEBUG    Config value read as: fmextensions = True
2018-10-15 22:04:35,170 INFO     Config read: /home/user/.config/yd-tools/yandex-disk-indicator.conf
2018-10-15 22:04:35,183 DEBUG    Config value read as: auth = /home/user/.config/yandex-disk/passwd
2018-10-15 22:04:35,183 DEBUG    Config value read as: dir = /home/user/Yandex.Disk
2018-10-15 22:04:35,184 DEBUG    Config value read as: proxy = False
2018-10-15 22:04:35,184 DEBUG    Config value read as: startonstartofindicator = True
2018-10-15 22:04:35,184 DEBUG    Config value read as: stoponexitfromindicator = False
2018-10-15 22:04:35,184 DEBUG    Config value read as: exclude-dirs = Фотокамера, upload
2018-10-15 22:04:35,184 INFO     Config read: /home/user/.config/yandex-disk/config.cfg
2018-10-15 22:04:35,497 DEBUG    Event raised by Timer
2018-10-15 22:04:35,498 INFO     Change event: stat,size,
2018-10-15 22:04:35,500 DEBUG    Sub-menu 'Last synchronized' has 0 items
2018-10-15 22:04:35,500 INFO     Status: unknown -> none
2018-10-15 22:04:37,618 INFO     Daemon started, message: Запуск демона...Готово

Describe your OS (distribution, version, desktop environment)
Ubuntu 14.04.5 LTS + Mate 1.10

Спасибо!

I think we need.

Hello,
I think we need add translation to https://github.com/slytomcat/yandex-disk-indicator/blob/master/ya-setup.
Is possible add translation to ya-setup file ?

Wrong localization info

Неверное сообщение о локализации.

Код в строках 934-936 исполняется в любом случае, даже если файл локализации не найден.
Соответственно то, что после except -- не исполняется, а текст в приложении на английском.
В консоли же сообщается неверная инфа.

Отсюда предположение о безсмысленности _ = str. В gettext'е это уже всё, вроде, автоматизировано.
Я бы поправил, но не знаю причины проверки.

Проблемы с запуском индикатора

При старте системы снова и снова приходится настраивать яндекс диск с помощью вашего индикатора
при запуске яндекс диска и индикатора зависает

вот лог из терминала

~ $ yandex-disk-indicator -l10
2017-06-09 09:51:12,137 INFO yandex-disk-indicator v.1.9.11
2017-06-09 09:51:12,137 DEBUG Logging level: 10
2017-06-09 09:51:12,138 DEBUG Config value read as: autostart = True
2017-06-09 09:51:12,139 DEBUG Config value read as: fmextensions = True
2017-06-09 09:51:12,139 DEBUG Config value read as: theme = False
2017-06-09 09:51:12,139 DEBUG Config value read as: notifications = True
2017-06-09 09:51:12,139 DEBUG Config value read as: daemons = /home/dima/.config/yandex-disk/config.cfg
2017-06-09 09:51:12,139 INFO Config read: /home/dima/.config/yd-tools/yandex-disk-indicator.conf
2017-06-09 09:51:12,191 DEBUG Config value read as: proxy = False
2017-06-09 09:51:12,192 DEBUG Config value read as: dir = /media/dima/Arch/Yandex/ftp174
2017-06-09 09:51:12,192 DEBUG Config value read as: auth = /home/dima/.config/yandex-disk/passwd
2017-06-09 09:51:12,192 INFO Config read: /home/dima/.config/yandex-disk/config.cfg

может это поможет папка диска находится на отдельном диске и Файловая система NTFS

могу предоставить удаленный доступ к рабочему столу что бы показать свяжитесь со мной, есть скайп bosdima

Падения на Ubuntu 17.10

Периодически падает при показе уведомлений с таким трейсом:

Traceback (most recent call last):
   File "/usr/bin/yandex-disk-indicator", line 380, in iNhandle
     self._iNotifier.process_events()
   File "/usr/lib/python3/dist-packages/pyinotify.py", line 1275, in process_events
     self._default_proc_fun(revent)
   File "/usr/lib/python3/dist-packages/pyinotify.py", line 910, in __call__
     return _ProcessEvent.__call__(self, event)
   File "/usr/lib/python3/dist-packages/pyinotify.py", line 630, in __call__
     return meth(event)
   File "/usr/bin/yandex-disk-indicator", line 372, in process_IN_MODIFY
     handler(par)
   File "/usr/bin/yandex-disk-indicator", line 486, in _eventHandler
     self.change(self.vals)                  # Raise outside update event
   File "/usr/bin/yandex-disk-indicator", line 694, in change
     self.notify.send(_('Synchronization has been completed'))
   File "/usr/bin/yandex-disk-indicator", line 317, in send
     self.note.close()
 GLib.GError: g-io-error-quark: GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.NotificationDaemonErrorQuark.Code100: 0 is not a valid notification ID (36)

Не уверен, как правильнее это чинить, у себя закостылил пока так:

--- yandex-disk-indicator.orig.py	2018-02-01 14:07:33.607797701 +0300
+++ /usr/bin/yandex-disk-indicator	2018-02-01 14:00:49.089740131 +0300
@@ -32,7 +32,7 @@
 require_version('Notify', '0.7')
 from gi.repository import Notify
 require_version('GLib', '2.0')
-from gi.repository.GLib import timeout_add, source_remove
+from gi.repository.GLib import timeout_add, source_remove, GError
 require_version('GdkPixbuf', '2.0')
 from gi.repository.GdkPixbuf import Pixbuf
 from subprocess import check_output, call, CalledProcessError
@@ -314,7 +314,10 @@
     logger.debug('Message: %s | %s' % (self.title, messg))
     if self.note is not None:
       # if self.note.props.closed_reason = -1:
-      self.note.close()
+      try:
+          self.note.close()
+      except GError:
+          pass
       self.note = None
     try:                            # Create notification
       self.note = Notify.Notification.new(self.title, messg)

1.8.18 post-installation script was killed

Привет.
При обновлении системы получил

Setting up yd-tools (1.8.18) ...
dpkg: error processing package yd-tools (--configure):
 subprocess installed post-installation script was killed by signal (Terminated)
Errors were encountered while processing:
 yd-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Видимо что-то с /var/lib/dpkg/info/yd-tools.postinst
Вылечил его, но так делать плохо

#!/bin/bash
exit 0
done

indication error

(en):
Greetings, having problem with indicator when all the files synchronized and yandex.disk daemon is idle. And there is error notification appear with error.

Problem only with indication of error in idle mode, when syncin' everything is fine

(ru):
В момент простоя, когда не производиться синхронизация, сам индикатор весит со статусом "ошибка", и после проверки на наличие синхронизации выдает уведомление об ошибке синхронизации.

Проблема только в сообщении "ошибка" и индикации данного сообщения. Проблемы с работоспособностью и непосредственно синхронизацией нет.

Не подключается к сервису яндекс диска

Manjaro Linux, Release: 18.0.0-rc, XFCE
Яндекс.Диск 0.1.5.1010

Индикатор не подключается к сервису яндекс диска и горит серым цветом. На кнопку "запустить сервис" - не реагирует. Сам яндекс-диск работает и синхронизирует нормально.

2018-10-21 00:29:54,444 INFO yandex-disk-indicator v.1.10.4 2018-10-21 00:29:54,444 DEBUG Logging level: 10 2018-10-21 00:29:54,445 DEBUG Config value read as: autostart = True 2018-10-21 00:29:54,445 DEBUG Config value read as: notifications = False 2018-10-21 00:29:54,445 DEBUG Config value read as: theme = False 2018-10-21 00:29:54,445 DEBUG Config value read as: fmextensions = True 2018-10-21 00:29:54,445 DEBUG Config value read as: daemons = /home/we/.config/yandex-disk/config.cfg 2018-10-21 00:29:54,445 INFO Config read: /home/we/.config/yd-tools/yandex-disk-indicator.conf /usr/bin/yandex-disk-indicator:716: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.last = Gtk.MenuItem(_('Last synchronized items')) /usr/bin/yandex-disk-indicator:722: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.daemon_ss = Gtk.MenuItem('') # Start/Stop daemon: Label is depends on current daemon status /usr/bin/yandex-disk-indicator:725: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.open_folder = Gtk.MenuItem(_('Open Yandex.Disk Folder')) /usr/bin/yandex-disk-indicator:728: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations open_web = Gtk.MenuItem(_('Open Yandex.Disk on the web')) /usr/bin/yandex-disk-indicator:732: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.preferences = Gtk.MenuItem(_('Preferences')) /usr/bin/yandex-disk-indicator:735: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations open_help = Gtk.MenuItem(_('Help')) /usr/bin/yandex-disk-indicator:737: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations help1 = Gtk.MenuItem(_('Yandex.Disk daemon')) /usr/bin/yandex-disk-indicator:740: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations help2 = Gtk.MenuItem(_('Yandex.Disk Indicator')) /usr/bin/yandex-disk-indicator:746: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.about = Gtk.MenuItem(_('About')); self.about.connect("activate", self.openAbout) /usr/bin/yandex-disk-indicator:749: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations close = Gtk.MenuItem(_('Quit')) 2018-10-21 00:29:54,451 DEBUG Config value read as: auth = /home/we/.config/yandex-disk/passwd 2018-10-21 00:29:54,451 DEBUG Config value read as: dir = /home/we/Yandex.Disk 2018-10-21 00:29:54,451 DEBUG Config value read as: proxy = False 2018-10-21 00:29:54,451 INFO Config read: /home/we/.config/yandex-disk/config.cfg 2018-10-21 00:29:54,763 DEBUG Event raised by Timer 2018-10-21 00:29:54,763 INFO Change event: stat,size, 2018-10-21 00:29:54,766 DEBUG Sub-menu 'Last synchronized' has 0 items 2018-10-21 00:29:54,766 INFO Status: unknown -> none /usr/bin/yandex-disk-indicator:693: DeprecationWarning: AppIndicator3.Indicator.set_icon is deprecated self.ind.set_icon(self.icon[status]) 2018-10-21 00:29:55,630 INFO Daemon started, message: Демон уже запущен.

Поддержка Python 3.2

Ubuntu 12.04 c Python 3.2.3 - не взлетит?

~ $ yandex-disk-indicator 
  File "/usr/bin/yandex-disk-indicator", line 7
    COPYRIGHT = 'Copyright ' + u'\u00a9' + ' 2013-2016 Sly_tom_cat'
                                       ^
SyntaxError: invalid syntax
~ $ python3 --version
Python 3.2.3

yd-tools require libappindicator-gtk3

Say, on Manjaro Linux XFCE/MATE libappindicator-gtk3 isn't installed by default, so yandex-disk-indicator raises ValueError: Namespace AppIndicator3 not available
This should have been mentioned in README.md as a dependency required.

Install error: "fatal: Not a git repository (or any of the parent directories): .git"

Describe what happened with indicator
"fatal: Not a git repository (or any of the parent directories): .git" error during the installation process according to the instructions in README.md.

Describe steps to recreate the issue

Download an archive from https://github.com/slytomcat/yandex-disk-indicator/releases/latest.
Extract the files and change to build directory.
Run sudo ./install.sh.

Make debugging log:

sudo ./install.sh 
yd-tools (1.10.3) artful; urgency=medium
  * Changes:
    - file watcher simplified (-iNotify +stat+timer)
    - multiselection in FileChooserDialog (while adding exluded folders)

 -- Sly_tom_cat <[email protected]>  Sun, 20 May 2018 11:44:32 +0300
fatal: Not a git repository (or any of the parent directories): .git

Describe your OS (distribution, version, desktop environment)
Ubuntu 17.10 x64

The reason is git clean -df . line in clean.sh, which is unnecessary if the program was downloaded as an archive.

Подвисает индикатор во время первого запуска в gentoo linux

Пиветствую!

В gentoo, во время первого запуска, индикатор подвисает на очень долгое время.
Судя по процессам он пытается запустить emerge, чтобы установить файловый менеджер:

Сейчас, чтобы избежать этого, мне приходяится изменять вот эти строки:

--- a/yandex-disk-indicator.py	2017-05-08 21:07:51.000000000 +0300
+++ b/yandex-disk-indicator.py	2017-09-16 22:47:48.596964782 +0300
@@ -1482,8 +1482,8 @@
   config['autostart'] = checkAutoStart(autoStartDst)
   # Setup on-screen notification settings from config value
   config.setdefault('notifications', True)
-  config.setdefault('theme', False)
-  config.setdefault('fmextensions', True)
+  config.setdefault('theme', True)
+  config.setdefault('fmextensions', False)
   config.setdefault('daemons', '~/.config/yandex-disk/config.cfg')
   # Is it a first run?
   if not config.readSuccess:
@@ -1506,8 +1506,6 @@
       except:
         logger.error('Can\'t activate indicator automatic start on system start-up')
 
-    # Activate FM actions according to config (as it is first run)
-    activateActions(config['fmextensions'])
     # Default settings should be saved (later)
     config.changed = True

При включении опции "Активировать расширения для файл-менеджера" индикатор так же зависает. В качестве файлового менеджера у меня используется Thunar

Пишет статус: Не запущен

Дистрибутив ALT Linux. Версия клиента yandex-disk-indicator 1.9.6. Версия yandex-disk 0.1.5.948.

yandex-disk-indicator -l10
2017-02-16 15:42:47,238 INFO     yandex-disk-indicator v.1.9.6
2017-02-16 15:42:47,239 DEBUG    Logging level: 10
2017-02-16 15:42:47,243 DEBUG    Config value read as: theme = False
2017-02-16 15:42:47,243 DEBUG    Config value read as: fmextensions = True
2017-02-16 15:42:47,244 DEBUG    Config value read as: autostart = True
2017-02-16 15:42:47,244 DEBUG    Config value read as: daemons = ~/.config/yandex-disk/config.cfg
2017-02-16 15:42:47,244 DEBUG    Config value read as: notifications = True
2017-02-16 15:42:47,244 INFO     Config read: /home/anton/.config/yd-tools/yandex-disk-indicator.conf
2017-02-16 15:42:47,427 DEBUG    Config value read as: proxy = False
2017-02-16 15:42:47,428 DEBUG    Config value read as: dir = /home/anton/Yandex.Disk
2017-02-16 15:42:47,428 DEBUG    Config value read as: auth = /home/anton/.config/yandex-disk/passwd
2017-02-16 15:42:47,428 DEBUG    Config value read as: stoponexitfromindicator = True
2017-02-16 15:42:47,429 DEBUG    Config value read as: startonstartofindicator = True
2017-02-16 15:42:47,429 INFO     Config read: /home/anton/.config/yandex-disk/config.cfg
2017-02-16 15:42:49,219 INFO     Start success, message: Запуск демона...Готово

2017-02-16 15:42:49,266 INFO     Change event: {init}
2017-02-16 15:42:49,276 DEBUG    Sub-menu 'Last synchronized' has been updated
2017-02-16 15:42:49,277 INFO     Status: none -> paused
2017-02-16 15:42:49,598 DEBUG    Event raised byTimer 
2017-02-16 15:42:49,599 INFO     Change event: {stat}
2017-02-16 15:42:49,600 INFO     Status: paused -> none
2017-02-16 15:42:49,600 DEBUG    Message: Яндекс.Диск  | Сервис Яндекс.Диск остановлен

Получается не может получить статус? Статус считываться должен из ~/Yandex.Disk/.sync/status ?

cat ~/Yandex.Disk/.sync/status
24203

При этом:

yandex-disk status
Статус ядра синхронизации: ожидание команды
Путь к папке Яндекс.Диска: '/home/anton/Yandex.Disk'
	Всего: 10 GB
	Занято: 2.71 GB
	Свободно: 7.29 GB
	Максимальный размер файла: 10 GB
	Размер корзины: 0 B

Последние синхронизированные пути:
	файл: 'Запись экрана 2016-12-18 19:41:38.mp4'
	файл: 'Включаем управление яркостью.mp4'
	файл: 'Screencast_23.03.2015_08:41:30.webm'
	файл: 'Screencast_23.03.2015_08:34:16.webm'
	файл: 'Загрузки/Builder-icex/regular-builder-icex-20151002-x86_64.iso'
	файл: 'Загрузки/Builder-icex/regular-builder-icex-qtcreator-20151005-x86_64.iso'
	файл: 'Загрузки/EPIC_FLAG.rar'
	файл: 'trikStudio/trikStudio-p7-64.tar.gz'
	файл: 'Загрузки/FLProg_1_10_Linux64.tar.gz'
	файл: 'Загрузки/Nokia N900 RX-51 Gr.RUS_sw-20.2010.36.2.exe'

New version 1.4.0

Before 5 minute download new version 1.4.0 ok.
But Icons lost.
I go to /usr/share/yd-tools/ and see wrong path for icons:

./fm-actions/Nautilus_Nemo/unpublish:zenity --info --window-icon=/opt/yd-tools/icons/yd-128_g.png --ok-label="Закрыть" --title="Yandex.Disk" --text="$*
./fm-actions/Nautilus_Nemo/publish:zenity --info --window-icon /opt/yd-tools/icons/yd-128_g.png --title="Yandex.Disk" --ok-label="Закрыть" --text="Ссылка на файл $*
./fm-actions/Dolphin/unpublish.desktop:X-KDE-Icon=/opt/yd-tools/icons/yd-128_g.png
./fm-actions/Dolphin/unpublish.desktop:Icon=/opt/yd-tools/icons/yd-128_g.png
./fm-actions/Dolphin/unpublish.desktop:Exec=zenity --info --window-icon=/opt/yd-tools/icons/yd-128_g.png --ok-label="Закрыть" --title="Yandex.Disk" --text="Убрать из публикации через Yandex.disk: yandex-disk unpublish %F"
./fm-actions/Dolphin/publish.desktop:X-KDE-Icon=/opt/yd-tools/icons/yd-128.png
./fm-actions/Dolphin/publish.desktop:Icon=/opt/yd-tools/icons/yd-128.png
./fm-actions/Dolphin/publish.desktop:Exec=yandex-disk publish %F | xclip -filter -selection clipboard; zenity --info --window-icon=/opt/yd-tools/icons/yd-128.png

Индиктор для 2го аккаунта: Другой экземпляр индикатора уже запущен.

Добрый день.

В документации написано, что yd-indicator умеет показывать синхронизацию для нескольких аккаунтов
https://github.com/slytomcat/yandex-disk-indicator/wiki/Часто-задаваемые-вопросы

Я настроил и запустил сервис ya-disk для работы с 2мя аккаунтами (судя по выводу консоли, они оба работают). Один аккаунт с дефолтными настройками, второму передаю параметры в командной строке.

Один yandex-disk-indicator запущен с настройками по умолчанию и показывает статус синхронизации для 1го аккаунта yandex.

Пробую запустить 2й экземпляр yandex-disk-indicator с указанием пути к отдельному конфиг-файлу

 yandex-disk-indicator --config /home/user/.config/yd-tools/yandex-disk-indicator-acc2.conf

получаю

Другой экземпляр индикатора уже запущен.

2й индикатор не стартует

Нет прокрутки списка каталогов исключений

Можете добавить прокрутку списка каталогов исключений? Так как у меня их больше 30.

Халява от Yandex-а - Freebie from Yandex

Думаю многим будет интересно - на Yandex диске раздают по 32Гб навсегда https://yandex.ru/set/lp/disk-32gb/0/

I think it can be interesting for many people - Yandex announced free 32Gb gift for everybody who:

have installed mobile version of yandex.disk
have switched on the photo autoloading to disk
Made a photo and have waited for uploading it to disk
Profit - you receive +32Gb for free and for forever

Action is until July 3 2017

Не открывается GUI до запуска демона

Я Яндекс.Диску символическими ссылками скормил папку с 7 ГБ исходников ядра Linux в несколкьих экземплярах, yandex-disk start висит по полчаса , потребление памяти постепенно увеличивается с 9 до 450 МБ, дальше не ждал. Через конфиг дописывание строки
exclude-dirs="/home/user/Яндекс.Диск/Linux-Dumalogiya/packages/linux-chuwi/"
не помогло,
yandex-disk start --exclude-dirs="/home/user/Яндекс.Диск/Linux-Dumalogiya/packages/linux-chuwi/"
тоже не помогло.
Установил yd-tools, надеясь, что он поможет мне настроить исключения, однако, судя по всему, yandex-disk-indicator ждет, пока выполнится yandex-disk start, и не появляется в трее, а он у меня очень джолго запускается и не известно, запустится ли вообще, как я уже написал.

Сейчас напишу в поддержку Яндекса и дам им ссылку сюда, в целом это проблема именно ЯндексДиска, но вдруг что-то придумаете или подскажете, как настроить исключения или измените алгоритм запуска Индикатора, чтобы в таких случаях, как у меня, он помог настроить исключения.

yandex-disk setup --exclude-dirs="/home/user/Яндекс.Диск/Linux-Dumalogiya/packages/linux-chuwi/" тоже вызывает запуск демона, который длится очень долго.

PyGTK DeprecationWarinigs / AppIndicator3 DeprecationWarning

/usr/bin/yandex-disk-indicator:717: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.last = Gtk.MenuItem(_('Last synchronized items'))

Same repeats in rows:
723: self.daemon_ss = Gtk.MenuItem('')
726: self.open_folder = Gtk.MenuItem(('Open Yandex.Disk Folder'))
729: open_web = Gtk.MenuItem(('Open Yandex.Disk on the web'))
733: self.preferences = Gtk.MenuItem(('Preferences'))
736: open_help = Gtk.MenuItem(('Help'))
738: help1 = Gtk.MenuItem(('Yandex.Disk daemon'))
741: help2 = Gtk.MenuItem(('Yandex.Disk Indicator'))
747: self.about = Gtk.MenuItem(('About')); self.about.connect("activate", self.openAbout)
750: close = Gtk.MenuItem(('Quit'))

/usr/bin/yandex-disk-indicator:694: DeprecationWarning: AppIndicator3.Indicator.set_icon is deprecated
self.ind.set_icon(self.icon[status])

ArchLinux 5.0.1-arch1-1-ARCH, LXQt. App version 1.10.6, Python 3.7.2.
Arch is rolling release distro that means that PyGObject and AppIndiactor are latest versions.

Перестал запускаться в Ubuntu 15.10

На днях yandex-disk-indicator (1.8.15) "на ровном месте" перестал запускаться.
Из консоли и при помощи ярлыка результат одинаковый.
В логах так:

2016-05-28 13:56:20,073 INFO yandex-disk-indicator v.1.8.15
2016-05-28 13:56:20,073 DEBUG Logging level: 10
2016-05-28 13:56:20,074 DEBUG Config value read as: theme = False
2016-05-28 13:56:20,075 DEBUG Config value read as: notifications = True
2016-05-28 13:56:20,075 DEBUG Config value read as: autostart = True
2016-05-28 13:56:20,075 DEBUG Config value read as: daemons = ~/.config/yandex-disk/config.cfg
2016-05-28 13:56:20,075 DEBUG Config value read as: fmextensions = True
2016-05-28 13:56:20,075 INFO Config read: /home/warrior/.config/yd-tools/yandex-disk-indicator.conf
2016-05-28 13:56:20,075 DEBUG Lock file is:/home/warrior/.config/yd-tools/pid
2016-05-28 13:56:20,076 DEBUG Lock file succesfully locked.
2016-05-28 13:56:20,099 DEBUG Config value read as: auth = /home/warrior/.config/yandex-disk/passwd
2016-05-28 13:56:20,099 DEBUG Config value read as: dir = /home/warrior/Yandex.Disk
2016-05-28 13:56:20,099 DEBUG Config value read as: proxy = False
2016-05-28 13:56:20,100 INFO Config read: /home/warrior/.config/yandex-disk/config.cfg
2016-05-28 13:56:20,115 INFO Change event: {stat, size, last, init}
2016-05-28 13:56:20,119 DEBUG Sub-menu 'Last synchronized' has been updated
2016-05-28 13:56:22,124 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:24,123 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:27,150 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:31,174 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:36,199 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:42,223 DEBUG Raw event Timer idle -> idle
2016-05-28 13:56:49,247 DEBUG Raw event Timer idle -> idle

Ставил из репо.
Переустановка с ключом purge не помогает, в логах - то же самое.
Что можно сделать?

Как добавить репозиторий в Parrot Linux?

Error: activateActions() missing 1 required positional argument: 'activate'

Describe what happened with indicator:
2018-02-02 14:10:16,933 INFO yandex-disk-indicator v.1.9.17
2018-02-02 14:10:16,934 DEBUG Logging level: 10
2018-02-02 14:10:16,934 ERROR Config file read error: /home/USER/.config/yd-tools/yandex-disk-indicator.conf
2018-02-02 14:10:16,934 INFO No config, probably it is a first run.
Traceback (most recent call last):
File "/usr/bin/yandex-disk-indicator", line 1400, in
activateActions()
TypeError: activateActions() missing 1 required positional argument: 'activate'
Describe steps to recreate the issue:
$ yandex-disk-indicator -l 10
Describe your OS (distribution, version, desktop environment):
Ubuntu 17.10, GNOME Shell 3.26.2

Не запускается в elementary OS

Установил через apt, иконка появилась (яндекс диск на тот момент уже был сконфигурирован через консоль и синхронизировался). При клике на иконку ничего не происходит.
Загрузил архив отсюда, выполнил yandex-disk-indicator.py
Получил такое:

** (yandex-disk-indicator.py:17754): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-emKvUVCxVb: В соединении отказано
2016-05-18 14:53:25,337 ERROR    Config file read error: /home/user/.config/yd-tools/yandex-disk-indicator.conf
Traceback (most recent call last):
  File "./yandex-disk-indicator.py", line 1494, in <module>
    activateActions()
  File "./yandex-disk-indicator.py", line 1349, in activateActions
    res = subprocess.call(["gksudo", "-D", "yd-tools", "cp", ctr_pub, ctr_unpub, ctrs_path])
  File "/usr/lib/python3.4/subprocess.py", line 537, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.4/subprocess.py", line 859, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.4/subprocess.py", line 1457, in _execute_child
    raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] Нет такого файла или каталога: 'gksudo'

Очевидно что нету gksudo, установил: sudo apt-get install gksu
заработало, но было бы очень классно если бы оно сразу заработало)
Возможно как-нибудь это предусмотреть? добавить в зависимости?

Не запускается

Describe what happened with indicator
Не запускается

Describe steps to recreate the issue

Скачать
Нажать на иконку

Make debugging log:

close indicator if ir is running
start indicator in terminal by command line: yandex-disk-indicator -l10
recreate the issue
copy debug output to issue

2019-06-11 16:07:12,920 INFO     yandex-disk-indicator v.1.10.9
2019-06-11 16:07:12,920 DEBUG    Logging level: 10
2019-06-11 16:07:12,921 DEBUG    Config value read as: autostart = True
2019-06-11 16:07:12,921 DEBUG    Config value read as: notifications = True
2019-06-11 16:07:12,921 DEBUG    Config value read as: theme = False
2019-06-11 16:07:12,921 DEBUG    Config value read as: fmextensions = True
2019-06-11 16:07:12,921 DEBUG    Config value read as: daemons = /home/ivan/.config/yandex-disk/config.cfg
2019-06-11 16:07:12,921 INFO     Config read: /home/ivan/.config/yd-tools/yandex-disk-indicator.conf
2019-06-11 16:07:12,977 DEBUG    Config value read as: auth = /home/ivan/.config/yandex-disk/passwd
2019-06-11 16:07:12,977 DEBUG    Config value read as: dir = /home/ivan/Yandex.Disk
2019-06-11 16:07:12,977 DEBUG    Config value read as: proxy = False
2019-06-11 16:07:12,977 INFO     Config read: /home/ivan/.config/yandex-disk/config.cfg
2019-06-11 16:07:13,002 INFO     Daemon is already started
2019-06-11 16:07:13,290 DEBUG    Event raised by Timer
2019-06-11 16:07:13,290 INFO     Change event: stat,size,last
2019-06-11 16:07:13,294 DEBUG    Sub-menu 'Last synchronized' has 10 items
2019-06-11 16:07:13,294 INFO     Status: unknown -> busy
2019-06-11 16:07:13,295 DEBUG    Message: Яндекс.Диск  | Запущена синхронизация

(yandex-disk-indicator:15227): Gdk-CRITICAL **: 16:07:13.377: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
2019-06-11 16:07:15,323 DEBUG    Event raised by Timer
2019-06-11 16:07:15,323 INFO     Change event: stat,,last
2019-06-11 16:07:15,326 DEBUG    Sub-menu 'Last synchronized' has 10 items
2019-06-11 16:07:17,350 DEBUG    Event raised by Timer
2019-06-11 16:07:17,351 INFO     Change event: stat,,
2019-06-11 16:07:19,379 DEBUG    Event raised by Timer
2019-06-11 16:07:19,379 INFO     Change event: stat,,
^C2019-06-11 16:07:21,148 DEBUG    Exit started
2019-06-11 16:07:21,148 DEBUG    Indicator exit started: 
2019-06-11 16:07:21,148 DEBUG    Indicator exited

Describe your OS (distribution, version, desktop environment)
Linux Mint 19.1 Cinnamon

"запуск сервиса не удался" хотя сервис успешно работает

Индикатор выдаёт сообщение о том, что запуск сервиса не удался, хотя сервис успешно работает. Предварительно с помощью этого приложения настроил клиент, ошибок не выводилось.

Скриншот сообщения об ошибке -

Вывод консольный:

$ yandex-disk-indicator -l10                              
2019-06-19 19:10:55,482 INFO     yandex-disk-indicator v.1.10.9
2019-06-19 19:10:55,483 DEBUG    Logging level: 10
2019-06-19 19:10:55,490 DEBUG    Config value read as: autostart = True
2019-06-19 19:10:55,491 DEBUG    Config value read as: notifications = True
2019-06-19 19:10:55,491 DEBUG    Config value read as: theme = False
2019-06-19 19:10:55,492 DEBUG    Config value read as: fmextensions = True
2019-06-19 19:10:55,494 DEBUG    Config value read as: daemons = /home/dmitriy/.config/yandex-disk/config.cfg
2019-06-19 19:10:55,496 INFO     Config read: /home/dmitriy/.config/yd-tools/yandex-disk-indicator.conf

(yandex-disk-indicator:22808): Gtk-WARNING **: 19:10:55.538: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:22808): Gtk-WARNING **: 19:10:55.538: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(yandex-disk-indicator:22808): Gtk-WARNING **: 19:10:55.538: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
2019-06-19 19:10:55,657 DEBUG    Config value read as: auth = /home/dmitriy/.config/yandex-disk/passwd
2019-06-19 19:10:55,657 INFO     Config read: /home/dmitriy/.config/yandex-disk/config.cfg
/usr/bin/yandex-disk-indicator:596: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "parent, flags, message_type, buttons, message_format" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  _('Yandex.Disk Indicator: daemon start failed'))
/usr/bin/yandex-disk-indicator:596: PyGTKDeprecationWarning: The keyword(s) "message_format" have been deprecated in favor of "text" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  _('Yandex.Disk Indicator: daemon start failed'))
Daemon is not configured

Вывод сервиса самого Яндекс.Диска:

$ yandex-disk status --dir=/home/dmitriy/downloads/Yandex.Disk 
Статус синхронизации: 720.77 MB/ 2.63 GB (26 %)
Статус ядра синхронизации: синхронизация
...

Устанавливал с ppa:slytomcat/ppa, операционная система Kubuntu 19.04.

Буду очень благодарен за помощь в решении этой проблемы.

--help key doesn't show output when indicator running

Start of indicator with --help key produces message 'The indicator instance is already running.' if indicator is already running. But it should show the command line options in any case.

Путь к папке используется другим пользователем

OS: Linux Mint Mate 18.3 x86_64
Симптомы: Индикатор успешно запускается со статусом остановленного сервиса, но запуск синхронизации ни к чему не приводит.

Логи запуска индикатора (после убийства всех процессов самого сервиса и индикатора):

$ yandex-disk-indicator -l10
2017-12-18 16:00:02,751 INFO     yandex-disk-indicator v.1.9.14
2017-12-18 16:00:02,751 DEBUG    Logging level: 10
2017-12-18 16:00:02,752 DEBUG    Config value read as: notifications = True
2017-12-18 16:00:02,752 DEBUG    Config value read as: fmextensions = True
2017-12-18 16:00:02,752 DEBUG    Config value read as: autostart = True
2017-12-18 16:00:02,752 DEBUG    Config value read as: daemons = /home/toby3d/.config/yandex-disk/config.cfg
2017-12-18 16:00:02,752 DEBUG    Config value read as: theme = False
2017-12-18 16:00:02,752 INFO     Config read: /home/toby3d/.config/yd-tools/yandex-disk-indicator.conf
2017-12-18 16:00:02,806 DEBUG    Config value read as: proxy = auto
2017-12-18 16:00:02,806 DEBUG    Config value read as: dir = /home/toby3d/Yandex.Disk
2017-12-18 16:00:02,806 DEBUG    Config value read as: auth = /home/toby3d/.config/yandex-disk/passwd
2017-12-18 16:00:02,806 INFO     Config read: /home/toby3d/.config/yandex-disk/config.cfg
2017-12-18 16:00:03,890 ERROR    Daemon start failed:Ошибка: путь к папке используется другим пользователем: /home/toby3d/Yandex.Disk

2017-12-18 16:00:03,913 DEBUG    Event raised byTimer 
2017-12-18 16:00:03,913 INFO     Change event: stat,size,
2017-12-18 16:00:03,914 DEBUG    Sub-menu 'Last synchronized' has 0 items
2017-12-18 16:00:03,915 INFO     Status: unknown -> none

Crash on unconfigured daemon

Indicator crashes after start on unconfigured daemon.

$ yandex-disk-indicator -l10
2018-03-23 14:44:38,424 INFO yandex-disk-indicator v.1.10.1
2018-03-23 14:44:38,424 DEBUG Logging level: 10
2018-03-23 14:44:38,425 DEBUG Config value read as: autostart = True
2018-03-23 14:44:38,425 DEBUG Config value read as: notifications = True
2018-03-23 14:44:38,425 DEBUG Config value read as: theme = False
2018-03-23 14:44:38,425 DEBUG Config value read as: fmextensions = True
2018-03-23 14:44:38,425 DEBUG Config value read as: daemons = /home/ivan/.config/yandex-disk/config.cfg
2018-03-23 14:44:38,425 INFO Config read: /home/ivan/.config/yd-tools/yandex-disk-indicator.conf
2018-03-23 14:44:38,452 DEBUG Config value read as: auth = /home/ivan/.config/yandex-disk/passwd
2018-03-23 14:44:38,452 INFO Config read: /home/ivan/.config/yandex-disk/config.cfg
Traceback (most recent call last):
File "/usr/bin/yandex-disk-indicator", line 1401, in
indicators.append(Indicator(d, _('#%d ') % len(indicators) if len(daemons) > 1 else ''))
File "/usr/bin/yandex-disk-indicator", line 676, in init
super(Indicator, self).init(path, ID)
File "/usr/bin/yandex-disk-indicator", line 412, in init
if self.errorDialog(cfgFile) != 0:
AttributeError: 'Indicator' object has no attribute 'errorDialog'

Status is "Not started"

Hi! I updated yandex-disk and status became "Not started"; "Used: .../..."
ArchLinux gnome 3
aur/yandex-disk 0.1.5.978-2 -> 0.1.5.1010-1

$ yandex-disk-indicator -l10
2018-10-30 16:23:23,178 INFO yandex-disk-indicator v.1.10.5
2018-10-30 16:23:23,178 DEBUG Logging level: 10
2018-10-30 16:23:23,179 DEBUG Config value read as: autostart = True
2018-10-30 16:23:23,179 DEBUG Config value read as: notifications = True
2018-10-30 16:23:23,179 DEBUG Config value read as: theme = False
2018-10-30 16:23:23,179 DEBUG Config value read as: fmextensions = True
2018-10-30 16:23:23,179 DEBUG Config value read as: daemons = /home/alexander/.config/yandex-disk/config.cfg
2018-10-30 16:23:23,179 INFO Config read: /home/alexander/.config/yd-tools/yandex-disk-indicator.conf
/usr/bin/yandex-disk-indicator:717: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.last = Gtk.MenuItem(('Last synchronized items'))
/usr/bin/yandex-disk-indicator:723: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.daemon_ss = Gtk.MenuItem('') # Start/Stop daemon: Label is depends on current daemon status
/usr/bin/yandex-disk-indicator:726: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.open_folder = Gtk.MenuItem(('Open Yandex.Disk Folder'))
/usr/bin/yandex-disk-indicator:729: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
open_web = Gtk.MenuItem(('Open Yandex.Disk on the web'))
/usr/bin/yandex-disk-indicator:733: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.preferences = Gtk.MenuItem(('Preferences'))
/usr/bin/yandex-disk-indicator:736: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
open_help = Gtk.MenuItem(('Help'))
/usr/bin/yandex-disk-indicator:738: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
help1 = Gtk.MenuItem(('Yandex.Disk daemon'))
/usr/bin/yandex-disk-indicator:741: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
help2 = Gtk.MenuItem(('Yandex.Disk Indicator'))
/usr/bin/yandex-disk-indicator:747: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
self.about = Gtk.MenuItem(('About')); self.about.connect("activate", self.openAbout)
/usr/bin/yandex-disk-indicator:750: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
close = Gtk.MenuItem(_('Quit'))
2018-10-30 16:23:23,212 DEBUG Config value read as: proxy = False
2018-10-30 16:23:23,213 DEBUG Config value read as: dir = /home/alexander/ahome/ydisk
2018-10-30 16:23:23,213 DEBUG Config value read as: auth = /home/alexander/.config/yandex-disk/passwd
2018-10-30 16:23:23,213 INFO Config read: /home/alexander/.config/yandex-disk/config.cfg
2018-10-30 16:23:23,518 INFO Daemon started, message: Daemon is already running.

2018-10-30 16:23:23,531 DEBUG Event raised by Timer
2018-10-30 16:23:23,532 INFO Change event: stat,size,
2018-10-30 16:23:23,536 DEBUG Sub-menu 'Last synchronized' has 0 items
2018-10-30 16:23:23,536 INFO Status: unknown -> none
/usr/bin/yandex-disk-indicator:694: DeprecationWarning: AppIndicator3.Indicator.set_icon is deprecated
self.ind.set_icon(self.icon[status])

Last synchronized menu is not updated on autostart

Describe what happened with indicator

Last synchronized menu is not updated on autostart. See details (Russian): http://forum.ubuntu.ru/index.php?topic=241992.msg2313192#msg2313192

Describe your OS (distribution, version, desktop environment):

Linux Neon 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: neon
Description: KDE neon User Edition 5.11
Release: 16.04
Codename: xenial

don't start on gentoo

Hello
Thank you for developing!
But i can't to try in, because it don't start
[code]
$ yandex-disk-indicator

(yandexDiskIndicator.py:25311): GLib-GIO-ERROR **: Settings schema 'apps.yandex-disk-indicator' is not installed

/usr/bin/yandex-disk-indicator: line 3: 25311 Trace/breakpoint trap ./yandexDiskIndicator.py

I tryed install from git and from deb package
Wat's the problem?

The last version update bug.

After the last update not start well,
We try it start from terminal and the answer is :
(yandexDiskIndicator.py:9010): Gtk-WARNING **: Theme parsing error: gtk.css:10:0: expected '{' after selectors.
Not serious bug, please check the /opt/yd-tools/yandexDiskIndicator.py
We try it on Linux Mint 17.2 Cinnamon , Yandex-disk-indicator version 1.3.1_Py2.

Подвисает во время обновления истории загрузок...

Если во время синхронизации открыть пункт "Последние синхронизированные" и дождаться обновления списка истории, то в момент обновления индикатор насмерть зависает.

До:

После:

Вывод команды "yandex-disk-indicator -l10"

2018-06-20 15:48:09,496 INFO     yandex-disk-indicator v.1.10.4
2018-06-20 15:48:09,496 DEBUG    Logging level: 10
2018-06-20 15:48:09,497 DEBUG    Config value read as: autostart = False
2018-06-20 15:48:09,498 DEBUG    Config value read as: fmextensions = False
2018-06-20 15:48:09,498 DEBUG    Config value read as: theme = True
2018-06-20 15:48:09,498 DEBUG    Config value read as: daemons = ¯\_(ツ)_/¯
2018-06-20 15:48:09,498 DEBUG    Config value read as: notifications = False
2018-06-20 15:48:09,498 INFO     Config read: ¯\_(ツ)_/¯
2018-06-20 15:48:09,555 DEBUG    Config value read as: auth = ¯\_(ツ)_/¯
2018-06-20 15:48:09,555 DEBUG    Config value read as: dir = ¯\_(ツ)_/¯
2018-06-20 15:48:09,555 DEBUG    Config value read as: exclude-dirs = ¯\_(ツ)_/¯
2018-06-20 15:48:09,555 DEBUG    Config value read as: proxy = False
2018-06-20 15:48:09,555 DEBUG    Config value read as: startonstartofindicator = False
2018-06-20 15:48:09,556 DEBUG    Config value read as: stoponexitfromindicator = True
2018-06-20 15:48:09,556 INFO     Config read: ¯\_(ツ)_/¯

(yandex-disk-indicator.py:31838): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
2018-06-20 15:48:09,878 DEBUG    Event raised by Timer
2018-06-20 15:48:09,878 INFO     Change event: stat,size,
2018-06-20 15:48:09,880 DEBUG    Sub-menu 'Last synchronized' has 0 items
2018-06-20 15:48:09,880 INFO     Status: unknown -> none
2018-06-20 15:48:16,861 INFO     Daemon started, message: Запуск демона...Готово

2018-06-20 15:48:17,347 DEBUG    Event raised by Watcher
2018-06-20 15:48:17,347 INFO     Change event: ,,last
2018-06-20 15:48:17,450 DEBUG    Sub-menu 'Last synchronized' has 10 items
2018-06-20 15:48:24,542 DEBUG    Event raised by Watcher
2018-06-20 15:48:24,542 INFO     Change event: stat,size,
2018-06-20 15:48:24,543 INFO     Status: none -> busy
2018-06-20 15:48:59,945 DEBUG    Event raised by Watcher
2018-06-20 15:48:59,945 INFO     Change event: stat,,last
2018-06-20 15:48:59,977 DEBUG    Sub-menu 'Last synchronized' has 10 items
2018-06-20 15:49:02,185 DEBUG    Event raised by Timer
2018-06-20 15:49:02,186 INFO     Change event: stat,,
2018-06-20 15:49:04,214 DEBUG    Event raised by Timer
2018-06-20 15:49:04,215 INFO     Change event: stat,,
2018-06-20 15:49:06,252 DEBUG    Event raised by Timer
2018-06-20 15:49:06,252 INFO     Change event: stat,,
2018-06-20 15:49:12,837 DEBUG    Event raised by Timer
2018-06-20 15:49:12,838 INFO     Change event: stat,,
2018-06-20 15:49:19,326 DEBUG    Event raised by Timer
2018-06-20 15:49:19,327 INFO     Change event: stat,,
2018-06-20 15:49:23,536 DEBUG    Event raised by Timer
2018-06-20 15:49:23,536 INFO     Change event: stat,,
2018-06-20 15:49:25,843 DEBUG    Event raised by Timer
2018-06-20 15:49:25,843 INFO     Change event: stat,,
2018-06-20 15:49:31,318 DEBUG    Event raised by Timer
2018-06-20 15:49:31,318 INFO     Change event: stat,,
2018-06-20 15:49:36,524 DEBUG    Event raised by Timer
2018-06-20 15:49:36,524 INFO     Change event: stat,,
2018-06-20 15:49:41,240 DEBUG    Event raised by Timer
2018-06-20 15:49:41,240 INFO     Change event: stat,,
2018-06-20 15:49:45,907 DEBUG    Event raised by Timer
2018-06-20 15:49:45,907 INFO     Change event: stat,,
2018-06-20 15:49:51,025 DEBUG    Event raised by Timer
2018-06-20 15:49:51,025 INFO     Change event: stat,,
2018-06-20 15:49:56,252 DEBUG    Event raised by Timer
2018-06-20 15:49:56,252 INFO     Change event: stat,,
2018-06-20 15:49:59,162 DEBUG    Event raised by Timer
2018-06-20 15:49:59,162 INFO     Change event: stat,,
2018-06-20 15:50:06,320 DEBUG    Event raised by Timer
2018-06-20 15:50:06,321 INFO     Change event: stat,,
2018-06-20 15:50:13,392 DEBUG    Event raised by Timer
2018-06-20 15:50:13,393 INFO     Change event: stat,,
2018-06-20 15:50:19,664 DEBUG    Event raised by Timer
2018-06-20 15:50:19,665 INFO     Change event: stat,,
2018-06-20 15:50:26,454 DEBUG    Event raised by Timer
2018-06-20 15:50:26,454 INFO     Change event: stat,,
2018-06-20 15:50:29,859 DEBUG    Event raised by Timer
2018-06-20 15:50:29,859 INFO     Change event: stat,,
2018-06-20 15:50:37,295 DEBUG    Event raised by Timer
2018-06-20 15:50:37,295 INFO     Change event: stat,,
2018-06-20 15:50:40,419 DEBUG    Event raised by Timer
2018-06-20 15:50:40,419 INFO     Change event: stat,,
2018-06-20 15:50:45,487 DEBUG    Event raised by Timer
2018-06-20 15:50:45,488 INFO     Change event: stat,,
2018-06-20 15:50:48,635 DEBUG    Event raised by Timer
2018-06-20 15:50:48,635 INFO     Change event: stat,,
2018-06-20 15:50:52,078 DEBUG    Event raised by Timer
2018-06-20 15:50:52,079 INFO     Change event: stat,,
2018-06-20 15:50:56,290 DEBUG    Event raised by Timer
2018-06-20 15:50:56,290 INFO     Change event: stat,,
2018-06-20 15:51:01,922 DEBUG    Event raised by Timer
2018-06-20 15:51:01,922 INFO     Change event: stat,,last
2018-06-20 15:51:04,317 DEBUG    Sub-menu 'Last synchronized' has 10 items
 *** судя по всему где-то тут начинает подвисать ***
2018-06-20 15:51:07,317 DEBUG    Event raised by Timer
2018-06-20 15:51:07,317 INFO     Change event: stat,,

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
2018-06-20 15:51:09,846 DEBUG    Event raised by Timer
2018-06-20 15:51:09,846 INFO     Change event: stat,,

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(yandex-disk-indicator.py:31838): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
2018-06-20 15:51:11,926 DEBUG    Event raised by Timer
2018-06-20 15:51:11,926 INFO     Change event: stat,,
2018-06-20 15:51:14,329 DEBUG    Event raised by Timer
2018-06-20 15:51:14,329 INFO     Change event: stat,,
2018-06-20 15:51:22,086 DEBUG    Event raised by Timer
2018-06-20 15:51:22,086 INFO     Change event: stat,,
2018-06-20 15:51:25,687 DEBUG    Event raised by Timer
2018-06-20 15:51:25,687 INFO     Change event: stat,,
2018-06-20 15:51:33,342 DEBUG    Event raised by Timer
2018-06-20 15:51:33,342 INFO     Change event: stat,,
2018-06-20 15:51:37,245 DEBUG    Event raised by Timer
2018-06-20 15:51:37,245 INFO     Change event: stat,,
2018-06-20 15:51:42,633 DEBUG    Event raised by Timer
2018-06-20 15:51:42,633 INFO     Change event: stat,,
2018-06-20 15:51:47,837 DEBUG    Event raised by Timer
2018-06-20 15:51:47,838 INFO     Change event: stat,,
*** Делаю SIGTERM ***
2018-06-20 15:51:49,586 DEBUG    Exit started
2018-06-20 15:51:49,586 DEBUG    Indicator exit started: 
2018-06-20 15:51:58,573 INFO     Daemon stopped, message: Демон остановлен.

2018-06-20 15:51:58,573 INFO     Demon stopped
2018-06-20 15:51:58,573 DEBUG    Indicator exited

Пугают сообщения "(yandex-disk-indicator.py:31838): Gtk-CRITICAL **"...
ОС Gentoo Linux. Дерево зависимостей:

* dependency graph for x11-misc/yd-tools-1.10.4
 `--  x11-misc/yd-tools-1.10.4  ~amd64 
   `--  dev-lang/python-3.4.8  (dev-lang/python) amd64 
   `--  dev-lang/python-3.5.5  (dev-lang/python) amd64 
   `--  dev-lang/python-3.6.5  (dev-lang/python) amd64 
   `--  dev-lang/python-exec-2.4.5  (>=dev-lang/python-exec-2) amd64  [python_targets_python3_4(-)? python_targets_python3_5(-)? python_targets_python3_6(-)? -python_single_target_python3_4(-) -python_single_target_python3_5(-) -python_single_target_python3_6(-)]
   `--  dev-libs/glib-2.52.3  (>=dev-libs/glib-2.0) amd64 
   `--  dev-libs/libappindicator-12.10.0-r301  (dev-libs/libappindicator) amd64 
   `--  dev-python/pyinotify-0.9.6  (>=dev-python/pyinotify-0.9.6) amd64  [python_targets_python3_4(-)? python_targets_python3_5(-)? python_targets_python3_6(-)? -python_single_target_python3_4(-) -python_single_target_python3_5(-) -python_single_target_python3_6(-)]
   `--  dev-python/pygobject-3.24.1  (dev-python/pygobject) amd64  [python_targets_python3_4(-)? python_targets_python3_5(-)? python_targets_python3_6(-)? -python_single_target_python3_4(-) -python_single_target_python3_5(-) -python_single_target_python3_6(-)]
   `--  gnome-extra/zenity-3.24.0  (gnome-extra/zenity) amd64 
   `--  net-misc/yandex-disk-0.1.5.978_p1  (net-misc/yandex-disk) ~amd64 
   `--  x11-misc/xclip-0.13  (x11-misc/xclip) amd64 
   `--  x11-libs/gtk+-3.22.29  (>=x11-libs/gtk+-3.0) amd64 
   `--  x11-libs/gdk-pixbuf-2.36.12  (>=x11-libs/gdk-pixbuf-2.0) amd64 
   `--  sys-devel/gettext-0.19.8.1  (sys-devel/gettext) amd64 
   `--  sys-apps/sed-4.2.2  (>=sys-apps/sed-4) amd64 
[ x11-misc/yd-tools-1.10.4 stats: packages (16), max depth (1) ]

расширения для файл-менеджера

какая функциональность у этих расширений?
Не вижу разницы между включением и выключением их

Push for inclusion in Russian Fedora

I am switching to Fedora from KDE neon, and I would like to use Yandex.Disk with the indicator, but the latter is not part of any repository. It would be great to have it in the RFRemix repos, I'm sure it could fit in nicely.

Bug in 1.8.0 on ppa

Привет,
На ppa в версии 1.8.0 есть ошибка.
Я сравнил файл yandex-disk-indicator.py здесь и в пакете ppa и есть большие различия.
Нужно их исправить.

pkill yd-tools не работает.

После последних изменений перестал нормально обрабатываться сигнал SIGTERM зарегистрированный в главном потоке, который обрабатывает главный цикл GTK.

Сигнал фиксируется, но обрабатывается только при просыпании главного цикла GTK.

Видимо обработчик сигнала надо регистрировать в системе событий GTK.

Требуется исследование вопроса.

v.1.10.0 utilizes one CPU core up to 100%

V.1.10.0 have the issue with CPU utilization due to switch to ThreadedNotifier without any tuning.

ThreadedNotifier must be tuned properly.

Проблема с индикатором. Значёк показывает постоянную синхронизацию.

Индикатор на панели показывает постоянную синхронизацию. При том что никаких файлов в яндекс.диск добавлено не было.

После запуска системы и запуска ya-tools индикатор показывает постоянную синхронизацию.

2018-11-14 11:34:52,352 INFO yandex-disk-indicator v.1.10.5
2018-11-14 11:34:52,353 DEBUG Logging level: 10
2018-11-14 11:34:52,354 DEBUG Config value read as: autostart = True
2018-11-14 11:34:52,354 DEBUG Config value read as: daemons = /home/i8086/.config/yandex-disk/config.cfg
2018-11-14 11:34:52,355 DEBUG Config value read as: fmextensions = True
2018-11-14 11:34:52,355 DEBUG Config value read as: notifications = True
2018-11-14 11:34:52,355 DEBUG Config value read as: theme = False
2018-11-14 11:34:52,355 INFO Config read: /home/i8086/.config/yd-tools/yandex-disk-indicator.conf
2018-11-14 11:34:52,392 DEBUG Config value read as: proxy = False
2018-11-14 11:34:52,392 DEBUG Config value read as: dir = /home/i8086/Yandex
2018-11-14 11:34:52,392 DEBUG Config value read as: auth = /home/i8086/.config/yandex-disk/passwd
2018-11-14 11:34:52,393 INFO Config read: /home/i8086/.config/yandex-disk/config.cfg
2018-11-14 11:34:52,421 INFO Daemon is already started
2018-11-14 11:34:52,702 DEBUG Event raised by Timer
2018-11-14 11:34:52,702 INFO Change event: stat,size,last
2018-11-14 11:34:52,706 DEBUG Sub-menu 'Last synchronized' has 10 items
2018-11-14 11:34:52,706 INFO Status: unknown -> busy
2018-11-14 11:34:52,707 DEBUG Message: Яндекс.Диск | Запущена синхронизация

(yandex-disk-indicator:16059): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
2018-11-14 11:36:23,907 DEBUG Togged: notifications val: False
2018-11-14 11:36:25,451 DEBUG Togged: notifications val: True
2018-11-14 11:36:29,155 DEBUG Togged: theme val: True
2018-11-14 11:36:35,867 DEBUG Togged: theme val: False
2018-11-14 11:36:40,475 DEBUG Togged: fmextensions val: False
2018-11-14 11:36:40,476 INFO Nemo installed
2018-11-14 11:36:40,476 ERROR File Deletion Error: /home/i8086/.gnome2/nemo-scripts/Опубликовать через Яндекс.Диск
2018-11-14 11:36:40,476 ERROR File Deletion Error: /home/i8086/.gnome2/nemo-scripts/Убрать из публикации через Яндекс.Диск
2018-11-14 11:36:41,611 DEBUG Togged: fmextensions val: True
2018-11-14 11:36:41,612 INFO Nemo installed
2018-11-14 11:36:44,867 DEBUG Togged: autostart val: False
2018-11-14 11:36:46,460 DEBUG Togged: autostart val: True
2018-11-14 11:36:50,979 DEBUG Togged: startonstartofindicator val: False
2018-11-14 11:36:52,147 DEBUG Togged: startonstartofindicator val: True
2018-11-14 11:36:56,860 DEBUG Togged: stoponexitfromindicator val: True
2018-11-14 11:37:05,802 DEBUG []
2018-11-14 11:37:07,155 DEBUG []
2018-11-14 11:37:11,036 DEBUG Config value to save: fmextensions="yes"
2018-11-14 11:37:11,037 DEBUG Config value to save: autostart="yes"
2018-11-14 11:37:11,037 DEBUG Config value to save: daemons="/home/i8086/.config/yandex-disk/config.cfg"
2018-11-14 11:37:11,037 DEBUG Config value to save: theme="no"
2018-11-14 11:37:11,037 DEBUG Config value to save: notifications="yes"
2018-11-14 11:37:11,055 INFO Config written: /home/i8086/.config/yd-tools/yandex-disk-indicator.conf
2018-11-14 11:37:11,055 DEBUG Config value to save: stoponexitfromindicator="yes"
2018-11-14 11:37:11,056 DEBUG Config value to save: startonstartofindicator="yes"
2018-11-14 11:37:11,056 DEBUG Config value 'read-only' will be removed
2018-11-14 11:37:11,056 DEBUG Config value 'overwrite' will be removed
2018-11-14 11:37:11,056 DEBUG Config value 'exclude-dirs' will be removed
2018-11-14 11:37:11,057 INFO Config written: /home/i8086/.config/yandex-disk/config.cfg
^C2018-11-14 11:39:08,821 DEBUG Exit started
2018-11-14 11:39:08,822 DEBUG Indicator exit started:
2018-11-14 11:39:08,842 INFO Daemon stopped, message: Демон остановлен.

2018-11-14 11:39:08,842 INFO Demon stopped
2018-11-14 11:39:08,843 DEBUG Indicator exited

LinuxMint 18.4 Cinnamon (3.6.7) 64-bit

Некорректно сохраняет настройки прокси в конфиге

Добавляет кавычки вокруг каждого параметра прокси:
proxy="тип", "адрес", "порт"

Должно быть
proxy="тип,адрес,порт"

Autostart

Началось все здесь:
#49 (comment)

На данным момент имеем

два разных атрибута для отключения автозапуска.
каталог ~/.config/autostart - отсутствует в большинстве дистрибутивов сразу после установки (добавлен код по созданию при первом запуске).

Решения:

Проверять переменные $XDG_CURRENT_DESKTOP и по справочнику выбирать нужный атрибут для проверки.
При разрешении авто-запуска атрибут не править, а перезаписывать файл.
При запрете - не парится с атрибутом, а просто удалять.
-запуска атрибут не править, а перезаписывать файл.
При запрете - не парится с атрибутом, а просто удалять.
Забить, прописывать автозапуск при первом старте и дать инструкцию пользователю рулить автозапуск только через утилиты системы.

Пока - думаю.

Wrong directory separator

Instead of syncing folders that contain files, it downloads files with names like dir1\dir2\dir3\file - all of them directly to the root folder of Yandex-Disk.
Looks like it determines directory separator wrong.

Details:

Xubuntu 16.04 x64 (with latest updates from official apt repositories)
Yandex-Disk 0.1.5.978 (latest from apt repository)
yd-tools 1.9.6 (latest from apt repository)

Logs during reproducing the bug:

patchranger@patchranger-HP-15ba061ur:~$ yandex-disk-indicator -l10
2016-11-27 17:17:17,299 INFO     yandex-disk-indicator v.1.9.6
2016-11-27 17:17:17,300 DEBUG    Logging level: 10
2016-11-27 17:17:17,303 DEBUG    Config value read as: daemons = ~/.config/yandex-disk/config.cfg
2016-11-27 17:17:17,303 DEBUG    Config value read as: autostart = True
2016-11-27 17:17:17,303 DEBUG    Config value read as: fmextensions = True
2016-11-27 17:17:17,303 DEBUG    Config value read as: theme = False
2016-11-27 17:17:17,303 DEBUG    Config value read as: notifications = True
2016-11-27 17:17:17,303 INFO     Config read: /home/patchranger/.config/yd-tools/yandex-disk-indicator.conf
2016-11-27 17:17:17,385 DEBUG    Config value read as: auth = /home/patchranger/.config/yandex-disk/passwd
2016-11-27 17:17:17,385 DEBUG    Config value read as: dir = /home/patchranger/YandexDisk/[email protected]
2016-11-27 17:17:17,385 DEBUG    Config value read as: proxy = False
2016-11-27 17:17:17,386 INFO     Config read: /home/patchranger/.config/yandex-disk/config.cfg
2016-11-27 17:17:19,683 INFO     Start success, message: Запуск демона...Готово

2016-11-27 17:17:19,706 INFO     Change event: {stat, init}
2016-11-27 17:17:19,710 DEBUG    Sub-menu 'Last synchronized' has been updated
2016-11-27 17:17:19,710 INFO     Status: none -> paused
2016-11-27 17:17:19,710 DEBUG    Message: Яндекс.Диск  | Сервис Яндекс.Диск запущен
2016-11-27 17:17:21,148 DEBUG    Event raised byiNtfy 
2016-11-27 17:17:21,149 INFO     Change event: {stat, last}
2016-11-27 17:17:21,156 DEBUG    Sub-menu 'Last synchronized' has been updated
2016-11-27 17:17:21,157 INFO     Status: paused -> busy
2016-11-27 17:17:21,157 DEBUG    Message: Яндекс.Диск  | Запущена синхронизация
2016-11-27 17:17:22,204 DEBUG    Event raised byTimer 
2016-11-27 17:17:22,205 INFO     Change event: {prog}
2016-11-27 17:17:25,752 DEBUG    Event raised byTimer 
2016-11-27 17:17:25,752 INFO     Change event: {size}
2016-11-27 17:17:29,753 DEBUG    Event raised byTimer 
2016-11-27 17:17:29,753 INFO     Change event: {last}
2016-11-27 17:17:29,766 DEBUG    Sub-menu 'Last synchronized' has been updated
2016-11-27 17:17:31,755 DEBUG    Event raised byTimer 
2016-11-27 17:17:31,755 INFO     Change event: {last}
2016-11-27 17:17:31,766 DEBUG    Sub-menu 'Last synchronized' has been updated
2016-11-27 17:17:33,750 DEBUG    Event raised byTimer 
2016-11-27 17:17:33,751 INFO     Change event: {last}
2016-11-27 17:17:33,761 DEBUG    Sub-menu 'Last synchronized' has been updated
2016-11-27 17:17:44,972 DEBUG    Event raised byiNtfy 
2016-11-27 17:17:44,973 INFO     Change event: {stat, prog, size, last}
2016-11-27 17:17:44,973 INFO     Status: busy -> none
2016-11-27 17:17:44,974 DEBUG    Message: Яндекс.Диск  | Сервис Яндекс.Диск остановлен

Индикатор не стартует после логаута пользователя

Директория /tmp при логауте пользователя не очищается. Лок-файл /tmp/yandex-disk-indicator.lock не удаляется, из за чего индикатор, после повтороного входа, не может запуститься.

Дополнительно, нельзя запустить индикатор для нескольких пользователей, ибо лок-файл один на всех.

slytomcat / yandex-disk-indicator Goto Github PK

yandex-disk-indicator's Introduction

yandex-disk-indicator

yandex-disk-indicator's People

Contributors

Stargazers

Watchers

Forkers

yandex-disk-indicator's Issues

Recommend Projects

Recommend Topics

Recommend Org