Search Criteria
Package Details: yandex-disk 0.1.6.1080-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/yandex-disk.git (read-only, click to copy) |
---|---|
Package Base: | yandex-disk |
Description: | Yandex.Disk keeps your files with you at all times. |
Upstream URL: | http://disk.yandex.ru/ |
Keywords: | disk yandex |
Licenses: | LicenseRef-yandex-disk |
Submitter: | ziggi |
Maintainer: | Stezko (Felixoid) |
Last Packager: | Felixoid |
Votes: | 136 |
Popularity: | 0.043733 |
First Submitted: | 2013-08-27 11:59 (UTC) |
Last Updated: | 2024-02-12 10:54 (UTC) |
Dependencies (4)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc11AUR, gcc-snapshotAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compatAUR)
Latest Comments
1 2 3 4 5 6 7 Next › Last »
parovoz commented on 2023-12-24 21:01 (UTC)
@erydit i fixed it by running 'yandex-disk setup' again
erydit commented on 2023-08-07 10:17 (UTC)
yandex-disk suddenly stopped to work. "> yandex-disk start" leads to: (process:39459): GLib-GObject-CRITICAL **: 13:15:03.356: cannot register existing type 'PxManager'
(process:39459): GLib-CRITICAL **: 13:15:03.357: g_once_init_leave: assertion 'result != 0' failed
(process:39459): GLib-GObject-CRITICAL **: 13:15:03.357: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Got signal 11, faulty address is 68, from 0x7f66e1b5fc2b 0.1.6.1080 x64 [bt] Execution path: [bt] /usr/lib/libglib-2.0.so.0(g_mutex_lock+0xb) [0x7f66e1b5fc2b] [bt] /usr/lib/libglib-2.0.so.0(g_mutex_lock+0xb) [0x7f66e1b5fc2b] [bt] /usr/lib/libproxy/libpxbackend-1.0.so(px_manager_get_proxies_sync+0x2f) [0x7f66e1ef6e8f] [bt] /usr/lib/libproxy.so(px_proxy_factory_get_proxies+0x2e) [0x7f66e1f0123e] [bt] yandex-disk() [0x468ec1] [bt] yandex-disk() [0x47613c] [bt] yandex-disk() [0x4764ef] [bt] yandex-disk() [0x4acee9] [bt] yandex-disk() [0x47c64b] [bt] yandex-disk() [0x47cd48] [bt] yandex-disk() [0x47f0da] [bt] yandex-disk() [0x4b3fef] [bt] yandex-disk() [0x41e307] [bt] yandex-disk() [0x415d63] [bt] yandex-disk() [0x41790b] [bt] /usr/lib/libc.so.6(+0x23850) [0x7f66e2833850] [bt] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f66e283390a] [bt] yandex-disk() [0x4140e9]
Any suggestions?
fatik_ul commented on 2022-07-07 05:27 (UTC)
Для решения проблемы с ошибкой: Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8, необходимо выполнить следующее:
В настройках Локализации > Форматы, вручную в "Регионы" выбрать "русский ru_RU.UTF-8", заново выполнить вход или перезагрузиться.
Изначально, там по какой-то причине установлен формат "ru_RU.UTF-8.UFT-8". Кстати, на эту ошибку ругается не только yandex-disk, но и другие пакеты, если внимательно посмотреть лог установки.
RBuster commented on 2022-06-15 02:33 (UTC)
Puted two lines to /etc/locale-gen and run "locale-gen".
en_US.UTF-8 UTF-8
ru_RU.UTF-8 UTF-8
Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8
The problem is only with the yandex-disk package. Maybe the package refers to other locales? Or an incorrect error - the problem is completely different
Stezko commented on 2022-06-14 09:16 (UTC)
Я думаю решать проблему локали недопустима в комментариях к пакету.
dchusovitin commented on 2022-06-14 09:12 (UTC) (edited on 2022-06-14 09:12 (UTC) by dchusovitin)
@RBuster where did you find "ru_RU.UTF-8.UTF-8" locale? It's a wrong locale. A message "Invalid or unsupported charset:utf-8.utf-8 or UTF-8" says about that.
Put two lines to /etc/locale-gen and run "locale-gen".
en_US.UTF-8 UTF-8
ru_RU.UTF-8 UTF-8
RBuster commented on 2022-06-14 07:14 (UTC)
The following lines are uncommented in the /etc/locale.gen file:
en_US.UTF-8 UTF-8 ru_RU.UTF-8.UTF-8 UTF-8
But still Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8
Stezko commented on 2022-06-13 17:00 (UTC)
@RBuster may be en_US.utf-8?
RBuster commented on 2022-06-13 16:16 (UTC)
Error: Invalid or unsupported charset:utf-8.utf-8 or UTF-8
1 2 3 4 5 6 7 Next › Last »