- openSUSE KDE

Updating kde3
by Anders Johansson 11 May '02

11 May '02

Hi, I'm trying to update from the supplementary packages for 8.0, specifically I'm trying to update kdevelop3. This rpm requires docbkdsl, docbkxsl and docbk30. I can't find these, or indeed any rpms with "docbk" in their names. Does anyone know what rpms satisfy these dependencies? Also, libogg and libvorbis are rc2 in the supplementaries but rc3 on the 8.0 cds. Any clue as to why? //Anders

1 1

Re: [suse-kde] Konqueror user agent
by dh 11 May '02

11 May '02

On Saturday 11 May 2002 08:27 am, Paul W. Abrahams wrote: > On Saturday 11 May 2002 01:08 am, you wrote: > > On Friday 10 May 2002 01:58 pm, Paul W. Abrahams wrote: > > > On Friday 10 May 2002 04:33 pm, I wrote: > > > > I haven't actually done it yet, but I think I now know the > > > > answer of how to [install "Change User Agent" in KDE 2.2.2, > > > > thanks to Pam and Liz's posts. > > ... > > > Glad you got it figured out. I never would have guessed that the > > parts were packaged seperately. > > I hope none of my responses sounded derogatory -- I certainly didn't > intend them that way. Not at all, I'm just glad you found a solution. -- dh I've been awake: 2 hours 02 minutes Suse Linux 7.2 professional kernel 2.4.17, xFree86 4.2.0, kde 2.2.2

1 0

Autostart prog->desktop #x
by del 11 May '02

11 May '02

Hi Folks, Is there a way to set the programs in the Autostart folder to open in a specified desktop, Suse 8.0? E.G. KMail to desktop 2 and KNode to desktop 3. Thanks, -- del 8-) http://www.diverdel.org.uk

5 10

Icon positions jumbled in KDE3
by Glenn Holmer 11 May '02

11 May '02

Maybe similar to my previous post, as normal user, desktop icons are frequently moved to random positions on login (in the same general area, but scrambled). And does anybody know how to specify the length of an icon text before it wraps? or disable/enable icon text wrapping? -- =========================================================== Glenn Holmer (gholmer(a)ameritech.net) ----------------------------------------------------------- Performing music well is a matter of distorting the score to produce the desired illusion, namely the existence of the score in a pure state. ----------------------------------------------------------- -Shadow, 1975 ===========================================================

1 1

Konqueror user agent
by Paul W. Abrahams 11 May '02

11 May '02

In version 2.2.2 of Konqueror at least, there's a facility for specifying a "user agent" in the configuration that enables Konqueror to identify itself as some other prowser (IE 5.5 is usually a good choice). It's necessary for accessing web sites that check for browser identity. Trouble is, it seems that it's necessary to specify the user agent individually for each website where it matters. There's no way I can find to say that Konqueror should by default identify itself as, say, IE5.5. Is there some way of doing that that I've missed? Is the behavior in version 3 any better? Paul Abrahams

9 20

Re: [SLE] Speaking of time?
by Christopher Mahmood 11 May '02

11 May '02

Patrick, Did you notice that the trailer on each message on suse-kde says not to crosspost? * Patrick (tracerb(a)sprintmail.com) [020509 17:03]: > Anthony brought up the subject of time/date being wrong on his mails, > but my problem is somewhat different. This seems to be a problem that > goes back to the 7.1 days! Each time I boot up, the system clock has > the wrong time and requires resetting. The bios clock is correct as I > have checked that already. This sounds vaguely familiar... > Going back to a previous mail when the problem showed up back in October > 2001, it seems to be a bug in the /etc/rc.d/boot script which will > cause the system clock to NOT be set to the hardware clock on boot. > The bug has been around for quite some time it seems. The problem was > simple in that adding the full path to the hwclock command solved the > problem. The solution was to change the CLOCKCMD=hwclock in > /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also > adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file! Ah ha! I don't know where you guys are digging this stuff up at but here's my response the last time someone posted this: http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html -- -ckm

5 7

KMail Date/Time Stamp Incorrect
by Anthony W. Marino 10 May '02

10 May '02

My messages are ALL coming in with yesterday's date, however, outgoing and self created messages to lists are showing up with the proper date/time. Any thoughts are appreciated! Thanks, Anthony

1 0

kdelibs Optimizations
by Anthony W. Marino 09 May '02

09 May '02

With the latest KDE3.0x rpms from SuSE, are kdelibs compiled with optimizations? This was a question that was asked of me from Marc Mutz (kde.org) in reply to a performance issue that I have. Thanks, Anthony

2 2

How to get faster startups?
by Matt Sheffield 09 May '02

09 May '02

Is it just me or does it seem that KDE (2.2 and 3.0) takes longer to start up the first time a user is logging in. On Red Hat, the first login takes just as long as subsequent logins. How is this accomplished? I can't stand waiting 45 seconds for KDE to start. I've tried editing my /opt/kde3/bin/startkde to comment out some of the uneeded features but it doesn't seem to speed things up. Has anyone else had this problem, too?

1 0

Speaking of time?
by Patrick 09 May '02

09 May '02

Hi all, Anthony brought up the subject of time/date being wrong on his mails, but my problem is somewhat different. This seems to be a problem that goes back to the 7.1 days! Each time I boot up, the system clock has the wrong time and requires resetting. The bios clock is correct as I have checked that already. Going back to a previous mail when the problem showed up back in October 2001, it seems to be a bug in the /etc/rc.d/boot script which will cause the system clock to NOT be set to the hardware clock on boot. The bug has been around for quite some time it seems. The problem was simple in that adding the full path to the hwclock command solved the problem. The solution was to change the CLOCKCMD=hwclock in /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file! First of all, I don't have the CLOCKCMD in my boot script any longer in Suse 8. Is that now located somewhere else or not needed? Is there some where else one should look to get the system clock to set to the hardware clock? Would adding just the command to the boot.local script fix the problem? Thanks for all help or suggestions. Patrick -- --- KMail v1.4 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb

1 0