Stable: 2.5.2
Development: 2.6-alpha3
Moc 2.5.0-beta1 won't open after upgrading to Xubuntu 13.10, constantly segfaults in strcmp on startup:
noccy@noccy-aspire:/tmp/moc-2.5.0~beta1+svn20130411$ mocp
Segmentation fault
noccy@noccy-aspire:/tmp/moc-2.5.0~beta1+svn20130411$ mocp -D
Segmentation fault
noccy@noccy-aspire:/tmp/moc-2.5.0~beta1+svn20130411$ mocp --debug
Segmentation fault
GDB trace:
(gdb) run
Starting program: /tmp/moc-2.5.0~beta1+svn20130411/mocp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
__strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:38
38 ../sysdeps/i386/i686/multiarch/../strcmp.S: No such file or directory.
(gdb) backtrace
#0 __strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:38
#1 0xb7c5774c in rccGetRealLanguage () from /usr/lib/librcc.so.0
#2 0xb7c5798a in rccGetCurrentLanguage () from /usr/lib/librcc.so.0
#3 0xb7c58a8c in rccGetCurrentConfig () from /usr/lib/librcc.so.0
#4 0xb7c55e60 in rccRegisterLanguage () from /usr/lib/librcc.so.0
#5 0xb7c567aa in rccCreateContext () from /usr/lib/librcc.so.0
#6 0xb7c5695a in rccInitDefaultContext () from /usr/lib/librcc.so.0
#7 0x08082916 in rcc_init () at rcc.c:64
#8 0x08053fb9 in main (argc=1, argv=0xbfffeca4) at main.c:845
(gdb)
jcf
Thu, 2013-10-10 05:34
Permalink
Versions, Please
Can you tell me, as precisely as possible, the version of librcc you are linking against?
riesebie
Mon, 2013-10-14 19:09
Permalink
I installed XUBUNTU-amd64
I installed XUBUNTU-amd64 13.10-beta2 in a chroot. Running mocp segfaulted with almost the same backtrace:
Ubuntu uses the same libc6 and librcc0 versions as Debian's sid where moc runs fine. Recompiling moc
--without-rcc
makes moc working in (X)Ubuntu. It seems that librcc0 (librcc-dev) or locale is somewhat broken. Please file a Ubuntu bug. Is it possible to mark such a bug as release critical?--
Elimar
jcf
Mon, 2013-10-14 20:12
Permalink
Doubtful From The Start
Thanks for confirming my initial doubts about this bug actually being in MOC code, Elimar. If you, "noccy", can file that bug report with Ubuntu we will track it.
riesebie
Tue, 2013-10-15 19:16
Permalink
Hi Gents, I built Debian
Hi Gents,
I built Debian packages of librcc-0.2.10 at XUbuntu 13.10-beta2 upgraded as of today and updated the installed 0.2.9 version. Did a rebuild of moc against librcc-dev 0.2.10-0ubuntu1 and......... It works ;-) This is done on a amd64 machine. I'll investigate on how to push this into the BTS of "Amazontu" on weekend. For now I have to relax a bit, though. Rest of the week I am quite busy.
Elimar
Debian's moc maintainer
Marslo
Thu, 2013-10-31 00:34
Permalink
Any news? I don't want using
Any news?
I don't want using cmus anymore....
jcf
Thu, 2013-10-31 02:08
Permalink
It's Out of Our Hands
If you followed the thread posted by Elimar you would have seen that it's not a MOC problem but something to do with Ubuntu's build of the librcc package. Unfortunately, this is not a MOC problem and therefore we cannot fix it in MOC. (I was going to post that a little earlier but decided to wait a little longer to see if there was any resolution at the Ubuntu end.)
One possible workaround would be to replace the Ubuntu librcc package by the Debian one, which is demonstrated to have worked. But I don't know enough about the Debian and Ubuntu packaging systems to instruct you on this.
Of course, if you don't actually need RCC support you could build MOC using the
--without-rcc
option onconfigure
, but I suspect you're not into building MOC from source.Marslo
Wed, 2013-11-06 18:46
Permalink
Error shows
What will happen by building moc without rcc?
Here error shows after built and install it:
Here is the gdb information:
My sound card is alsa
I'v installed the libdb++-dev, libdb-dev and libltdl-dev
Here my system information:
How can I fix this issue?
Thanks in advanced.
Marslo
Marslo
Wed, 2013-11-06 19:01
Permalink
Error fixed
Okay, accroding to this post , I insalled the following packages:
My moc works finally!! ^_^
Marslo
jcf
Wed, 2013-11-06 19:36
Permalink
Exactly
Yes, I just logged in to post that you would need additional '-dev' packages and saw your happy news.
The Ubuntu packagers still don't seem to have responded to this problem on their thread.
Marslo
Wed, 2013-11-06 19:40
Permalink
Thanks
Yeah, it'a a hard way, but I made it, :)
And, I made the basic Q&A
jcf
Wed, 2013-11-06 19:48
Permalink
Recent README Edit
I recently included a note in MOC's README file regarding the need for '-dev' packages on Debian-based distributions:
You may not have been using a recent enough version of MOC to have seen that, however.
Marslo
Wed, 2013-11-06 20:00
Permalink
My bad
Okay. Thayt's my bad. ignore README is my bad habit. I must to develop good habits.
Marslo
Wed, 2013-11-06 19:46
Permalink
what will happed without rcc
I still want to know what will happed without rcc?
Thanks.
Marslo
jcf
Wed, 2013-11-06 20:01
Permalink
Nothing Too Bad
MOC uses RCC to handle national character encodings in displayed filenames. If you only use ASCII filenames then there'll be no difference; if you have non-ASCII characters, then some filenames may not look as they should.
jcf
Wed, 2013-11-20 09:13
Permalink
Movement, At Last
The Ubuntu thread is now showing the problem as fixed (librcc-0.2.9-3.1ubuntu0.1) and working its way through the Ubuntu release process.
riesebie
Wed, 2013-10-16 07:32
Permalink
Please notice
Please notice https://bugs.launchpad.net/ubuntu/+source/librcc/+bug/1183580
ldanko
Fri, 2013-10-18 11:24
Permalink
mocp crash
I got the same error on standard Ubuntu 13.10