can you explain how you make it crash please ?

Created attachment 63414 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3

- What I was doing when the application crashed:

Had a video DVD in the drive, clicked the entry for it in the upper left of K3b.

-- Backtrace (Reduced):
#6  0x0000003f0017b355 in K3b::VideoDVD::VideoDVD::open (this=0x26189f8, dev=0x23c44c0) at /usr/src/debug/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:227
#7  0x000000000054d9f9 in K3b::VideoDVDRippingView::reloadMedium (this=0x2616400) at /usr/src/debug/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#8  0x000000000050e488 in K3b::DirView::showMediumInfo (this=0x25869c0, medium=...) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:193
#9  0x000000000050e6a2 in K3b::DirView::showDevice (this=0x25869c0, dev=0x23c44c0) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:167
#10 0x000000000050ef8c in K3b::DirView::qt_metacall (this=0x25869c0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff62e08490) at /usr/src/debug/k3b-2.0.2/x86_64-redhat-linux-gnu/src/k3bdirview.moc:99

Attached gdb and reproduced the crash; got the following output before the SEGV:

libdvdread: Using libdvdcss version 1.2.10 for DVD access

*** libdvdread: CHECK_VALUE failed in /builddir/build/BUILD/libdvdread-4.1.4/src/ifo_read.c:1203 ***
*** for vts_ptt_srpt->title[i].ptt[j].pgn != 0 ***


*** libdvdread: CHECK_VALUE failed in /builddir/build/BUILD/libdvdread-4.1.4/src/ifo_read.c:1914 ***
*** for pgci_ut->nr_of_lus < 100 ***

Please send bug report - no VTS_TMAPT ?? 

Program received signal SIGSEGV, Segmentation fault.
0x0000003f0017b355 in K3b::VideoDVD::VideoDVD::open (this=0xe4b8d8, dev=0xd6b320)
    at /usr/src/debug/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:227
227                                                              convertFrameRate(cur_pgc->cell_playback[j].playback_time.frame_u) );
[...]
(gdb) print cur_pgc->cell_playback
$3 = (cell_playback_t *) 0x0

(gdb) print *cur_pgc
$13 = {
  zero_1 = 0, 
  nr_of_programs = 0 '\000', 
  nr_of_cells = 0 '\000', 
  playback_time = {
    hour = 0 '\000', 
    minute = 0 '\000', 
    second = 0 '\000', 
    frame_u = 64 '@'
  }, 
  prohibited_ops = {
    zero = 0, 
    video_pres_mode_change = 0, 
    karaoke_audio_pres_mode_change = 0, 
    angle_change = 0, 
    subpic_stream_change = 0, 
    audio_stream_change = 0, 
    pause_on = 0, 
    still_off = 0, 
    button_select_or_activate = 0, 
    resume = 0, 
    chapter_menu_call = 0, 
    angle_menu_call = 0, 
    audio_menu_call = 0, 
    subpic_menu_call = 0, 
    root_menu_call = 0, 
    title_menu_call = 0, 
    backward_scan = 0, 
    forward_scan = 0, 
    next_pg_search = 0, 
    prev_or_top_pg_search = 0, 
    time_or_chapter_search = 0, 
    go_up = 0, 
    stop = 0, 
    title_play = 0, 
    chapter_search_or_play = 0, 
    title_or_time_play = 0
  }, 
  audio_control = {0, 0, 0, 0, 0, 0, 0, 0}, 
  subp_control = {0 <repeats 32 times>}, 
  next_pgc_nr = 2, 
  prev_pgc_nr = 3, 
  goup_pgc_nr = 0, 
  still_time = 0 '\000', 
  pg_playback_mode = 0 '\000', 
  palette = {0 <repeats 16 times>}, 
  command_tbl_offset = 236, 
  program_map_offset = 0, 
  cell_playback_offset = 0, 
  cell_position_offset = 0, 
  command_tbl = 0x128c2a0, 
  program_map = 0x0, 
  cell_playback = 0x0, 
  cell_position = 0x0
}

*** Bug 283496 has been marked as a duplicate of this bug. ***

Created attachment 71012 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

- What I was doing when the application crashed:
* Inserted a DVD and selected Rip Video DVD with k3b from media mounting message in taskbar. Crash was imediate. Repeated.
* Opened k3b and selected Rip Video DVD from Tools menu. Crashed immediately on selection. 
* Changed from SuSE 11.4 install to slightly newer version from packman repository, retired last step. Crash was still imediate.
* Removed DVD from drive. Selected Rip Video DVD from Tools menu. Message pop-up asked me to insert media. I returned the DVD to the drive and closed tray. After a few moments the DVD title appeared as a selection. When I selected the title application crashed.

-- Backtrace (Reduced):
#6  0x00007f184b78b69b in K3b::VideoDVD::VideoDVD::open (this=0xb41538, dev=0x9a26d0) at /usr/src/debug/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:130
#7  0x000000000054dc1f in K3b::VideoDVDRippingView::reloadMedium (this=0xb3eec0) at /usr/src/debug/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#8  0x000000000050cf98 in K3b::DirView::showMediumInfo (this=0xa48f60, medium=...) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:193
#9  0x000000000050d1af in K3b::DirView::showDevice (this=0xa48f60, dev=0x9a26d0) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:167
#10 0x00000000005154d2 in K3b::MainWindow::videoDvdRip (this=0x9f04f0, dev=0x9a26d0) at /usr/src/debug/k3b-2.0.2/src/k3b.cpp:1603

Created attachment 71043 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4

I reported on this issue a couple days ago (comment 6). It had been a while since I had updated my system, so the other night I re-installed using SuSE 12.1. Unfortunately k3b is still giving me the same crash behavior as before.

-- Backtrace (Reduced):
#6  0x00007f8cd9326a73 in K3b::VideoDVD::VideoDVD::open (this=0xb38cd8, dev=0xa2def0) at /usr/src/debug/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:130
#7  0x0000000000553e69 in K3b::VideoDVDRippingView::reloadMedium (this=0xb36730) at /usr/src/debug/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#8  0x00000000005140d8 in K3b::DirView::showMediumInfo (this=0x9f1bd0, medium=...) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:193
#9  0x00000000005142f2 in K3b::DirView::showDevice (this=0x9f1bd0, dev=0xa2def0) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:167
#10 0x000000000051ca54 in K3b::MainWindow::videoDvdRip (this=0x9adc40, dev=0xa2def0) at /usr/src/debug/k3b-2.0.2/src/k3b.cpp:1603

This behaviour has occurred for me since Kubuntu Oneiric (2011). 

It happens with hardware I have been successfully using to burn DVDs and D/L DVDs on Kubuntu for years.

It only happens when burning more than 3.8 GB of data onto a DVD. I have no problems burning DVDs with less data on them than that. It happens no matter whether I am using k3b, k9copy, or even Brasero or Gnomebaker.

The symptoms are freezing when data burned reaches about 3.9 GB, or a k3b abort, or an unusable/unreadable disc, or the mysterious "error 254."

It makes me think there is a problem with wodim and/or genisoimage/growisofs, which Debian-based systems have substituted in their cdrkit for cdrecord and mkisofs of cdrtools.

Further, k3b currently allows no method for selecting the writing package even when cdrtools (cdrecord and mkisofs) is once again installed.

This behaviour has occurred for me since Kubuntu Oneiric (2011). 

It happens with hardware I have been successfully using to burn DVDs and D/L DVDs on Kubuntu for years.

It only happens when burning more than 3.8 GB of data onto a DVD. I have no problems burning DVDs with less data on them than that. It happens no matter whether I am using k3b, k9copy, or even Brasero or Gnomebaker.

The symptoms are freezing when data burned reaches about 3.9 GB, or a k3b abort, or an unusable/unreadable disc, or the mysterious "error 254."

It makes me think there is a problem with wodim and/or genisoimage/growisofs, which Debian-based systems have substituted in their cdrkit for cdrecord and mkisofs of cdrtools.

Further, k3b currently allows no method for selecting the writing package even when cdrtools (cdrecord and mkisofs) is once again installed.

If I'm not mistaken, genisoimage is used for DVDs and growisofs is used for D/L DVDs, and each preconfigures data for wodim to write. Something is wrong with this chain of writing events...

*** Bug 302322 has been marked as a duplicate of this bug. ***

*** Bug 303824 has been marked as a duplicate of this bug. ***

*** Bug 315177 has been marked as a duplicate of this bug. ***

Created attachment 79847 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:
just starting the program to copy a dvd.  crashes before it ever opens.

-- Backtrace (Reduced):
#5  0x00007f4cad0e9a47 in K3b::VideoDVD::VideoDVD::open (this=0x2761128, dev=0x23724a0) at /build/buildd/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:227
#6  0x0000000000536335 in K3b::VideoDVDRippingView::reloadMedium (this=0x275ebb0) at /build/buildd/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#7  0x00000000004fbcf0 in K3b::DirView::showMediumInfo (this=this@entry=0x23576e0, medium=...) at /build/buildd/k3b-2.0.2/src/k3bdirview.cpp:193
#8  0x00000000004fbef2 in K3b::DirView::showDevice (this=0x23576e0, dev=dev@entry=0x23724a0) at /build/buildd/k3b-2.0.2/src/k3bdirview.cpp:167
#9  0x0000000000503c0e in K3b::MainWindow::videoDvdRip (this=0x2320750, dev=0x23724a0) at /build/buildd/k3b-2.0.2/src/k3b.cpp:1603

Created attachment 82101 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.10.5 using Qt 4.8.5

This looks like there are libdvdread errors - some of which have been addressed since the last release a long time ago; regardless, k3b should catch errors instead of crashing.

-- Backtrace (Reduced):
#6  0x00007f2ff1c9d07c in K3b::VideoDVD::VideoDVD::open (this=0x29685b8, dev=<optimized out>) at /usr/src/debug/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:227
#7  0x0000000000536f67 in K3b::VideoDVDRippingView::reloadMedium (this=0x2965f50) at /usr/src/debug/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#8  0x00000000004fd190 in K3b::DirView::showMediumInfo (this=this@entry=0x28e2200, medium=...) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:193
#9  0x00000000004fd346 in K3b::DirView::showDevice (this=0x28e2200, dev=0x27712d0) at /usr/src/debug/k3b-2.0.2/src/k3bdirview.cpp:167
#10 0x00000000004fdc6c in K3b::DirView::qt_static_metacall (_o=0x28e2200, _id=1, _a=0xa2a019d0, _c=<optimized out>) at /usr/src/debug/k3b-2.0.2/x86_64-redhat-linux-gnu/src/k3bdirview.moc:75

Created attachment 82905 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.9.5 using Qt 4.8.3

- What I was doing when the application crashed:

As all the others were doing: Trying to rip a DVD, in this particular case one that VLC would not play because auf a segfault in libdvdread (sound familiar? :-P), hoping the issue was with vlc and not libdvdread... No idea how much you guys can do about it, but if I can help (I'm perfectly happy to attach a debugger and look at whatever someone with knowledge of the internals involved points me too ;-))

-- Backtrace (Reduced):
#5  0x00007f661d160a97 in K3b::VideoDVD::VideoDVD::open (this=0x1f4af18, dev=0x1bc57f0) at /build/buildd/k3b-2.0.2/libk3b/videodvd/k3bvideodvd.cpp:227
#6  0x00000000005363b5 in K3b::VideoDVDRippingView::reloadMedium (this=0x1f489d0) at /build/buildd/k3b-2.0.2/src/rip/videodvd/k3bvideodvdrippingview.cpp:217
#7  0x00000000004fbd70 in K3b::DirView::showMediumInfo (this=this@entry=0x1d57b70, medium=...) at /build/buildd/k3b-2.0.2/src/k3bdirview.cpp:193
#8  0x00000000004fbf72 in K3b::DirView::showDevice (this=0x1d57b70, dev=0x1bc57f0) at /build/buildd/k3b-2.0.2/src/k3bdirview.cpp:167
#9  0x0000000000503c8e in K3b::MainWindow::videoDvdRip (this=0x1b4e260, dev=0x1bc57f0) at /build/buildd/k3b-2.0.2/src/k3b.cpp:1603

*** Bug 320672 has been marked as a duplicate of this bug. ***

*** Bug 332723 has been marked as a duplicate of this bug. ***

Is this bug still valid when using current k3b packages from Packman?

If yes, please provide a new backtrace and full console output:
$ kdebugdialog --on k3b
$ k3b

When providing information please set status to "CONFIRMED".

Created attachment 90540 [details]
New crash information added by DrKonqi

k3b (2.0.80) on KDE Platform 4.14.4 using Qt 4.8.5

- What I was doing when the application crashed:
Opened K3B from the KDE context-menu for the DVD "Merida" that I put in my optical drive. Immediately  the "KDE crash manager" pops up and proposed me to restart the application (K3B).
I did it and then I selected 'Extract DVD titles ' from 'Other actions' popup menu: K3B crashed again.

-- Backtrace (Reduced):
#6  0x00007f2c73a2e443 in K3b::VideoDVD::VideoDVD::open (this=0x1c19c08, dev=<optimized out>) at /usr/src/debug/k3b/libk3b/videodvd/k3bvideodvd.cpp:228
#7  0x00000000004f76f7 in K3b::VideoDVDRippingView::reloadMedium (this=0x1c16d60) at /usr/src/debug/k3b/src/rip/videodvd/k3bvideodvdrippingview.cpp:275
#8  0x000000000051dce0 in K3b::DirView::showMediumInfo (this=this@entry=0x1b72c30, medium=...) at /usr/src/debug/k3b/src/k3bdirview.cpp:192
#9  0x000000000051de92 in K3b::DirView::showDevice (this=0x1b72c30, dev=dev@entry=0x20b5d10) at /usr/src/debug/k3b/src/k3bdirview.cpp:166
#10 0x00000000005221ec in K3b::MainWindow::videoDvdRip (this=0x18186f0, dev=0x20b5d10, dev@entry=0x0) at /usr/src/debug/k3b/src/k3b.cpp:1495

Created attachment 91184 [details]
New crash information added by DrKonqi

k3b (2.0.3) on KDE Platform 4.14.5 using Qt 4.8.6

- What I was doing when the application crashed:

starting k3b with a dvd in drive /dev/sr1. This is a duplicate for bugs found with k3b, but the same problem happened in the same way with k9copy also (consistently) if that will help you. All updates current were installed on my system at the time of the crash.

-- Backtrace (Reduced):
#5  0x00007f017c7e2f39 in K3b::VideoDVD::VideoDVD::open(K3b::Device::Device*) () at /lib64/libk3blib.so.6
#6  0x0000000000542f47 in K3b::VideoDVDRippingView::reloadMedium() ()
#7  0x00000000005063c8 in K3b::DirView::showMediumInfo(K3b::Medium const&) ()
#8  0x0000000000506557 in K3b::DirView::showDevice(K3b::Device::Device*) ()
[...]
#11 0x000000000050263a in K3b::FileTreeView::slotClicked(QModelIndex const&) ()

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!