Ticket #32 (closed defect: invalid)

Opened 2 years ago

Last modified 2 years ago

can't start museekd from museeq

Reported by: silver@… Owned by: daelstorm
Priority: major Milestone:
Component: museeq Version: 0.1.11
Keywords: Cc:

Description

I tried Museek+ on FreeBSD 6.0 (KDE 3.5.3, QT 3.3.6), installed from newly created FreeBSD-port (http://www.freshports.org/net-p2p/museekplus).

In the connection dialog, I'd like Museeq to start museekd, so I click on "Daemon Options...", select /usr/home/silver/.museekd/config.xml into "Museek Daemon Config:" and click "Start Daemon". In Museeq status I see: "No Config for Museek Daemon selected, giving up..." and as I started museeq from commandline, I see in console: "QSettings::sync: filename is null/empty". So I can't autostart museekd from museeq, which is pretty uncomfortable for ordinary users.

Attachments

Change History

Changed 2 years ago by silver@…

Resolved! I just wasn't owner of ~/.qt - I guess it was created while executing smth with sudo.

Changed 2 years ago by gandalf

  • status changed from new to closed
  • resolution set to invalid

Add/Change #32 (can't start museekd from museeq)

Author



Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.