After upgrading to sys-libs/glibc-2.36-r3 media-video/makemmkv-1.17.1 crashes during start up phase while searching for disc drives. The crashes happens independently of whether a disc is inserted or not. Reproducible: Always Steps to Reproduce: 1. Start makemkv 2. 3.
Created attachment 814714 [details] backtrace
Created attachment 814717 [details] emerge --info makemkv
I think we need to know why the program it pipes to suddenly dies.
I bisected glibc and it's caused by efa7936e4c91b1c260d03614bb26858fbb8a0204: dlsym: Make RTLD_NEXT prefer default version definition [BZ #14932] I've posted this information upstream.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c1fe0f501af09acaf1acbbbfce1e7bf528b90d57 commit c1fe0f501af09acaf1acbbbfce1e7bf528b90d57 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2022-10-02 20:28:18 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2022-10-02 20:28:35 +0000 media-video/makemkv: Broken with glibc 2.36 so prevent upgraded Obviously users who have already upgraded cannot downgrade, but at least we can help the ones who haven't upgraded yet. Bug: https://bugs.gentoo.org/873508 Signed-off-by: James Le Cuirot <chewi@gentoo.org> media-video/makemkv/makemkv-1.17.1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Is the makemkv upstream aware of this issue with latest glibc? Where is the ball right now?
(In reply to devsk from comment #6) > Is the makemkv upstream aware of this issue with latest glibc? Where is the > ball right now? Chewi said "I'll send this information upstream"
Arch users have been complaining about it since early August, but I've only just pointed out what the cause is. Unfortunately, upstream have not said anything about it this whole time. https://forum.makemkv.com/forum/viewtopic.php?f=3&t=28856
Isn't it a better solution to revert that commit in glibc and release a new glibc-rX ebuild instead of forcing a glibc downgrade? Every world update I do now is trying to force the glibc downgrade.
No, we're not going to change glibc's behaviour just for this. I think you'll only see a glibc downgrade if MakeMKV has an update pending, which is unlikely since it was last bumped in July. You can avoid the downgrade by passing --exclude=media-video/makemkv to emerge. Bear in mind that we *may* have to remove MakeMKV from Gentoo soon for a completely different reason anyway, but I don't want to say more about that until we have more information.
Nothing seems to be broken with glibc-2.35 (where that commit is not there, of course). But yes, if you have other reasons to take makemkv out of portage, it probably does not deserve such a huge favor.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e57bd10ca6176ce2eda405817925ba54f087f0a commit 0e57bd10ca6176ce2eda405817925ba54f087f0a Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2022-10-12 20:23:30 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2022-10-12 20:23:30 +0000 media-video/makemkv: Bump to 1.17.2, drop old 1.17.1 Fixes the crash seen against glibc 2.36. Closes: https://bugs.gentoo.org/873508 Signed-off-by: James Le Cuirot <chewi@gentoo.org> media-video/makemkv/Manifest | 4 ++-- media-video/makemkv/{makemkv-1.17.1.ebuild => makemkv-1.17.2.ebuild} | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
