K9copy Segmentation Fault 11

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Deminar

K9copy Segmentation Fault 11

Post by Deminar »

Hi everyone,
I am hoping to get a bit of help. I am not an expert but I can usually figure my way out of stuff. However, I hit a wall this time. I used to run Ubuntu but moved to Mint Nadia (14) with the MATE desktop. I used to use K9copy to backup my kids's favorite DVD but since I moved to MINT I haven't been able to do a single one. I can decrypt the DVD files and save them on my computer but I can never write them to a DVD without the segmentation fault. Here's what I have done:

I have installed all the libdvdread4 (including the libdvdcss2), the ubuntu-restriced-extras, the libdvdcss-dev; libdvdnav-dev and libdvdread-dev. If it makes a difference, I also have the ffmpg stuff installed. Because everything failed, I purged everything using the sudo apt-get purge on everything. I did the autoremove for any unused files left. I re-installed everything fresh and still the same segmentation fault 11. It doesn't matter if I do an ISO or if I just decrypt the VOB files in the temp folder. (I did notice that I had to remove the (-caption) from the start menu for the application to launch.) If there is any further information you require, please let me know and I will provide. I searched all the forums for several days and no threads were able to guide me through a resolution. The most popular thread was for Ubuntu and it was marked as solved but it's far from solved for me.

So here are the backtrace content and please, can anyone help me figure this out?
____________________________________________________________________________________________________
Application: k9copy (k9copy), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb334d740 (LWP 22455))]

Thread 2 (Thread 0xafe96b40 (LWP 22456)):
#0 0xb46d7c64 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#1 0xb4d5b8a4 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#2 0xb3c26f10 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0xb3be5ba0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0xb3be5e61 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0xb51c899f in QEventDispatcherGlib::processEvents (this=0xaf500468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0xb519526c in QEventLoop::processEvents (this=this@entry=0xafe96228, flags=...) at kernel/qeventloop.cpp:149
#7 0xb5195561 in QEventLoop::exec (this=0xafe96228, flags=...) at kernel/qeventloop.cpp:204
#8 0xb508066c in QThread::exec (this=0xa64f150) at thread/qthread.cpp:501
#9 0xb51737bd in QInotifyFileSystemWatcherEngine::run (this=0xa64f150) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb5083a58 in QThreadPrivate::start (arg=0xa64f150) at thread/qthread_unix.cpp:338
#11 0xb46d4d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb4d4dd3e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb334d740 (LWP 22455)):
[KCrash Handler]
#6 ref (this=0x4) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120
#7 QString::operator= (this=0xabd6730, other=...) at tools/qstring.cpp:1410
#8 0x080ebd64 in k9DVD::scandvd (this=0xa6be278, device=..., _quickScan=true) at /build/buildd/k9copy-2.3.8/src/core/k9dvd.cpp:473
#9 0x08098bb1 in k9Main::Open (this=0xa683de0) at /build/buildd/k9copy-2.3.8/src/main/k9main.cpp:489
#10 0xb51aeed6 in QMetaObject::activate (sender=0xa607e08, m=0xb60783b8 <QAction::staticMetaObject>, local_signal_index=1, argv=0xbfdf8fb8) at kernel/qobject.cpp:3547
#11 0xb56fd10d in QAction::triggered (this=this@entry=0xa607e08, _t1=false) at .moc/release-shared/moc_qaction.cpp:277
#12 0xb56fd3ac in QAction::activate (this=0xa607e08, event=QAction::Trigger) at kernel/qaction.cpp:1257
#13 0xb5bf92d0 in trigger (this=<optimized out>) at ../../include/QtGui/../../src/gui/kernel/qaction.h:218
#14 QToolButton::nextCheckState (this=0xa6abf80) at widgets/qtoolbutton.cpp:1144
#15 0xb5b23ee7 in QAbstractButtonPrivate::click (this=this@entry=0xa7dbcc8) at widgets/qabstractbutton.cpp:530
#16 0xb5b241e6 in QAbstractButton::mouseReleaseEvent (this=0xa6abf80, e=0xbfdf9704) at widgets/qabstractbutton.cpp:1123
#17 0xb5bf936d in QToolButton::mouseReleaseEvent (this=0xa6abf80, e=0xbfdf9704) at widgets/qtoolbutton.cpp:718
#18 0xb575d6df in QWidget::event (this=0xa6abf80, event=0xbfdf9704) at kernel/qwidget.cpp:8371
#19 0xb5b235a2 in QAbstractButton::event (this=0xa6abf80, e=0xbfdf9704) at widgets/qabstractbutton.cpp:1082
#20 0xb5bfaa4d in QToolButton::event (this=0xa6abf80, event=0xbfdf9704) at widgets/qtoolbutton.cpp:1160
#21 0xb570439c in QApplicationPrivate::notify_helper (this=0xa46be60, receiver=0xa6abf80, e=0xbfdf9704) at kernel/qapplication.cpp:4562
#22 0xb5709892 in QApplication::notify (this=0xa46be60, receiver=0xa6abf80, e=0xbfdf9704) at kernel/qapplication.cpp:4105
#23 0xb7523e91 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#24 0xb519678e in QCoreApplication::notifyInternal (this=0xbfdf9f08, receiver=0xa6abf80, event=0xbfdf9704) at kernel/qcoreapplication.cpp:915
#25 0xb5705206 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#26 QApplicationPrivate::sendMouseEvent (receiver=0xa6abf80, event=0xbfdf9704, alienWidget=0xa6abf80, nativeWidget=0xa644da8, buttonDown=0xb6095d14 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3173
#27 0xb5790a75 in QETWidget::translateMouseEvent (this=0xa644da8, event=0xbfdf9b2c) at kernel/qapplication_x11.cpp:4622
#28 0xb578f705 in QApplication::x11ProcessEvent (this=0xbfdf9f08, event=0xbfdf9b2c) at kernel/qapplication_x11.cpp:3737
#29 0xb57badc4 in x11EventSourceDispatch (s=0xa46cc68, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0xb3be59e3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0xb3be5d80 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#32 0xb3be5e61 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0xb51c8981 in QEventDispatcherGlib::processEvents (this=0xa43d760, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#34 0xb57ba9aa in QGuiEventDispatcherGlib::processEvents (this=0xa43d760, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0xb519526c in QEventLoop::processEvents (this=this@entry=0xbfdf9e28, flags=...) at kernel/qeventloop.cpp:149
#36 0xb5195561 in QEventLoop::exec (this=0xbfdf9e28, flags=...) at kernel/qeventloop.cpp:204
#37 0xb519acba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#38 0xb5701fc4 in QApplication::exec () at kernel/qapplication.cpp:3823
#39 0x08060f10 in main (argc=1, argv=0xbfdfa0d4) at /build/buildd/k9copy-2.3.8/main.cpp:103
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
DataMan

Re: K9copy Segmentation Fault 11

Post by DataMan »

I don't have a definitive answer for you. The following is a "reach" suggestion... :)

One thing you might want to check out is the cache directory that K9copy is putting files into. Insure that it is large enough and permissions are set correctly.

-DataMan
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

If it helps, this is how the application crashes:

I open the K9copy (or the assistant), I pick the folder where I saved the DVD files and when I click next, that's when I get the segmentation fault.


Thank you, I will look for those folder attributes and post back my findings here.
grepnix

Re: K9copy Segmentation Fault 11

Post by grepnix »

Have you tried running k9copy from a terminal to see if it outputs any useful error messages?

Cheers,
Grepnix
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

Hi,
I have and always obtain the same results. The application launches perfectly. I select my source folder and when I click next, the application crashes with Segmentation Fault 11.
grepnix

Re: K9copy Segmentation Fault 11

Post by grepnix »

Deminar wrote: I can decrypt the DVD files and save them on my computer but I can never write them to a DVD without the segmentation fault.

It doesn't matter if I do an ISO or if I just decrypt the VOB files in the temp folder.

I open the K9copy (or the assistant), I pick the folder where I saved the DVD files and when I click next, that's when I get the segmentation fault.
Are you saying you can create an ISO? If so, can you just run k3b or whatever burning software you have on mate and burn the image to a dvd?

I just installed k9copy on my mint KDE 13 system and did a test run on a DVD and saved a copy as an ISO. Then burnt it with K3B...

Seems fine. On my KDE system these files were also installed :-

apport (version 2.0.1-0ubuntu17.1) will be installed
apport-hooks-medibuntu (version 2) will be installed
apport-symptoms (version 0.16.1) will be installed
dvdauthor (version 0.7.0-1.1build1) will be installed
ffmpeg (version 4:0.8.4-0ubuntu0.12.04.1) will be installed
k9copy (version 2.3.8-1) will be installed
libav-tools (version 4:0.8.4-0ubuntu0.12.04.1) will be installed
libavdevice53 (version 4:0.8.4-0ubuntu0.12.04.1) will be installed
libavfilter2 (version 4:0.8.4-0ubuntu0.12.04.1) will be installed
liblzo2-2 (version 2.06-1) will be installed
mencoder (version 2:1.0~rc4.dfsg1+svn34540-1+medibuntu1) will be installed
python-apport (version 2.0.1-0ubuntu17.1) will be installed

Cheers,
Grepnix
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

Hi, so I looked at the folder and size shouldn't be a problem unless there is something I am not aware of. The VOB files are not too big or unusually big. The permissions are create and delete files. It is not rooted and I shouldn't need to do that. Next step is to try it from the boot disk so it can mimic the single user mode.

I'll try again to decrypt the files to an ISO file and try to write it with K3b. It failed before. The disk is just not readable for some reason. Either my dvd player or linux.

I also confirmed that all the proper packages are installing like Grepnix was saying.
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

I tried doing the image and copying it with K3b and it still doesn't work. Now I don't have the segmentation fault because I don't use k9copy but the image burns successfully, however nothing can read the dvd.

Also, I have checked the region setting of my hardware and that's correct. I think I will have to give DVD95 a try but I had mixed results with that one. I would rather find a way to get K9copy to work as I loved the application.

Thank you for your help and please don't give up. I want to find a way to fix this.
grepnix

Re: K9copy Segmentation Fault 11

Post by grepnix »

Deminar wrote:I tried doing the image and copying it with K3b and it still doesn't work. Now I don't have the segmentation fault because I don't use k9copy but the image burns successfully, however nothing can read the dvd.
Is there anything different about the DVD media that you are using compared to what worked before? Different make etc?

Cheers,
Grepnix
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

Update,
I still can't use K9copy for anything other than creating the ISO files and after a little bit of investigation, I was able to successfully copy the ISO using K3b. I will attempt to repeat that tonight once I am off of work.
I am using a new DVD drive. The ones I had before were older ones and were using the old power connectiors and IDE cables. This one, along with the new computer, is using SATA connections for media and power. I may install a copy of Ubuntu in a Virtual Box and see if I can successfully run K9copy. If I can't, then it would have something to do with the hardware versus the OS.

In the meantime, if you need any other reports of my configurations, either hardware or software, let me know and I will provide.

Regards,

Me.
Deminar

Re: K9copy Segmentation Fault 11

Post by Deminar »

I gave up.

Thank you for your tips.

I resorted to image the disk using K9 and copy it using K3b. (Works for all except newer Disney DVDs.)
grepnix

Re: K9copy Segmentation Fault 11

Post by grepnix »

Deminar wrote:
I resorted to image the disk using K9 and copy it using K3b. (Works for all except newer Disney DVDs.)
Thats the way I've always done it to be honest... I did have some problems with some DVDs and someone suggested that I use vobcopy.

I installed it from the repository and ran their suggested command line (First checking that /dev/sr0 was my dvd drive via ‘fdisk -l’ and changing the output directory to my own)

Code: Select all

vobcopy -b 7.5m -l -i /dev/sr0 -f -o ~/Movies/
This produced a large decrypted file with .VOB as the extension. I ran that through Devede which seemed to hang at the point it creates the .iso file. Undeterred I just renamed the .VOB to .mp4 and tried again. This time it worked and it produced a successful backup! Not sure why it had to be renamed. Maybe if I’d had more patience and waited the first time it would have worked anyway…

Regards,
Grepnix
electroken

Re: K9copy Segmentation Fault 11

Post by electroken »

I think perhaps you solved this issue by updating your hardware. I have found issue with some dvd burners which are related to them being too old to make copies of the latest movies or data disks. Updating codecs is often required. I have to do that often on my windows computer running XP which I use mainly to burn my avi files to disk.
I had been using a dvd drive to burn the avi files on my computer and had chance to have to use it to burn dual layer dvds for a project I was doing and found that my computer/dvd combination was not up to the task. It should have easily burned the dual layer disks as it was not an old dvd burner, but it would fail always when trying to burn a dual layer disk. I tried two or three brands of dvd-9 disks and all failed. When I used the burner on my linux machine to do the same task and using the same brand but different model of the same dvd burner, it would work fine.
I still have the same issue with the other computer and burner after attempting updating etc, so it could be something to do with the dvd burner's laser of mechanical operation.
It is nice to have another computer around that can test for the other one and see if it is the OS or the drive or the software causing the issue.
I hope it all works out ok now, but I think you have found the reason for the failure you had in the past.
Ken
Locked

Return to “Software & Applications”