[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#264189: marked as done (Konqueror won't save file association settings)

Your message dated Sun, 14 May 2006 17:31:02 -0400
with message-id <200605141731.04021.chrsmrtn@debian.org>
and subject line konqueror: File Type Associations Cannot Be Set
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: konqueror
Version: 4:3.2.3-1
When I open an mp3 file in Konqueror, I'm shown the "Open with:" dialog. I select XMMS, check "Remember application association for this type of file", and click OK. XMMS opens. All okay so far...
Later I click on another mp3 file, expecting Konqueror to remember that it should open it with xmms... but it doesn't, and I have to go through the "Open with" process again. 

This happens continuously.

As an alternative, I tried clicking Settings -> Configure Konqueror,
going into the File Associations section, and setting XMMS up there.
The result this time is that as soon as I close the Configure dialog, Konqueror has again forgotten the settings.
This message shows up in .xsession-errors each time I instruct Konqueror to save its settings: 


kbuildsycoca running...
Reusing existing ksycoca


Any idea what might be happening here?

Thanks

-- graham

--- End Message ---
--- Begin Message --- 
Version: 4:3.5.2-1

I'm closing the classic "File Associations Can't be Set" bugs since 
there have been no reported of this problem for a good long while. I 
myself stopped experiencing it some time ago.

Let us know (better, let upstream know) if these problems persist with 
KDE 3.5.2+. Thanks.

--- End Message ---
Reply to: