k3b in amd64 lucid freezes after ripping a CD to flac or after convering a cue+audio file to flac

ah:

k3b:
  Installed: 1.91.0~rc2-0ubuntu3
  Candidate: 1.91.0~rc2-0ubuntu3
  Version table:
 *** 1.91.0~rc2-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

I can confirm this bug on a 32bit installation when ripping and encoding to mp3. Same terminal output here. I think this happens anytime you try to rip, no matter what installation. The output suggests an error in the gui-engine, but that is just a guess.

same here on Kubuntu 10.04 64bit

This bug is probably related: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/576563
Shows the same behavior but using lame instead of flac.

That bug is a duplicate of this one, in fact. Thanks for spotting it.

I can confirm this on AMD64 Kubuntu 10.04 using lame MP3.
The audio file gets written ok, but K3B never pops up the completed window, nor does it make the little 'honk' sound. Instead the K3B process just sits there and sucks up 100% of one of my cores until I kill it.

This started happening after I upgraded from 9.10.

I ran K3B session from command line and did not see any carping.

On that same note...is anyone else experiencing their Kubuntu desktop 'freezing up' for 30 seconds or so every so often after upgrading from 9.10 to 10.4? If so, could you kindly direct me to the bug report for that?

I'm wondering if is this is not so much a bug with K3B but a problem at a lower level.

I get exactly the same problem. I burn an audio cd, the burn process completes but i have to 'force quit' to close k3b. I am running Ubuntu Lucid (64 bit version). Although Brasero is pre-installed in Ubuntu, I have had so much trouble using it, that I use K3b in preference.

As Antonio reported, It was working ok on 9.10 before the upgrade.

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/KDE. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Seeing it here when using lame as the external encoder. K3b is 100% unusable for ripping CD to mp3... On to SoundKonverter.

Same problem here. I hope a fix is in the works.

This bug was fixed in the package k3b - 2.0.1-1ubuntu1

---------------
k3b (2.0.1-1ubuntu1) maverick; urgency=low

  [ Jonathan Thomas ]
  * Merge from Debian Unstable, remaining changes:
    - Do not add build-depend on libdvdread-dev (universe)
    - Suggest, not recommend libk3b6-extracodecs (multiverse)
    - Do not install unused scalable icons to save space
    - Keep kubuntu_02_kubuntu_restricted.diff
    - Keep kubuntu_03_no_missing_mp3_warn.diff
    - Disable 111_advice_debian_libk3b3-extracodes.diff, the above two patches
      take care of this for us (without string changes, too)
    - Disable 112_dont_require_mp3.diff, it causes the package to FTBFS
    - Keep Kubuntu l10n stuff in debian/rules
    - Don't ship docs, as of 2.0 they are not so good
    - Disable the k3b-i18n package. Rosetta handles the translations since
      k3b is in main, and we aren't shipping docs at the moment for k3b
  * The new upstream release fixes LP: #576500

  [ Felix Geyer]
  * Remove accidentally added patch debian-changes-1.92.0~rc3-1ubuntu1
 -- Jonathan Thomas <email address hidden> Wed, 18 Aug 2010 14:36:05 -0400

When can we expect a backport for 10.04 LTS?

On Sun, 22 Aug 2010, Kevin Krumwiede wrote:

> When can we expect a backport for 10.04 LTS?

I got tired of waiting and built 2.0.1 from the source deb on Lucid. It
claims it needs a newer pkg-kde-tools and kdelibs5-dev than the ones with
10.04, but I simply edited the debian/control file to accept what was on
the box. It built and works fine.

Really irritates me when the stated requirements lock you out of
backporting for no good reason.

--

It seems that there is another one finding weird that distros care for new features and not for good working of what is in the field. Micr* style.

I suspect a fixed package would have been released months ago if k3b started with a 'g' instead of a 'k'. For whatever reason, nothing in Kubuntu/KDE ever seems to get fixed until the next distro comes along.

don't know, there's a lot of g-bugs, let's entertain them till they find us so ugly they want to get rid of us...ahhhhhh...

Since an upstream task for Fedora would be to show the bug report number for Fedora, opening it and marking it opinion is not a correct use for that status.

@Antonio & Steven: Yeah, I didn't install a LTS release so I could build my own backports. :(

@Steven: I ended up building 2.0.1 on lucid, removing the version requirements from the two unsatisfied dependencies as you suggested.

Speaking of unnecessary dependencies, look what I saw on the console as it was building. (attachment)

Since seven different binary debs end up getting built, it's possible that one or more of them does need those dependencies. I'm not an expert in the Debian build system (and it seems most of the documentation is incomplete or out-of-date, but that's another rant for another time) but perhaps you're seeing those from a component that doesn't have the requirement?

will there ever be a fix to this bug in lucid lynx??