Moc refuse to launch in kinetic - buffer overflow detected

Bug #1995330 reported by Christophe C
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
moc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since the upgrade from jammy to kinetic, moc refuse to launch with this message :

*** buffer overflow detected ***: terminated

Archlinux has the same problem and it exists a patch. See there : https://bugs.archlinux.org/task/74041

Revision history for this message
Christophe C (batra3) wrote :

in the forum archlinux, one of the last comment explain :

Comment by gamezelda (gamezelda) - Saturday, 14 May 2022, 09:06 GMT

The underlying cause of the crash is fixed in glibc 2.35-5, so all that's needed to fix the moc package now is a rebuild (i.e. pkgrel bump without any changes).

(glibc 2.35-5 builds from glibc commit 28ea43f8d64f0dd1f2de75525157730e1532e600, and the fix for the moc crash is glibc commit c8ee1c85c07b3c9eaef46355cb1095300855e8fa which is an ancestor of it)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in moc (Ubuntu):
status: New → Confirmed
Revision history for this message
Boris Gjenero (boris-gjenero) wrote :

Using packages from Ubuntu 23.04, moc works without serious dependency problems. I used moc_2.6.0~svn-r3005-3build1 and moc-ffmpeg-plugin_2.6.0_svn-r3005-3build1 from https://launchpad.net/ubuntu/+source/moc and libflac12_1.4.2+ds-2ubuntu1 from https://launchpad.net/ubuntu/+source/flac

Only using moc_2.6.0_svn-r3005-1 from Ubuntu 22.04 works too, but it is more complicated. The ffmpeg plugin from 22.04 has dependency problems, so it is necessary to use the one from 22.10 and mess with things to get rid of the warnings.

Revision history for this message
Christophe C (batra3) wrote :

On Ubuntu 23.04, the problem seams to be solve on my PC. The ffmpeg plugin (moc-ffmpeg-plugin) works nicely, without any workaround. I have had to restart the computer after the installation of the plugin, no more.

Revision history for this message
Christophe C (batra3) wrote :

i suppose it is the upgrade of glibc (now in 2.37) which solve the problem. The bug can be closed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.