Bug 868147 – <net-misc/yandex-disk-0.1.6.1080_p1: segmentation fault on startup

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Oschtan 2022-09-03 02:58:06 UTC]

yandex-disk start --dir=Work/
yandex-disk: /usr/local/boost/boost_1_59_0/include/boost/thread/pthread/mutex.hpp:111: boost::mutex::~mutex(): Assertion `!res' failed.
Got signal 6
0.1.6.1074 x64
[bt] Execution path:
[bt] /lib64/libc.so.6(+0x8ac6c) [0x7f6a1cf04c6c]
[bt] /lib64/libc.so.6(+0x8ac6c) [0x7f6a1cf04c6c]
[bt] /lib64/libc.so.6(raise+0x12) [0x7f6a1ceb7a22]
[bt] /lib64/libc.so.6(abort+0xcf) [0x7f6a1cea2469]
[bt] /lib64/libc.so.6(+0x28395) [0x7f6a1cea2395]
[bt] /lib64/libc.so.6(+0x369d2) [0x7f6a1ceb09d2]
[bt] yandex-disk() [0x57eb50]
[bt] yandex-disk() [0x484812]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x58a444]
[bt] yandex-disk() [0x822d69]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x807768]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x7f988d]
[bt] yandex-disk() [0x59097a]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x8076e7]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x807f41]
[bt] yandex-disk() [0x80bbca]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x805281]
[bt] yandex-disk() [0x417d09]
[bt] yandex-disk() [0x81e8db]
[bt] yandex-disk() [0x43288f]
[bt] yandex-disk() [0x8258e5]
[bt] yandex-disk() [0xa7424c]
[bt] /lib64/libc.so.6(+0x88f2a) [0x7f6a1cf02f2a]
[bt] /lib64/libc.so.6(clone+0x40) [0x7f6a1cf87400]

Complete recompilation of the system did not help

Reproducible: Always

[Comment 1 Oschtan 2022-09-03 03:00:25 UTC]

Created attachment 802822 [details]
emerge --info

[Comment 2 Oschtan 2022-09-03 03:02:17 UTC]

=net-misc/yandex-disk-0.1.6.1074_p1

[Comment 3 Oschtan 2022-09-03 03:03:54 UTC]

=net-misc/yandex-disk-0.1.5.1039_p1 similar error

[Comment 4 Sergey Popov 2022-12-08 07:47:32 UTC]

Can not reproduce it. Does it happen also on clean user profile when you run 'yandex-disk setup' or it fails only when trying to sync?

[Comment 5 Oschtan 2022-12-16 01:35:16 UTC]

I'm not going to clean up my profile. It doesn't make sense. An error occurs with the specified command. In this case, synchronization occurs and after that the daemon immediately exits. That is, after any changes in the synchronized folder, it was necessary to start the daemon again. It can be seen that the error is probably due to the draft version of boost in the presented two versions of yandex-disk. With the new version 0.1.6.1080_p1, this error is not observed

[Comment 6 Sam James 2022-12-16 01:37:51 UTC]

(In reply to Oschtan from comment #5)
> I'm not going to clean up my profile. It doesn't make sense.

They didn't say "delete your profile", they said "does it happen with a clean one?" because it's easier to then debug. You could easily make a new temporary one.

[Comment 7 Oschtan 2022-12-16 02:18:17 UTC]

(In reply to Sam James from comment #6)
> (In reply to Oschtan from comment #5)
> > I'm not going to clean up my profile. It doesn't make sense.
> 
> They didn't say "delete your profile", they said "does it happen with a
> clean one?" because it's easier to then debug. You could easily make a new
> temporary one.

I understand, but I don't want to look for fleas in yandex-disk versions built with boost-1.59 when boost-1.80 is currently being used. Moreover, the latest version of yandex-disk, which appeared recently in portage, works correctly. And therefore I propose to close this bug, and remove the version of net-misc/yandex-disk-0.1.6.1074_p1 from the portage tree.
In the end, the developer could have posted the source code of yandex-disk, and not the binary version, to make it easier to track down errors. I am sure that there is nothing fancy and unique in the code of this client to hide it.

[Comment 8 Sergey Popov 2023-02-09 17:38:27 UTC]

Current stable version of net-misc/yandex-disk is 0.1.6.1080_p1
Older versions are removed from portage tree