Hello all,
I've managed to resolve all dependencies with the new kde packages,
the 3.1.95 packages, save one. While installing <rpm -Uvh *rpm> as su/
root I get the following error:
error: Failed dependencies:
kdebase3-SuSE <= 9.0 conflicts with kdebase3-3.1.95-0
I've searched this mailing list and several others but I couldn't find any
suggestions or hints to resolve this error. And, a newer kdebase3-SuSE
package has not made its way to the SuSE downloads site, nor have I
found it in the supplementary > kde section on the ftp site.
Has anyone else encountered this problem? Any suggestions?
Thank you, in advance, for any help.
Chris/CMS
Hello!
I've only recently joined this list after you've written your message, therefore
I cannot reply properly. Sorry for inconveniences.
The script you're looking for is the kde startup script itself:
/opt/kde3/bin/startkde
It is "patched" by SuSE and includes all the code to copy the SuSE default icons
and the rest of the configuration. If you want to add some other icons, you can
probably do it there.
Personally I think, this is not a good way to modify the KDE configuration for a
new user, but I will discuss this in an additional message.
Cheers
Olaf
Do the 3.1.95 rpms requires qt-3.3? Is qt-3.3 available?
See following url: http://dot.kde.org/1074527533/1074544034/
--
Richard Bos
Without a home the journey is endless
After a great deal of searching I was able to determine and fix the inability
to get core dumps in SLP 9.0 under a KDM login. Evidently, gpg-agent plays
some role in a KDM login, what I am not sure but it explicitly disables core
dumps in it's main function.
I was able to build a new version of /usr/bin/gpg-agent from package
newpg-0.9.4-119 using it's source RPM and build(1). It is missing several
dependencies for the build if BUILD_ROOT is set in your environment. If you
do not set BUILD_ROOT it uses /var/tmp and does not have any missing
dependencies. I have included the changes needed to gpg-agent.c and
instructions for building a new /usr/bin/gpg-agent.
which is just commenting out the call to:
#if notdef
may_coredump = disable_core_dumps ();
#endif
in agent/gpg-agent.c
Also note, you must comment out the following in /etc/profile:
#ulimit -Sc 0 # don't create core files
Perhaps ULB or someone will be kind enough to create a package. Maybe SuSE
will fix it.
Best Regards.
==================
Install the source rpm package for newpg-0.9.4-119 from the YaST via
Yast2->Software->Install and Remove Software and searching for newpg.
Check the source checkbox (scrolled off the screen).Install and Remove
Software and searching for newpg.
Check the source checkbox (scrolled off the screen). Push the accept button.
It will tell you which disc to get source from or to turnover the DVD disc
if you have the DVD.
Now as root create a temporary directory and cd to it.
# mkdir temp
# cd temp
# cp /usr/src/packages/SOURCES/die-with-parent.diff .
# cp /usr/src/packages/SOURCES/newpg-0.9.4.tar.bz2 .
# cp /usr/src/packages/SPECS/newpg.spec .
Now manually mount the install disc, mine goes to /media/dvd
# mount /media/dvd
# build newpg.spec
If you have never done this before it uses /var/tmp by default. This directory
is normally clean on reboot so you lose everything. Make sure you have enough
disk space free as build uses a chroot(1)ed environment. I have the
environmental variable BUILD_ROOT set to "/build" on my system but for this
discussion I will use /var/tmp as if BUILD_ROOT was not set.
The build copies all sorts of libraries and executeables from install system
to the chroot(1)ed environment. This will take several minutes. After the
build
finishes if no packages were missing then:
If unset use /var/tmp in place of ${BUILD_ROOT)
# cp ../newgpg-agent.c
${BUILD_ROOT}/buildroot//usr/src/packages/BUILD/newpg-0.9.4/agent/gpg-agent.c
# cd ${BUILD_ROOT}/buildroot//usr/src/packages/BUILD/newpg-0.9.4
# make
# cp agent/gpg-agent /usr/bin/gpg-agent
Reboot and you will be able to get coredumps.
==================
--
_/_/_/ Bob Pearson gottadoit(a)mailsnare.net
_/_/_/ "The best way to get information on Usenet is not to ask a
_/_/_/ question, but to post the wrong information." - Aahz' Law
Hi,
I came across the need to use kdialog, specifically the 'combobox'
option. When I key in: kdialog --combobox I receive the following
error:
kdialog: Unknown option '--combobox'.
kdialog: Use --help to get a list of available command line options.
I'm running SuSE 9.0 with latest YOU updates. I understand 'kdialog' is
part of kdebase, which lends me to believe that I may have an bad
install? Or possibly missing a library or two? Any assist is greatly
appreciated.
Thank you
/Carl
Does anybody know why KDE 3.1.5 is not available through SuSE YOU? What is the
official, end user oriented way of updating KDE to 3.1.5 and KDE 3.2 when
time comes (can't wait)?
-j
--
Linux install party in La Paz, Bolivia
<http://weblog.janus.dk/archives/2002/10/19/000184.html>
Hi all,
And isn't the newest 3.2 just grand? ;o)
Some nice fixes and changes. For those that haven't seen it yet, you
are in for a treat with KDE 3.2 final.
I've got a question to any of those running the new KDE. In KMail, I
can't seem to open kaddressbook anymore. I can open from a konsole
or from a desktop icon, but I cannot open from within kmail. Neither
from the menu or toolbar icon.
Anyone else experiencing the same? Suggestions on how to fix?
Lee
--
--- KMail v1.6 --- SuSE Linux Pro v9.0 ---
Registered Linux User #225206
On any other day, that might seem strange...
On some messages I get the following displayed just after the header:
/Message was signed with unknown key 0x<some hex numbers>
The validity of the signature cannot be verified.
Status: No public key to verify the signature/
Does this indicate that I have not configured KMail correctly? Where is
the public key mentioned in the message.
--
"Don't you see that the whole aim of Newspeak is to narrow the range of
thought? In the end we shall make thoughtcrime literally impossible,
because there will be no words in which to express it."
-- George Orwell as Syme in "1984"
The switch in KNode to emulate KMail keyboard shortcuts does not seem to
work. Is this a known bug? Or is something more needed to properly
configure KNode?
Albert
