Hi all,
has anyone else noticed that sometimes (about 50% of the time), when you click
on the install/remove software module in yast it doesn't start the first time
you click it, it doesn't start the second time you click it...you have to
click it three times before it starts.
I thought I was imagining it at first, but it seems to be a real problem...
Can anyone back me up on this one?
daveor
HI all,
I upgraded my SuSE 9.1 box to KDE 3.3 via yast by adding
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.1/yast-sour…
to my list of installation sources and updating all KDE packages. I have one
problem now...openoffice won't start. I get the following:
daveor@jimbo:~> OOo-writer
Starting /opt/OpenOffice.org/program/swriter...
soffice.bin: kdecore/kcmdlineargs.cpp:159: static void KCmdLineArgs::init(int,
char**, const KAboutData*, bool): Assertion `argsList == 0' failed.
Aborted
daveor@jimbo:~>
anyone seen this or know what it's about?
thanks for the help!
daveor
Does anyone know if/when suse will release KDE 3.3 over yast2 online update?
--
Peace,
Jake Sallee spark(a)breathedeeply.com
Hate viruses? Hate Microsoft? Try Linux!
SuSE Linux 9.1 Professional www.suse.com
Hallo,
funktioniert bei jemandem mit KDE 3.3 noch der Servertest ?
Ooo funktioniert seit heute wieder ;) Updates sind gerade gekommen.
--
MfG / Regards
Günther J. Niederwimmer
Hi all,
I have a quick question but I'm not really sure who to ask....I'm developing
an application with support for maildir and I was testing it out on my kmail
mail folder. Apparently there are some assumptions in the maildir support I
was using (javamaildir), specifically:
- Folders are called ".FolderName"
whereas in my kmail folders:
- Folders are called "FolderName" and subfolders are in a separate directory
called ".FolderName.directories".
So, what I'm wondering is whether
a) the javamaildir needs work (which I'm prepared to do),
b) kmail uses some non-standard strain of maildir or
c) there's lots of wiggle room in the maildir specification
If I've mailed to the wrong place can someone let me know where to take my
question...
thanks in advance,
daveor
Hi all,
It's the first time I write to the list, but I carefully read it.
I performed a kde-3.3 install on SuSE 9.1 without any problem.
Everything works for me
except 2 things.
- OO won't start as previously reported, I didn't modify
/usr/X11R6/bin/OOo-template, but I launch the
app with the command : /opt/OpenOffice.org/program/soffice
and I get the same result.
- I reported a few releases earlier that the clockpanel applet is broken
: it is no longer impossible to set the
background color in a digital (non LCD) clock. I sent the following
patch which has to be applied to kdebase3 :
-------------------------------------------------------------------------------------------------------------------
diff -ru org/kicker/applets/clock/clock.cpp
mod/kicker/applets/clock/clock.cpp
--- org/kicker/applets/clock/clock.cpp 2004-07-17 19:52:06.000000000
+0200
+++ mod/kicker/applets/clock/clock.cpp 2004-08-29 19:57:26.293488408
+0200
@@ -1026,7 +1026,7 @@
// let's propagate the background brush too
if ((!_clock->widget()->paletteBackgroundPixmap() &&
_clock->widget()->paletteBackgroundColor() ==
paletteBackgroundColor())
- || paletteBackgroundPixmap())
+ || _clock->widget()->paletteBackgroundPixmap())
{
_clock->widget()->setBackgroundOrigin(AncestorOrigin);
const QPixmap* brush = paletteBackgroundPixmap();
------------------------------------------------------------------------------------------------------------------
which works very well, but it is not taken into account !
Take it if you are interested in.
Michel.
Colin Pinkney wrote:
> I've got SuSE 9.0 Pro and I just upgraded to the latest KDE 3.3 packages from
> the SuSE supplementary feed using YAST. I've done this loads before and
> everything has been fine.
>
> Now however, konqueror has started to abort (SIGABRT) when I start it up with
> the web profile. With the file browsing profile it is fine and the preloaded
> instance also starts ok
Here are another rpms, but with working krpmview plugin :
ftp://81.10.195.96/rpms/
I hope they don´t work only for me.
Andrä
Hi,
I've found that KDE 3.3's attempt to carry forward saved window settings
from an earlier KDE is inadequate in many cases.
I was in the habit of using the old Save Window Settings (form the window
manager menu's Advanced sub-menu--I don't know if I have the name exactly
right, and of course, I cannot check on what it was, having upgraded to
KDE 3.3). Thus I had quite a few of these settings. Fortunately, in the
Control Center the settings that were carried forward to KDE 3.3 are all
flagged with the string " (KDE3.2)" so they're easy to identify and
either fix or discard and re-create.
For example, in working with the problems getting OpenOffice.org to launch
via the wrapper script in /usr/X11R6/bin, OOo-wrapper, I found that the
application window was being confined to the size of the OpenOffice.org
splash window! Eradicating the carry-over Window-Specific settings from
the Control Center freed OOo from this left-over and allowed me to
re-create new settings that reflected the variety of windows in
OpenOffice.org.
Randall Schulz
I've got SuSE 9.0 Pro and I just upgraded to the latest KDE 3.3 packages from
the SuSE supplementary feed using YAST. I've done this loads before and
everything has been fine.
Now however, konqueror has started to abort (SIGABRT) when I start it up with
the web profile. With the file browsing profile it is fine and the preloaded
instance also starts ok.
The part where it goes wrong is when its preloading some kparts:
konqueror: kparts/factory.cpp:79: virtual QObject*
KParts::Factory::createObject(QObject*, const char*, const char*, const
QStringList&): Assertion `!parent ||parent->isWidgetType()' failed.
I've tried redownloading and reinstalling kdelibs, kdebase and any other kde
packages that I could find which contain kparts or konqueror stuff. I've also
reinstalled QT just in case something got corrupted, but it hasn't fixed it.
The error seems to be pretty low level to me, yet I cannot find any other KDE
app that is affected like this. Even Quanta and its web preview work fine and
I cannot find anything at bugs.kde.org.
Has anyone else seen this? Thanks
--
Colin Pinkney
http://www.cpinkney.org.uk
