media kioslave crashes, causes konq to crash too

2005-09-08 Thread Daniel Andor
Hi All,

I set up dbus, hal, and pmount as per the thread on this list, and media:/ 
appears initially at least to work as expected.  However, 'doing' anything to 
one of the devices - even hovering over one with a mouse - causes konqueror 
to crash with a segmentation fault.  Even if I haven't inserted a thing into 
any drives, just hover over one of the mounted harddiscs.

How can I find out what's causing the problem?  To begin with, here are the 
debian package versions:

$ dpkg -l | egrep ^ii.*(hal|dbus|pmount|kio) | cut -c-60
ii  dbus-10.23.4-6
ii  dbus-1-utils  0.23.4-6
ii  dbus-glib-1   0.23.4-6
ii  dbus-qt-1c2   0.23.4-6
ii  hal   0.4.8-7
ii  hal-device-manager0.4.8-7
ii  kdebase-kio-plugins   3.4.2-2
ii  kdemultimedia-kio-plugins 3.4.2-2
ii  kdepim-kio-plugins3.4.2-1
ii  libhal-storage0   0.4.8-7
ii  libhal0   0.4.8-7
ii  pmount0.8-2

$ uname -a
Linux pooh 2.6.12-1-k7 #1 Tue Aug 16 22:48:25 UTC 2005 i686 GNU/Linux

dmesg doesn't give a clue. 

Advice would be appreciated!
Thanks,
Daniel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: media kioslave crashes, causes konq to crash too

2005-09-08 Thread Daniel Andor
On Thursday 08 September 2005 7:56 pm, David Pye wrote:
 On Thursday 08 September 2005 15:44, Daniel Andor wrote:
  I set up dbus, hal, and pmount as per the thread on this list, and
  media:/ appears initially at least to work as expected.  However, 'doing'
  anything to one of the devices - even hovering over one with a mouse -
  causes konqueror to crash with a segmentation fault.  Even if I haven't
  inserted a thing into any drives, just hover over one of the mounted
  harddiscs.

 I presume the KCrash handler appears to announce this.

Yes

 What does the backtrace look like?

Ah, initially it repeatedly said no debugging symbols, and I assumed this to 
be normal since I'd presumed debian binaries probably had symbols stripped, 
but then a few seconds later the extract at the bottom came up.

Do I need to be worrying about C and C++ library versions?  I wonder why arts 
and soundserver stuff is mentioned...?

Thanks,
Daniel.
Backtrace:
[New Thread -1230718080 (LWP 6839)]
[KCrash handler]
#3  0xb5bc0dea in __gnu_cxx::__mt_allocstd::string, 
__gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true 
::allocate(unsigned, void const*) ()
   from /usr/lib/libsoundserver_idl.so.1
#4  0xb583a2a1 in Arts::TraderOffer_impl::TraderOffer_impl(std::string const, 
std::string const) () from /usr/lib/libmcop.so.1
#5  0xb583aa25 in Arts::TraderHelper::addDirectory(std::string const, 
std::string const, std::mapstd::pairunsigned long long, unsigned long, 
bool, std::lessstd::pairunsigned long long, unsigned long , 
std::allocatorstd::pairstd::pairunsigned long long, unsigned long const, 
bool  *) ()
   from /usr/lib/libmcop.so.1
#6  0xb583a96e in Arts::TraderHelper::addDirectory(std::string const, 
std::string const, std::mapstd::pairunsigned long long, unsigned long, 
bool, std::lessstd::pairunsigned long long, unsigned long , 
std::allocatorstd::pairstd::pairunsigned long long, unsigned long const, 
bool  *) ()
   from /usr/lib/libmcop.so.1
#7  0xb583aff2 in Arts::TraderHelper::load() () from /usr/lib/libmcop.so.1
#8  0xb583b1f0 in Arts::TraderHelper::TraderHelper() ()
   from /usr/lib/libmcop.so.1
#9  0xb583b384 in Arts::TraderHelper::the() () from /usr/lib/libmcop.so.1
#10 0xb583b3f6 in Arts::TraderQuery_impl::query() () 
from /usr/lib/libmcop.so.1
#11 0xb5c0698d in KonqSoundPlayerImpl::mimeTypes() ()
   from /usr/lib/kde3/konq_sound.so
#12 0xb671da6d in KonqIconViewWidget::slotOnItem(QIconViewItem*) ()
   from /usr/lib/libkonq.so.4
#13 0xb673b95a in KonqIconViewWidget::qt_invoke(int, QUObject*) ()
   from /usr/lib/libkonq.so.4
#14 0xb73a3239 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#15 0xb76ee56d in QIconView::onItem(QIconViewItem*) ()
   from /usr/lib/libqt-mt.so.3
#16 0xb75553cd in QIconView::contentsMouseMoveEvent(QMouseEvent*) ()
   from /usr/lib/libqt-mt.so.3
#17 0xb670f828 in KonqIconViewWidget::contentsMouseMoveEvent(QMouseEvent*) ()
   from /usr/lib/libkonq.so.4
#18 0xb74b502f in QScrollView::viewportMouseMoveEvent(QMouseEvent*) ()
   from /usr/lib/libqt-mt.so.3
#19 0xb74b1d5c in QScrollView::eventFilter(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#20 0xb754ef24 in QIconView::eventFilter(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#21 0xb73a2fea in QObject::activate_filters(QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#22 0xb73a3074 in QObject::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#23 0xb73da142 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#24 0xb7346b95 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#25 0xb7347938 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#26 0xb79686fc in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#27 0xb72e3fb8 in QETWidget::translateMouseEvent(_XEvent const*) ()
   from /usr/lib/libqt-mt.so.3
#28 0xb72e2921 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libqt-mt.so.3
#29 0xb72f5698 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/libqt-mt.so.3
#30 0xb735c73b in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#31 0xb735c654 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#32 0xb73465cf in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#33 0xb67fd10c in kdemain () from /usr/lib/libkdeinit_konqueror.so
#34 0xb6845550 in kdeinitmain () from /usr/lib/kde3/konqueror.so
#35 0x0804deed in ?? ()
#36 0x0002 in ?? ()
#37 0x080d7ef0 in ?? ()
#38 0xbf9e9338 in ?? ()
#39 0x0804df11 in ?? ()
#40 0x1000 in ?? ()
#41 0xb7d890a4 in free () from /lib/tls/libc.so.6
#42 0x0804e4da in ?? ()
#43 0x080d6e2e in ?? ()
#44 0x001e in ?? ()
#45 0x080d7360 in ?? ()
#46 0x0001 in ?? ()


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



icon view crash [3.4.2] (Re: media kioslave crashes, causes konq to crash too)

2005-09-08 Thread Daniel Andor
On Thursday 08 September 2005 8:39 pm, Daniel Andor wrote:
 On Thursday 08 September 2005 7:56 pm, David Pye wrote:
  On Thursday 08 September 2005 15:44, Daniel Andor wrote:
   I set up dbus, hal, and pmount as per the thread on this list, and
   media:/ appears initially at least to work as expected.  However,
   'doing' anything to one of the devices - even hovering over one with a
   mouse - causes konqueror to crash with a segmentation fault.  Even if I
   haven't inserted a thing into any drives, just hover over one of the
   mounted harddiscs.

On further investigation, it appears to crash whenever konq is using the large 
icon view, so perhaps nothing to do with the media ioslave (as hinted by the 
backtrace).  The backtrace is exactly the same.

How do I go debugging from here?  All my packages appear to be upto date, and 
I didn't have this problem before upgrading to 3.4.2.

Thanks,
Daniel.

 Backtrace:
 [New Thread -1230718080 (LWP 6839)]
 [KCrash handler]
 #3  0xb5bc0dea in __gnu_cxx::__mt_allocstd::string,
 __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true

 ::allocate(unsigned, void const*) ()

from /usr/lib/libsoundserver_idl.so.1
 #4  0xb583a2a1 in Arts::TraderOffer_impl::TraderOffer_impl(std::string
 const, std::string const) () from /usr/lib/libmcop.so.1
 #5  0xb583aa25 in Arts::TraderHelper::addDirectory(std::string const,
 std::string const, std::mapstd::pairunsigned long long, unsigned long,
 bool, std::lessstd::pairunsigned long long, unsigned long ,
 std::allocatorstd::pairstd::pairunsigned long long, unsigned long
 const, bool  *) ()
from /usr/lib/libmcop.so.1
 #6  0xb583a96e in Arts::TraderHelper::addDirectory(std::string const,
 std::string const, std::mapstd::pairunsigned long long, unsigned long,
 bool, std::lessstd::pairunsigned long long, unsigned long ,
 std::allocatorstd::pairstd::pairunsigned long long, unsigned long
 const, bool  *) ()
from /usr/lib/libmcop.so.1
 #7  0xb583aff2 in Arts::TraderHelper::load() () from /usr/lib/libmcop.so.1
 #8  0xb583b1f0 in Arts::TraderHelper::TraderHelper() ()
from /usr/lib/libmcop.so.1
 #9  0xb583b384 in Arts::TraderHelper::the() () from /usr/lib/libmcop.so.1
 #10 0xb583b3f6 in Arts::TraderQuery_impl::query() ()
 from /usr/lib/libmcop.so.1
 #11 0xb5c0698d in KonqSoundPlayerImpl::mimeTypes() ()
from /usr/lib/kde3/konq_sound.so
 #12 0xb671da6d in KonqIconViewWidget::slotOnItem(QIconViewItem*) ()
from /usr/lib/libkonq.so.4
 #13 0xb673b95a in KonqIconViewWidget::qt_invoke(int, QUObject*) ()
from /usr/lib/libkonq.so.4
 #14 0xb73a3239 in QObject::activate_signal(QConnectionList*, QUObject*) ()
from /usr/lib/libqt-mt.so.3
 #15 0xb76ee56d in QIconView::onItem(QIconViewItem*) ()
from /usr/lib/libqt-mt.so.3
 #16 0xb75553cd in QIconView::contentsMouseMoveEvent(QMouseEvent*) ()
from /usr/lib/libqt-mt.so.3
 #17 0xb670f828 in KonqIconViewWidget::contentsMouseMoveEvent(QMouseEvent*)
 () from /usr/lib/libkonq.so.4
 #18 0xb74b502f in QScrollView::viewportMouseMoveEvent(QMouseEvent*) ()
from /usr/lib/libqt-mt.so.3
 #19 0xb74b1d5c in QScrollView::eventFilter(QObject*, QEvent*) ()
from /usr/lib/libqt-mt.so.3
 #20 0xb754ef24 in QIconView::eventFilter(QObject*, QEvent*) ()
from /usr/lib/libqt-mt.so.3
 #21 0xb73a2fea in QObject::activate_filters(QEvent*) ()
from /usr/lib/libqt-mt.so.3
 #22 0xb73a3074 in QObject::event(QEvent*) () from /usr/lib/libqt-mt.so.3
 #23 0xb73da142 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3
 #24 0xb7346b95 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/lib/libqt-mt.so.3
 #25 0xb7347938 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libqt-mt.so.3
 #26 0xb79686fc in KApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libkdecore.so.4
 #27 0xb72e3fb8 in QETWidget::translateMouseEvent(_XEvent const*) ()
from /usr/lib/libqt-mt.so.3
 #28 0xb72e2921 in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/lib/libqt-mt.so.3
 #29 0xb72f5698 in QEventLoop::processEvents(unsigned) ()
from /usr/lib/libqt-mt.so.3
 #30 0xb735c73b in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
 #31 0xb735c654 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
 #32 0xb73465cf in QApplication::exec() () from /usr/lib/libqt-mt.so.3
 #33 0xb67fd10c in kdemain () from /usr/lib/libkdeinit_konqueror.so
 #34 0xb6845550 in kdeinitmain () from /usr/lib/kde3/konqueror.so
 #35 0x0804deed in ?? ()
 #36 0x0002 in ?? ()
 #37 0x080d7ef0 in ?? ()
 #38 0xbf9e9338 in ?? ()
 #39 0x0804df11 in ?? ()
 #40 0x1000 in ?? ()
 #41 0xb7d890a4 in free () from /lib/tls/libc.so.6
 #42 0x0804e4da in ?? ()
 #43 0x080d6e2e in ?? ()
 #44 0x001e in ?? ()
 #45 0x080d7360 in ?? ()
 #46 0x0001 in ?? ()


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: icon view crash [3.4.2] (Re: media kioslave crashes, causes konq to crash too)

2005-09-08 Thread Daniel Andor
On Thursday 08 September 2005 10:20 pm, Martin Steigerwald wrote:
 Am Donnerstag 08 September 2005 22:54 schrieb Daniel Andor:
  On further investigation, it appears to crash whenever konq is using
  the large icon view, so perhaps nothing to do with the media ioslave
  (as hinted by the backtrace).  The backtrace is exactly the same.
 I am quite pleased with stability here in general.

 But well this is still day one with KDE 3.4.2 so let's see how it goes.

  How do I go debugging from here?  All my packages appear to be upto
  date, and I didn't have this problem before upgrading to 3.4.2.

 Maybe try strace konqueror to find out what Konqueror is trying to do
 when it crashes. But as strace gives lots of output it might not be easy
 to find the culprit.

The last bit of strace before it segfaults is

open(/home/da209/.mcoprc, O_RDONLY|O_LARGEFILE) = 21
read(21, GlobalComm=Arts::TmpGlobalComm\n, 8191) = 31
read(21, , 8191)  = 0
close(21)   = 0
stat64(/usr/lib/mcop, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open(/usr/lib/mcop, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 21
fstat64(21, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl64(21, F_SETFD, FD_CLOEXEC)= 0
getdents64(21, /* 56 entries */, 4096)  = 2512
stat64(/usr/lib/mcop/., {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64(/usr/lib/mcop/.., {st_mode=S_IFDIR|0755, st_size=106496, ...}) = 0
stat64(/usr/lib/mcop/kmedia2.mcoptype, {st_mode=S_IFREG|0644, 
st_size=2281, ...}) = 0
stat64(/usr/lib/mcop/Arts, {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
open(/usr/lib/mcop/Arts, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 22
fstat64(22, {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
fcntl64(22, F_SETFD, FD_CLOEXEC)= 0
getdents64(22, /* 85 entries */, 4096)  = 4056
stat64(/usr/lib/mcop/Arts/., {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
stat64(/usr/lib/mcop/Arts/.., {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64(/usr/lib/mcop/Arts/Synth_BUS_DOWNLINK.mcopclass, {st_mode=S_IFREG|
0644, st_size=94, ...}) = 0
open(/usr/lib/mcop/Arts/Synth_BUS_DOWNLINK.mcopclass, O_RDONLY|O_LARGEFILE) 
= 23
read(23, Buildable=true\nInterface=Arts::S..., 8191) = 94
--- SIGSEGV (Segmentation fault) @ 0 (0) ---


 It might also make sense to try it with a bog standard KDE configuration
 by doing mv ~/.kde ~/.kde.off. If that fixes the crash you could try
 which configuration file triggers it. Most likely its one from Konqueror
 like konquerorrc.

I think you're onto something - with a fresh .kde, it seems fine.  What config 
files relate to the above arts-ey stuff??

Thanks,
Daniel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: icon view crash [3.4.2] (Re: media kioslave crashes, causes konq to crash too)

2005-09-08 Thread Daniel Andor
On Thursday 08 September 2005 10:20 pm, Martin Steigerwald wrote:
 It might also make sense to try it with a bog standard KDE configuration
 by doing mv ~/.kde ~/.kde.off. If that fixes the crash you could try
 which configuration file triggers it. Most likely its one from Konqueror
 like konquerorrc.

A bit of experimenting showed that this:

[Settings]
EnableSoundPreviews=true

in the file .kde/share/config/konqiconviewrc

made the iconview crash.

Removing that line (but leaving the other settings unchanged) made the 
iconview work again.

Am I the only one who gets that setting to crash konq?

Thx,
Daniel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



KDE 3.3b1

2004-07-15 Thread Daniel Andor
Someone just mentioned mentioned an apt repository for KDE 3.3b1 (as 
advertised on another kde list) -- sorry I lost mail.

Trying to install it, it turns out to require new a qt, which in turn requires 
libgcc1 version 3.4.  Unstable currently carries 3.3 -- is my mirror just 
lagging, or do I need to get new gcc from elsewhere?

D




Re: KDE 3.3b1

2004-07-15 Thread Daniel Andor
On Thursday 15 July 2004 10:49 pm, Adeodato Simó wrote:
 * Daniel Andor [Thu, 15 Jul 2004 18:04:59 +0100]:
  Trying to install it, it turns out to require new a qt, which in turn
  requires libgcc1 version 3.4.  Unstable currently carries 3.3 -- is my
  mirror just lagging, or do I need to get new gcc from elsewhere?

   there is a libgcc1 3.4 in experimental. hope it serves your purpose
   (and write back telling us so! :-)

Adding the experimental source lines and doing
apt-get install gcc-3.4/experimental libgcc1/experimental
allowed me to install new version of libqt3c102-mt.  gcc-3.4 is probably not 
needed.  

Haven't tried any further yet.




KAB access error after update

2004-04-23 Thread Daniel Andor
Hi All,

I can't edit my kde addressbook after updating to 3.2.1 and 3.2.2.  Any
program (including kmail and kaddressbook) trying to access the standard
addressbook fails to modify it.  For example, kmail fails with:

kmail: ERROR: The resource '_home_da209_.kde_share_apps_kabc_std.vcf' is
locked by application ''.
kmail: ERROR: Unable to save to resource 'resource-name'. It is locked.

What does this mean, and how can I fix it??

Thanks,
Daniel.




Re: Qt3 libraries not found while compiling

2004-04-20 Thread Daniel Andor
On Monday 19 April 2004 8:38 am, Chris Cheney wrote:
 You might need to include --with-qt-dir=/usr/share/qt3 . Please look at
 the docs in kdelibs4-dev and the admin/debianrules file for more
 information about how to compile kde packages under Debian.

I know this doesn't count as RTD (Reading The Documentation), but I find that 
the following settings usually suffice in order to compile and then package 
random kde software:
export QTDIR=/usr/share/qt3
./configure --prefix=/usr --libexecdir=/usr/bin --sysconfdir=/etc \ 
--libdir=/usr/lib --includedir=/usr/include/kde \ 
--with-qt-includes=/usr/include/qt3 --mandir=/usr/share/man \ 
--infodir=/usr/share/info

Then do a make, and then in order to package and install:
sudo checkinstall -D
(the above does a make install for you.)

Usually works for me.  (But of course if I've missed out anything important 
please amend...)

HTH,
Daniel.




Re: udev HOWTO? [OFFTOPIC]

2004-03-26 Thread Daniel Andor
On Friday 26 March 2004 8:46 am, Dr.-Ing. C. Hurschler wrote:
 Yes, thats what I thought too.  If I have to edit fstab every time to find
 my USB device, then the average user will be helpless.  Maybe this is
 handled better in the easier distros...

And it looks like currently there are no userfriendly frontends. 

I just apt-got udev and writing the rules for my external drive, card reader, 
dvd drive, tv card, webcam and printer were quite simple.  However, I did 
have to overcome the snafu that there were no ptys!!  I don't quite 
understand why the package ships this way.

D




orth - 3.2.1 binary compatibility?

2004-03-07 Thread Daniel Andor
Hi all,

Can orth's cvs 3.2 packages be used with the kdelibs from 3.2.1?

I realise that 3.2.x ought to be binary compatible, but I don't know if 
anything's changed between orth's last cvs packages and 3.2.1 in unstable.  
If something was marked 3.2-pre, does that mean it's binary compatible with 
3.2.x?

Is it safe to --force-depends in order to install the 3.2.1 packages over 
orth's packages?

Quite keen on being able to keep using kmail until it gets into unstable...

Thanks,
Daniel.




Re: mplayer vs. xine

2003-07-16 Thread Daniel Andor
On Wednesday 16 July 2003 11:24 pm, Wolfgang Mader wrote:
 noatun uses the xine lib by plugins to play most of the videoformats
 (nothing new to you i think :-))
 on my system mplayer i much faster than xine. is there a reason and if so
 why is noatun not using mplayer.

For a thin wrapper around mplayer, try either
KMplayer http://www.xs4all.nl/~jjvrieze/kmplayer.html
  (also available directly from James Greenhalgh's CVS deb packages)

OR
KPlayer http://kplayer.sourceforge.net/
  (also available from Marillat's multimedia deb repository, along with 
mplayer debs)

I say _thin_ wrapper, since neither use arts.  For that, you need to wrap 
mplayer with artsdsp, and take care of latency manually.

HTH,
D




PS (Re: mplayer vs. xine)

2003-07-16 Thread Daniel Andor
On Thursday 17 July 2003 12:02 am, Daniel Andor wrote:
 KMplayer http://www.xs4all.nl/~jjvrieze/kmplayer.html
 OR
 KPlayer http://kplayer.sourceforge.net/

As a footnote: I marginally prefer KMplayer over KPlayer, since KMplayer works 
nicely for webpages with embedded video (e.g. trailers).




Re: mplayer vs. xine

2003-07-16 Thread Daniel Andor
On Thursday 17 July 2003 12:06 am, David Bishop wrote:
  I say _thin_ wrapper, since neither use arts.  For that, you need to wrap
  mplayer with artsdsp, and take care of latency manually.

 Not quite true.  Mplayer can use arts 'natively', and KMplayer,at least,
 has a gui option to turn that option on.  Alternatively, you can change
 your mplayer config file, and it will work no matter what front-end you
 use.

Yes, sorry, that's correct.

 This all assumes that you are using an mplayer with arts support built-in.

I was blindly under the assumption that one would be using mplayer debs from 
Marillat, which do not have arts support compiled in. (He has a note (as of 
04/04/2003) about it on his webpage http://marillat.free.fr )

So if you compile mplayer yourself, or use another deb repository, then you 
can be good with arts.

D




Re: Tried KDE 3.1 in SID

2003-03-11 Thread Daniel Andor
On Mon, 10 Mar 2003, Karolina Lindqvist wrote:
 In a kind of fit of PMS I erased and purged my own KDE version and installed
 the version in SID yesterday.

 But I removed it and reinstalled my own version today, since the SID version
 just gave me too many problems. It was also noticable slower in addition to
 the problems.

I've been using the kl packages leading upto and beyond the release of
KDE3.1.  It's been great, thanks!  But what is the current policy with
regard to which version I should use?  What's the difference?  Do they
both use the same source packages?  Both kl and sid versions of kde seem
to be kept upto date, as far as I can tell.  What about future release
candidates and minor upgrades?

Sorry for the many questions: the kde debian page doesn't seem to have an
exposition on these questions.

Thanks,
Daniel.




Re: KDE and java

2003-03-09 Thread Daniel Andor
On Sunday 09 March 2003 4:39 pm, Matteo Vescovi wrote:
 Hi all,
 I've got KDE 3.1 installed on Debian woody. I'm used to go to an URL with
 java scripts and stuff like that, but konqueror refuses to enter the site.
 After some tests, I discovered that the problem is the java good-looking
 things that the site requires to load at the beginning. Now, the question
 is: what should I do?? Which kind of java should I install?

If you want to get java (applets) working with konqueror, check out the 
kde-java HOWTO:
http://www.konqueror.org/konq-java.html

Basically, a fairly recent version of jre should work.  I'm using the IBM 
Java2 1.4 jre and it works great.
This link may work: http://www-106.ibm.com/developerworks/java/jdk/linux140/

HTH,
Daniel




kded accessing HD every 500ms?

2002-11-29 Thread Daniel Andor
Hi,

Since I upgraded from rc2 - rc3 KDED now makes the hard disc's head move 
every 500ms when it polls the filesystem.  Before the upgrade, the polling 
was set to the same frequency, but there were no disc accesses -- presumably 
most polls are cached.

Since I have a laptop, this completely kills any possibility of disc spinnig 
down, and is quite annoying to listen to.

Any ideas what may actually be going on?

Thanks,
Daniel.