Re: Kopete fixes forthcoming?
On Monday 12 July 2004 09:51, Robert Lindgren wrote: > Sorry to fast on the trigger, > > http://kopete.kde.org/ > > 0.8.4 is out with fixes for icq and yahoo Just my 2 cents Kopete broke with ICQ since about Thursday, but it's OK again this morning without me having upgraded /touched anything. If the ICQ part is the only section you're interested in, then try again before delving into an upgrade rigmorol :) Cheers, Gavin.
Re: download.kde.org packages
On Thursday 08 July 2004 10:55, Kevin Krammer wrote: > I think they are still there and even updated, but for some reason not > apt-get'able (I think some package index files is missing) http://ftp.plig.net/pub/kde/stable/latest/Debian/ I'm still waiting, since I want the libqt3 for woody and I'm too lazy to compile it myself :) gdh
Konqueror crashing regularly
Hi :) We run a call centre with 20-30 KDE diskless workstations. The machines are mainly used with a web-based hotel-booking application which we have developed, and are finding a relatively high level of instability with Konqueror. In short, Konq will sometimes segfault after submitting a POST form at the point where the remote server is starting to send the next HTML through. This problem has stayed with us for a few months and I thought it had gone away with a previous KDE release, but I've been told that the problem is still there. Given that I would like to trace the problem rather than just moving everyone to Firefox, etc. - how can I (easily?) build a set of Debian packages for sid that will contain debug information so I can submit a useful backtrace to the developers? As I said, the machines are diskless, and have 256MB RAM and no swap space - all they run is Konq and an Evolution instance - nothing really heavy like OpenOffice, etc. so I can't really see the problem being lack of RAM, but I would dearly like to get to the bottom of this, and fix it not only for us, but possibly for many others who just put it down to 'some bug'. Cheers, Gavin.
Re: How to get rid of KVim
On Friday 25 June 2004 15:32, Silvan wrote: > ->apt-get remove kvim > Reading Package Lists... Done > Building Dependency Tree... Done > The following packages will be REMOVED: > kde kdeaddons kvim vimpart > 0 upgraded, 0 newly installed, 4 to remove and 1 not upgraded. > Need to get 0B of archives. > ... This is a complete misnomer... Removing 'kvim' will NOT remove the entirety of the K Desktop Environment. It will remove the 10k Debian 'metapackage' called 'kde' as well as the one called 'kdeaddons'. It does this because kvim is part of the kdeaddons metapackage, and kdeaddons is part of the kde metapackage. Rest assured your KDE installation is safe. Cheers, Gavin.
Re: background: world time zones
On Monday 17 May 2004 14:58, Uwe Brauer wrote: > Thanks for you help, it is really odd, now kcontrol tells me that I am > in kde.3.2.2 (during installation of kworldclock several upgrades were > performed, however this kde version is not part neither woody, sarge > nor sid). KDE 3.2.2 has been in sid for a couple of weeks now - and I now suspect you have a mix of packages from 3.2.2 and a previous version which may explain strange problems you're having - could you try a full dist-upgrade to bring everything on your system to a concurrent level? > In any case under Did you mean to leave this sentence half-finished? I do that a lot! :) > no it is not there, the option to use a appear only the option > bleeding. > Strange Uwe, I think the language barrier has come between us - I simply don't understand what you're trying to say :( Could you perhaps post a screenshot of what your 'Advanced Options' window looks like (use the 'ksnapshot' package to do this) Mine looks like http://bum.net/snapshot1.jpg Cheers, Gavin.
Re: background: world time zones
On Monday 17 May 2004 14:29, Uwe Brauer wrote: > Well, I found kworldclock, which seems pretty much what you are > describing, however I fail to configure it as a background, since I > don't find the corresponding walletpaper. As above.. kcontrol -> Appearance and Themes -> Background .. now look on the right just underneath the picture of the monitor, there's "Advanced Options", now select "use the following program for drawing the background" and you should then be able to select "kdeworld" from the list. Cheers, Gavin.
Re: background: world time zones
On Monday 17 May 2004 10:53, Uwe Brauer wrote: > > kcontrol -> Appearance and Themes -> Background -> Advanced -> [x] > > Use the following program... -> kdeworld > > Thanks, but seems not to be in kde 3.1.5, I might upgrade then The Debian package you need is called 'kworldwatch' - I'm sure it was part of KDE 3.1.5, but you simply may need to install this package :) Cheers, Gavin.
Re: Could not contact DCOP ?
On Wednesday 21 April 2004 10:58, Pascal Mainini wrote: > in my case, the following directories in /tmp get accessrights of 600 > instead of 700 and can't get accessed anymore: Many thanks, Pascal - I'll watch for that next time it happens! :) > so, basically i just set up a cronjob which resets the permissions every > now and then. Yep, my mind was already running down that track. > but if i'm not the only one with that problem, we should maybe file a bug > about? or do some of the kde-people in here know, where the problems are > coming from? The reflex reaction is certainly to file a bugreport, but if neither of us can reproduce a random behaviour, then how will the KDE devels? :( Anyway, I'll keep an eye on that. Thanks again, I wasn't expecting a reply let alone a possible fix :) Cheers, Gavin.
Could not contact DCOP ?
Hullo. I've been running KDE on about 25 identical diskless machines using PXE network booting / NFS root / NIS login / NFS homedirs quite successfully for a couple of months now, but there's one problem that I can't solve. Every now and again, for no discernable reason, the machine will refuse to run any more applications, and instead choose to display a dialog box saying " could not contact DCOP" - from that point, the user must log off, and log in again, at which point all is rosy. The actual text of the message may be different (it's been a day or two since I was at the call centre) but I expect the meaning comes across. I'm experienced at maintaining Linux in a server environment, but am less so with desktops - I've been using KDE on my own desktop for the last 18 months, but haven't experienced this problem (that said, I use a hard disk, and no NFS / initrd boot trickery) the machines were originally using a CVS snapshot of KDE 3.2.1 from Debian experimental, and are now running 3.2.1. The instances of this problem has dropped as a result of the upgrade, and I'll be testing the 3.2.2 packages this week hopefully. Of course it's near impossible to provide a solution based on the scant information I have provided, but could someone provide a few pointers for me to check when this next happens? e.g. what processes should be running? should anythng appear in the logs? any commandlines for me to try to talk to the 'dcopserver' directly to aid in the problem diagnosis? Aside from this periodic annoyance, the call centre admins have been very pleased with KDE and have been greatly enjoying life without viruses, trojans, spyware and malware - a big thank-you from all of us! Cheers, Gavin.
Re: 3.2.1 and krfb
On Sat, Apr 03, 2004 at 02:31:51AM +0200, Christoph Kaminski wrote: > I there any fix for it yet? Yes. Use the proper resources to find out more. http://bugs.debian.org/krfb Cheers, Gavin.
krfb on 3.2.1 malfunction?
Hullo :) I've just installed a fresh unstable suite on my notebook (kdebase then single packages as-needed to keep the clutter down), and all is working well up to a point :) This machine has been Win2000-based running TightVNC so we can control it remotely, and the docs seem to suggest that krfb is capable of the same functionality - i.e. always listen for a connection, and provide access to the X11 desktop via only a password (Uninvited Connections). Unfortunately, when I connect to port 5900 from another PC, I do not see the familiar "RFB 003.003", but instead I either connect and then get no data, or connect and get immediately disconnected again. Whilst this is happening, the desktop chugs a bit, and KDE System Tray makes room for a blank icon, but I do not see any actual icon displayed. I can't find anything in syslog, or the ~/.xsession-errors file - where can I find more information on this problem? :) Cheers, Gavin.
