Could not open mp3 from a zip, when viewed the zipped folder inside Dolphin

[sipiatti]

Binary package hint: kdebase

Hi I came across a Dolphin bug. When you set Dolphin to display a zip content inside its window, you cannot start playing an mp3.
I tried it with Amarok and also VLC. I think they receive an urlencoded filepath to the related mp3 file what they parse as normal utf string. I tried other filetypes like txt and pdf, they worked with Kate and Okular.
On the other hand when I set Dolphin to not display a zip in its window, but open it with Ark I can start playing the mp3 from the Ark window.
Anyway, the type of archive is irrelevant. Everything is the same with tar.gz.

Kubuntu 9.10

ProblemType: Bug
Architecture: amd64
Date: Tue Jan 19 21:13:47 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/dolphin
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: dolphin 4:4.3.2-0ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: kdebase
Uname: Linux 2.6.31-17-generic x86_64
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2161): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:2334): GLib-WARNING **: g_set_prgname() called multiple times
 (npviewer.bin:2397): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: hibás ELF osztály: ELFCLASS64
 (npviewer.bin:2397): Gdk-WARNING **: XID collision, trouble ahead
 (npviewer.bin:2397): Gdk-WARNING **: XID collision, trouble ahead

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

[sipiatti (sipiatti)]

Ok, I've reported there too: https://bugs.kde.org/show_bug.cgi?id=223539