This forum has been archived. All content is frozen. Please use KDE Discuss instead.

mp4/m4a track change cauases crash

Tags: None
(comma "," separated)
bradfucious
Registered Member
Posts
2
Karma
0

mp4/m4a track change cauases crash

Wed Nov 29, 2006 3:49 pm
I'm having an odd little problem with Amarok at present (only since reinstalling Ubuntu):

I can play mp3 files, ogg files and mp4/m4a files without any hiccoughs, but when Amarok changes tracks to an mp4/m4a file or away from an mp4/m4a file, it first hangs up for about 5-7 seconds, then gives me a new window that states:

"Cound not Launch Mail Client"

At this point, my only way out of the new window or Amarok is to do a force quit.  My temporary solution has been to just remove all of the mp4/m4a files from my playlists (there are only about 300 or so tracks in this format), but that's not really a great way to address this type of issue.

About the system:
Ubuntu 6.06 AMD64
Amarok 1.4.3

As stated, I didn't begin having this problem until a recent reinstall of the OS (due to a previous poor partitioning job on my part), at which point I went from using the x86 version of Ubuntu 6.06 to the AMD64 version of 6.06.  All installed packages are the exact same (though some additional ones have been added, but those pertain more to graphics and encryption than they do to multimedia), just optimized for my architecture.

Any thoughts would be appreciated, as I've basically run out of ideas here...
Martin Aumueller
KDE Developer
Posts
219
Karma
0
I remember having had problems with the xine libraries in version 1.1.1 on amd64 while the very same version of the libraries on ia32 worked w/o problems. And to my knowledge, dapper has libxine 1.1.1, whereas edgy has 1.1.2.
bradfucious
Registered Member
Posts
2
Karma
0
You are correct sir, 1.1.1 is what's being used.

Problem is, the past two times that I've tried migrating from Dapper to Edgy, I've ended up with file systems so corrupted that I couldn't even get in successfully in single user mode.

I'm looking at going back to 32bit because of some...lets call them oddities that I've encountered with the 64bit install.

Thanks for your input, sir.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]