Opera crashes with KDE3.1rc2

2002-11-29 Thread Michael Thaler
Hello,

I use KDE3.1rc2 + QT3.1 from the release candidate. Recently I
installed Opera 6.0 for Linux. I tired the deb packages and the *.tar.gz
archives. Both the static and the dynamically linked versions crash on
startup.

Opera loads fine, I think it adopts the KDE theme (Keramik), but when
it tries to open a webpage, it segfaults. Is this a known bug? Is
there any solution?

Greetings,
Michael




Re: Opera crashes with KDE3.1rc2

2002-11-29 Thread Karolina Lindqvist
fredagen den 29 november 2002 08.06 skrev Michael Thaler:
 Hello,

 I use KDE3.1rc2 + QT3.1 from the release candidate. Recently I
 installed Opera 6.0 for Linux. I tired the deb packages and the *.tar.gz
 archives. Both the static and the dynamically linked versions crash on
 startup.

 Opera loads fine, I think it adopts the KDE theme (Keramik), but when
 it tries to open a webpage, it segfaults. Is this a known bug? Is
 there any solution?

I tried dynamic linked opera, KDE 3.1.0 + QT3.1.0, and it appears to work. 

-- Karolina




RE: I cannot load kde 2.2.2

2002-11-29 Thread Ravi Joganathan
The debconf generated XF86Config-4 file may have an option in section Device 
enabling use of frame buffers, disable that option.  


Section Device
Identifier  nVidia TnT2
Driver  nv
BusID   PCI:01:00:00
#   Option  UseFBDev  true
EndSection


Ravi

-Original Message-
From: Rodrigo Agerri [mailto:[EMAIL PROTECTED]
Sent: 28 November 2002 18:11
To: debian-kde@lists.debian.org
Subject: I cannot load kde 2.2.2



Hi everybody

I've got an ATI Rage 128PF video card. I am running woody with kernel version
2.4.18bf24. According to the manuals, it seems that I should use the r128
driver for my xfree86 configuration. However, the xserver it does not work.
When I try to use a desktop environment, it gives me the error  no screens
found.

I tried also with ati and it did not work either. Then I choose vesa and
it worked ok, butonly gnome. I cannot load kde which is very funny.

The problem is that it does not return any error; it starts to load it and
suddenly freezes.

I've checked the whole xserver-xfree86 configuration again and I cannot work
out why I am able to use gnome (and fluxbox as well) but  I cannot load kde.

any ideas are more than welcome

Rodrigo


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




How to get Anti-aliasing to work

2002-11-29 Thread Manegold
Hallo list,
I use debian woody with KDE 3.04 and I can't get anti-aliasinig to work. The 
checkbox has no effect. When I preview a font (TT or Type1) with the Font 
installer in KControl-Center, the font is displayed with anti-aliasing, but 
not in any apps. What am I missing here?

TIA
Thorsten




Re: Relation of debs and KDE CVS?

2002-11-29 Thread Paolo Ulivi
On Thu, Nov 28, 2002 at 10:29:34AM +1100, Daniel Stone wrote:

 On Wed, Nov 27, 2002 at 11:17:09PM +1100, Ben Burton scrawled:
   It should be possible to build debian packages straight out of CVS. You 
   may 
   have issues with some modules, but as we are currently in a feature 
   freeze, 
   there should be no problems with files being moved around, breaking the 
   builds. 
  
  Well.. that's what I'd thought too. :)
  
  Peter Hawkins just pointed out to me a build failure in kdeaddons
  resulting from one of the noatun plugins being pulled out of the release
  several days ago.
 
 I'm infrequently scp'ing Peter's debs across from his build machine
 (which is about 10m from where I am now), and they work fine. :)

Is him the same Peter Hawkins who created the GNU/Linux port of the
game Descent II, namely D2X,  which was later debianized by Bradley
Bell and rpmmed (yup) by me ?

Ciao,
Paolo

-- 
If Linux is not Unix then Windows are not Gates
 Anonymous, XXI Century




Re: Build times?

2002-11-29 Thread Frank Van Damme
On Friday 29 November 2002 02:12, Michael Schuerig wrote:
 As I wrote earlier, I consider building my own KDE packages (possibly
 from CVS) with debugging enabled. I just tried this on qt-copy and this
 is what time said of the effort:

 real487m1.732s
 user401m35.620s
 sys 12m42.350s

 (450 MHz Celeron 2, 640MB RAM, Kernel 2.4.19, gcc 2.9.5)
   ^
2.95?

 This is a bit long... I'm wondering, what are the times on current,
 faster machines (2 GHz and up)?

I don't know, QT took about 4 hours here; 

- athlon classic 800 MHz 
- epox 7kxa board, via kx133 chipset 
- 384 meg sdram
- gcc 3.2 (IMPORTANT!!! takes more time to compile...)

Frank




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.




kmail: delete multiple mails

2002-11-29 Thread Michael Schmitz
Hi,

I would like to clean up my mail folder.
Especially: deleting all mails in the 'deleted' folder with a specific 
recipient address.

Kmail allows to search for recipients, but not to order by it (therefore I can 
not select and delete them at once)

Thanks in advance for your support
Michael




Re: Build times?

2002-11-29 Thread Michael Schuerig
On Friday 29 November 2002 11:25, Frank Van Damme wrote:
 On Friday 29 November 2002 02:12, Michael Schuerig wrote:
  As I wrote earlier, I consider building my own KDE packages
  (possibly from CVS) with debugging enabled. I just tried this on
  qt-copy and this is what time said of the effort:
 
  real487m1.732s
  user401m35.620s
  sys 12m42.350s
 
  (450 MHz Celeron 2, 640MB RAM, Kernel 2.4.19, gcc 2.9.5)

^
 2.95?

Yes.

  This is a bit long... I'm wondering, what are the times on current,
  faster machines (2 GHz and up)?

 I don't know, QT took about 4 hours here;

 - athlon classic 800 MHz
 - epox 7kxa board, via kx133 chipset
 - 384 meg sdram
 - gcc 3.2 (IMPORTANT!!! takes more time to compile...)

Did you build with -debug enabled, i.e., added to the configure options? 
Also, I didn't do a plain make, but rather debuild -us -uc binary I 
expect the later to take longer considerably longer as it creates 
packages for everything.

Michael

-- 
Michael Schuerig  If at first you don't succeed...
mailto:[EMAIL PROTECTED]   try, try again.
http://www.schuerig.de/michael/   --Jerome Morrow, Gattaca




Re: How to get Anti-aliasing to work

2002-11-29 Thread Albert Teixidó
Hi,

What version of QT does work well with debian and kde 3.0.5? Any URL about
recompile QT to get anti-aliasing?
Thanks,

Albert

Regnat Nikolaus dijo:
 On Friday 29 November 2002 10:44, Manegold wrote:
 Hallo list,
 I use debian woody with KDE 3.04 and I can't get anti-aliasinig to
 work. The checkbox has no effect. When I preview a font (TT or Type1)
 with the Font installer in KControl-Center, the font is displayed with
 anti-aliasing, but not in any apps. What am I missing here?

 TIA
 Thorsten

 Hello Thorsten,

 QT is compiled without xft support. You have to recompile QT and enable
 xft  support to get anti-aliasing to work.

 Nik


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


-- 
Albert Teixidó
Pub PGP key 0x0E16E76 Albert Teixidó [EMAIL PROTECTED]
at pgp.rediris.es





Re: How to get Anti-aliasing to work

2002-11-29 Thread Regnat Nikolaus
Hi,

I suggest you do the following:

apt-get source qt-x11-free 
(This downloads and uncompresses qt 3.0.5 which is recommended for KDE 3.0.5, 
You need to have e.g. the following line in your /etc/apt/sources.list
deb src ftp://ftp.kde.org/pub/kde/stable/3.0.5/Debian/woody ./ )

Then edit the file /debian/rules in your extracted qt-x11-free-3.0.5 directory

Search for the text -no-xft and replace it with -xft 

Do a dch -i if you want to increase the Debian version number (to distinguish 
the packages from the original ones), this is optional. dch is included in 
the package devscripts.

run dpkg-buildpackage to create the debs and install them (dpkg-buildpackage 
is included in the package dpkg-dev).

Note that it is not recommended to run XFree86 4.1.0 with xft (therefore it  
was disabled). Read the RELEASE-NOTES.woody in on your kde mirror e.g.
http://ftp.du.se/pub/mirrors/kde/stable/3.0.5/Debian/woody/RELEASE-NOTES.woody 
 

Nik

 Hi,

 What version of QT does work well with debian and kde 3.0.5? Any URL about
 recompile QT to get anti-aliasing?
 Thanks,

 Albert

 Regnat Nikolaus dijo:
  On Friday 29 November 2002 10:44, Manegold wrote:
  Hallo list,
  I use debian woody with KDE 3.04 and I can't get anti-aliasinig to
  work. The checkbox has no effect. When I preview a font (TT or Type1)
  with the Font installer in KControl-Center, the font is displayed with
  anti-aliasing, but not in any apps. What am I missing here?
 
  TIA
  Thorsten
 
  Hello Thorsten,
 
  QT is compiled without xft support. You have to recompile QT and enable
  xft  support to get anti-aliasing to work.
 
  Nik
 
 
  --
  To UNSUBSCRIBE, email to [EMAIL PROTECTED]
  with a subject of unsubscribe. Trouble? Contact
  [EMAIL PROTECTED]




Re: kmail: delete multiple mails

2002-11-29 Thread Hendrik Sattler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Freitag, 29. November 2002 11:43 schrieb Michael Schmitz:
 I would like to clean up my mail folder.
 Especially: deleting all mails in the 'deleted' folder with a specific
 recipient address.

 Kmail allows to search for recipients, but not to order by it (therefore I
 can not select and delete them at once)

Yes it does. Find a recipient, mark the line, click on the recipient field tab 
at the top, then mark the most top one of the mails to delete and use 
Shift-Click and Ctrl-Click to mark all the other mails and delete them.
Pretty good working like in any other of such programs...
You should disable threaded view first, though.

HS

- -- 
Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
oder über pgp.net

PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9512Qzvr6q9zCwcERAtBrAJ9GllbQSV3TGf4ZhjvHBToO56sDbgCghrxB
TdEPD4mLcFmXfSafUktDDoY=
=6JJe
-END PGP SIGNATURE-




Re: kmail: delete multiple mails

2002-11-29 Thread Michael Schmitz
On Friday 29 November 2002 13:29, Hendrik Sattler wrote:
 Am Freitag, 29. November 2002 11:43 schrieb Michael Schmitz:
  I would like to clean up my mail folder.
  Especially: deleting all mails in the 'deleted' folder with a specific
  recipient address.
 
  Kmail allows to search for recipients, but not to order by it (therefore
  I can not select and delete them at once)

 Yes it does. Find a recipient, mark the line, click on the recipient field
 tab at the top, then mark the most top one of the mails to delete and use
 Shift-Click and Ctrl-Click to mark all the other mails and delete them.
 Pretty good working like in any other of such programs...
 You should disable threaded view first, though.

The problem is, that in the 'trash' folder there is no 'recipient' column. 
Just a 'receiver'.

Regards,
Michael




Re: Build times?

2002-11-29 Thread Frank Van Damme
On Friday 29 November 2002 11:50, Michael Schuerig wrote:
 Did you build with -debug enabled, i.e., added to the configure options?
 Also, I didn't do a plain make, but rather debuild -us -uc binary I
 expect the later to take longer considerably longer as it creates
 packages for everything.

I used the recommended options - it's in some readme file  also on 
trolltechs website I think.

Nothing fancy :)

Now I only wished all my stuff would link correctly... 

Frank




Re: new shakti.ath.cx mirror structure

2002-11-29 Thread Paolo Ulivi
On Mon, Nov 25, 2002 at 06:04:37PM +0100, Karolina Lindqvist wrote:

 There is no fixed RC4 release in the CVS, since it is not separately tagged. 
 At least as far as I can see. Instead it is continuously updated, and it is 
 thus more of a CVS snapshot than a release candidate. The question with that 
 is always when to make the snapshot? The separately packed RC4 snapshot is 
 read protected, for some reason.

On Fri, Nov 29, 2002 at 01:06:27AM -0700, James Richard Tyrer wrote:

 Dirk Mueller wrote:
 Hi, 
 
 CVS HEAD is open for commits again for KDE 3.2 release. 
 
 I must say that I am not happy to hear this.
 
 I still am unable to compile three packages in KDE_3_1_0_RELEASE.
 
 irony So, we won't really concern ourselves with the bugs in the 
 current release which won't even compile, we will just rush on with new 
 features. /irony
 
 I would like to suggest that I feel that this model of the development 
 tree is WRONG -- that it contributes to buggy code.  Yes I know that 
 many projects do it that way -- and many projects produce buggy code.
 
 First I would like to suggest that we take a pause here.  Release 3.1.0 
 has a certain significance when compared to the competition: Windows. 
 It was after that release that Windows went into feature bloat and 
 change for the sake of change and never mind fixing the bugs.  It 
 finally reached the point before the release (or escape) of Windows 2000 
 that the code was such a mess that nobody understood how it was supposed 
 to work and a programmer with a phD in CS was assigned to try to fix it. 
  He and a team of professional programmers were unable to do the job.
 
 My point is that we should be very careful not to in any way repeat the 
 mistakes of MicroSoft Windows.
 
 As I understand the current model, the release is branched off and 
 becomes the less important while HEAD continues immediately with new 
 development and becomes the more important. I see this as the first 
 problem.  The current release should be the more important and work on a 
 future release should be the less important.
 
 One model I have seen is simply not to branch the current release for a 
 certain period of time with new features being worked on separately to 
 be  integrated into the current HEAD at the end of this post release 
 development pause.  What I see as the most advantageous part of this is 
 the bugs do NOT need to be fixed twice -- that the new features are 
 added to the release after a period of bug fixing.
 
 I would like to see this method made somewhat permanent.  That the 
 current release remains HEAD until it is decided that the final minor 
 release has been made and only then is it branched off.  Until that time 
 all new features would be in a temporary branch and would have to be 
 based on the new release.
 
 And, yes I know that this would make it more difficult to add new 
 features, but would also make it easier to fix the bugs.  And, would 
 also require that the bugs be fixed in the current release.
 
 Whether it is with commercial software or open source software, users do 
 not like to hear that the bug has been fixed (or will be fixed) in the 
 next major release.  They should not hear that.  Major releases are for 
 new features NOT for bug fixes.
 
 So, that is my manifesto.  I would appreciate it if I received no 
 arrogant and flippant comments about this.  They do not in any way 
 promote a useful discussion.
 
 I also wanted to make a note here so that everyone that reads this will 
 know:  I am a professional programmer retired on disability.  I studied 
 Electrical Engineering  Computer Science in college.  There is much 
 that I do not know about the KDE project.  But I know a lot more about 
 computer programing than some of the self taught hackers that have been 
 telling me that I don't know anything (yes that is an arogrant remark). 
  I don't appreciate it and you only make fools of yourself doing it.
 
 --
 JRT
 
I reported this msg from kde-devel just to underline that, IMMO,
your doubts about KDE's development model are not echoes in the
desert.

Ciao,
Paolo

-- 
If Linux is not Unix then Windows are not Gates
 Anonymous, XXI Century




arts Curiosity

2002-11-29 Thread Robert Tilley
After KDE 3.1beta2 opens, I must perform an 'artsd ' to start the arts 
daemon.  Into which file should I insert this command so that the arts server 
is run at startup?
-- 
Comments are most appreciated,

Bob




Re: kded accessing HD every 500ms?

2002-11-29 Thread Oleg
 Am Freitag, 29. November 2002 11:42 schrieb Daniel Andor:
  Since I upgraded from rc2 - rc3 KDED now makes the hard disc's head move
  every 500ms when it polls the filesystem.  

BTW, how can you tell which process accesses the HD and how often? strace ? I 
wonder if there is a top-like utility, but for HD access instead of CPU 
usage.

Thanks
Oleg





Compiling KDE 3.1 on Woody

2002-11-29 Thread Sean Fraley
I am running an install of Woody, and I would like to have KDE 3.1 on my 
system.  I --do not-- want to track testing/unstable to do this.  The problem 
is that the /debian directory of the current snapshots is rather specifically 
geared towards testing/unstable, making it a pain to create debs for Woody 
from them, and I am not yet skilled enough with the dev tool to configure a 
Woody compatible set of debs myself, at least not for something as large and 
complicated as QT/KDE.  Therefore, I would like to compile it myself, but I 
would like to accomplish the following when I do.

1)  Install all of the files into the same directories that they would be into 
if installed from .deb files.  What options need to be passed to the 
configure script to accomplish this?  Do I need to manually move any of the 
files after running make install?  Are there any symlinks I need to make?  
Doing this would allow my compile to be overwritten by a later install of 
QT/KDE 3.1 packages without leaving cruft in obscure directories.

2)  Is there a convenient way to find any library and other build depends for 
QT or KDE, so I can get the appropriate software installed before finding out 
one and a half hours into a build that something was missing.

3)  Is there a policy manual for KDE and other desktops available? where?

Thank You




Re: Build times?

2002-11-29 Thread Bjoern Krombholz
On Fri, Nov 29, 2002 at 10:53:42PM +0100, Oswald Buddenhagen wrote:
 On Fri, Nov 29, 2002 at 05:12:49PM +0100, Bjoern Krombholz wrote:

 i'm not impressed ... the debian build does everything four times, so
 you're not even 2.5 times as fast. :-P

Hmm? I'm not shure i got it right - 4 times? Why?

  Compiling C++ stuff takes much longer than plain C because of the
  preprocessing
 cpp does not not need much time,

Never said anything else. ;)

 a) g++ is slower than gcc

Aren't those both the same, more or less?
(`g++' equals `gcc -lstdc++ -lm')


Bjoern