Re: kdeeject - unmouting media patch
Hi all interested users,
I sat down and patched eject 2.0.13 which comes with debian woody.
Now, eject does not follow any symlinks to device files, but uses the
original command line argument to look up the mount point and tries
to unmount the device. You have to use the same device file name
(either a real file or a symlink) to eject as to mount the media.
This is quite a quick'n'dirty patch, but both eject and kdeeject
works for me now :-)
Tobias
Am Mittwoch, 11. Juni 2003 23:17 schrieb David Pye:
> Hmm - here's a thought perhaps?
>
> the piece of main page you quoted says:
> > ... Eject may not always be able to determine if the device is
> > mounted (e.g. if it has several names). If the device name is a
> > symbolic link, eject will follow the link and use the device that
> > it points to. ...
>
> Could we not work around this?
>
> If I read that right, eject behaves by following the link and
> trying to umount the link destination as a device rather than a
> mount point if it was passed a symbolic link.
>
> Couldn't we make kdeeject simply dereference the symbolic link and
> call eject with the parameter of the link DESTINATION?
>
> So if you tried to eject /mnt/cdrom via kdeeject and it's a symlink
> to /cdrom, couldn't kdeeject run eject /mnt/cdrom?
>
> Assuming kdeeject works on mount points not devices, then is there
> a downside to this I haven't yet seen? :)
>
> David
--
/"\ ASCII Ribbon Campaign - against HTML mail
\ / No proprietary formats in attachments without request
X i.e. *NO* WORD, POWERPOINT or EXCEL documents
/ \ Respect Open Standards
http://www.fsf.org/philosophy/no-word-attachments.html
http://www.goldmark.org/netrants/no-word/attach.html
Registered Linux User #293344
31a32,54
> /
> *
> * You Are Using An Quick'n'Dirty-Patch !!!
> *
>
> *
> * With this patch it _should_ be possible to use symlinks on device
> * files in /etc/fstab and using this version of eject (with the
> * symlink as parameter) to unmount the device and eject the
> * respective media. In the original version eject followed the
> * symlinks and used the 'real' files to look up the mount point.
> * The result was (where /dev/cdrom -> sr1 -> scd1):
> *
> * # eject /dev/cdrom
> * eject: unable to eject, last error: Invalid argument
> *
> * as eject tried to unmount /dev/scd1 while /dev/cdrom is used
> * in /etc/fstab.
> *
> * No other file (esp. man-page 'eject.1') has been updated!
> *
> */
>
114a138
> "With quick'n'dirty patch to use symlinks on device files of mounted devices\n"
813a838
> char *fullName2;
866c891
< free(fullName);
---
> fullName2=fullName;
879c904
< mounted = MountedDevice(fullName, &mountName, &deviceName);
---
> mounted = MountedDevice(fullName2, &mountName, &deviceName);
892c917
< mountable = MountableDevice(fullName, &mountName, &deviceName);
---
> mountable = MountableDevice(fullName2, &mountName, &deviceName);
897c922
< printf(_("%s: `%s' is not a mount point\n"), programName, fullName);
---
> printf(_("%s: `%s' is not a mount point\n"), programName, fullName2);
Re: Packaging very large i18n material
On Tuesday 10 June 2003 08:12, Ben Burton wrote: > Sure, it was always going to come from one source package. It's the 37 > *binary* packages I was worried about, which is what the end users have > to deal with. Are there any thoughts or visions on how to deal with the ever-growing number of packages at all? Having package tags and such, it should be easy to filter out those that are not relevant to the end user. For instance, a package 'debian-personalizer', which gets fed from the new installer, would tag all i18n packages it knows as 'hidden', so that normal operations (aptitude, apt-cache, ...) won't see them, but debian-personalizer can then be used to modify system-wide i18n-related settings. This would imply 3 assumptions: - package tools know these tags (which could be prefixed with apt:: or whatever) - it is possible to setup tag overrides, both as root and as normal user, so if I want package A to carry tag B, so be it - the gain: if less packages are considered, less RAM and calculation time is needed (not sure about dependencies though) Another such use would be to tag all laptop-related packages as hidden if the user indicates that a PC is in use. Or to hide all X11-related packages if a console-only system is to be set up. Just random thoughts, so that packages can be used what they're intended for... Josef -- Play for fun, win for freedom.
Re: Qt packages when installing KDE 3.1.2 on stable
Looks like the kde.org mirrors are missing the Qt packages for powerpc. Specifically: Package: libqt3-mt (It's in binary-i386) but under binary-powerpc, these are the only libqt3 packages: Package: libqt3-compat-headers Package: libqt3-headers Package: libqt3-i18n Package: libqt3-plugins-headers There's a number of Qt packages missing, including the qt-embedded dev kit etc. Shows how many people use the PPC packages ;) David
Re: Packaging very large i18n material
Following on from this, what about: KDE already groups languages (well kpersonalizer does ;)) as Eastern Europe, Western Europe, Asia, etc... Couldn't we compromise and have language packs similarly? ie I want Chinese, so I have to put up with koffice-i18n-asia, french koffice-i18n-weu (western europe ;)) Not ideal, but better than having a huge i18n package containing loads of languages I don't want... David On Wednesday 11 June 2003 21:06, Mike Mestnik wrote: > > The question is how to actually package it. All of the available options > > have clear drawbacks. > > The > options as I see it are as follows. > > > 1) Build a single koffice-i18n binary package. > > 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n). > > I would make a compromise from 1 & 2. Have 10 or 16 binary packages /w 4 > i18n each. This won't have one big package, but also won't clutter up the > archive too badly. Sadly this is a maintainer non-friendly solution. > > Since all packages could have this problem, it would be better for every > one if there was a standered way of deviding up il8n. The user would know, > be told, that his il8n are in *-i18n-af vs *-i18n-gl... > > Seams poor and bad I know, just an idea. > > __ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com
Re: kdeeject - unmouting media patch
Hmm - here's a thought perhaps? the piece of main page you quoted says: > ... Eject may not always be able to determine if the device is mounted > (e.g. if it has several names). If the device name is a symbolic > link, eject will follow the link and use the device that it points > to. ... Could we not work around this? If I read that right, eject behaves by following the link and trying to umount the link destination as a device rather than a mount point if it was passed a symbolic link. Couldn't we make kdeeject simply dereference the symbolic link and call eject with the parameter of the link DESTINATION? So if you tried to eject /mnt/cdrom via kdeeject and it's a symlink to /cdrom, couldn't kdeeject run eject /mnt/cdrom? Assuming kdeeject works on mount points not devices, then is there a downside to this I haven't yet seen? :) David
Qt packages when installing KDE 3.1.2 on stable
A quick question which I'm sure must have an obvious answer. Installing the KDE 3.1.2 woody backport from a ftp.kde.org mirror asks for a matching Qt library which I only have an older version of. Where can I find the correct Qt package version? Thanks Jonathan Riddell
Re: compiling kdelibs4/arts failing in linker stage
After investigating the problem some more I found out that f.ex. "Arts::ObjectManager::the" is in the libarts1-dev package, more precisely in /usr/lib/libartsflow_idl.so.1.0.0. And I realized that the libarts1-dev package was not installed on my system so I installed it. I thought that I might be lucky and add the library manually, by adding -lartsflow_idl to the compile comand line below - but no, it doesn't work - libtool seems to be ignoring the extra parameter and/or not linking to the shared library. Can anybdody help? Do I have to: kdelibs $ make clean; ./configure --blah --blah; make; make install again and have my poor laptop compile for another two or three days with me running back and forth to see whether it didn't break/stop somewhere in the middle? Is there any other way to tell that libtool monster to add one further library? Or is libarts compiled with an old compiler? How can I find out? Help is still, very, very much appreciated, *t On Wed, 11 Jun 2003, tomas pospisek wrote: > Hello kde packagers and hackers, I've been trying to compile kdelibs4 from > CVS against current (unstable) Debian infrastructure and I'm failing in > the arts directory. To me it looks like libvorbis0a (from unstable, > together with libvorbis-dev) was not built with current gcc-3.2. > > Could anybody who did succeed in compiling kdelibs give me a hint? It > would be very, very, very wellcome since it is the 4th attempt on my > laptop at home and I've been compiling it for 5 days straight now :-/ > > Help would be very, very wellcome. > > (compiling against qt from unstable, libvorbis(0a/-dev) from unstable, > gcc-3.3 from unstable) > > --- > > Making all in kde > make[1]: Entering directory > `/home/tpo/sync_tpo2/src/projects/karmCVS/KDE/CVS/kdelibs/arts/kde' > /bin/sh ../../libtool --silent --mode=link --tag=CXX g++ > -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W > -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE > -Wcast-align -Wconversion -Wchar-subscripts - > O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions > -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_ > NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION-o > libartskde.la.closure libartskde_la_closure.lo -L/u > sr/X11R6/lib -L/home/tpo/src/projects/karmCVS/KDE/kde-HEAD/lib > -no-undefined -version-info 3:0:2 artskde.lo kioinput > stream_impl.lo kplayobject.lo kplayobjectfactory.lo kartsfloatwatch.lo > kartsdispatcher.lo kaudiorecordstream.lo kartss > erver.lo kdatarequest_impl.lo kaudioconverter.lo kvideowidget.lo > kplayobjectcreator.lo ../../kio/libkio.la -lqtmcop -l > soundserver_idl > libtool: link: warning: `-version-info' is ignored for programs > .libs/artskde.o(.text+0x18): In function > `Arts::KFloatWatchProxy_base::_create(std::basic_string std::char_trait > s, std::allocator > const&)': > : undefined reference to `Arts::ObjectManager::the()' > .libs/artskde.o(.text+0x20): In function > `Arts::KFloatWatchProxy_base::_create(std::basic_string std::char_trait > s, std::allocator > const&)': > : undefined reference to > `Arts::ObjectManager::create(std::basic_string std::char_traits, std::allocator har> > const&)' > .libs/artskde.o(.text+0xac): In function > `Arts::KFloatWatchProxy_base::_fromString(std::basic_string std::char_t > raits, std::allocator > const&)': > : undefined reference to > `Arts::ObjectReference::ObjectReference[in-charge]()' > > and so forth > > Thanks, > *t > > -- > Why is the US governement lying? http://democrats.com/images/lindh-naked.jpeg > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- Im Gazastreifen, dem laut Uno-Angaben am dichtesten besiedelten Flecken der Erde, leben unter 1,3 Millionen Palästinensern 5000 Israelis und okkupieren 40 Prozent der Fläche. NZZ 8.4.2002
Re: kdm locale problem
gaskavahkku, geassemÃnu 11. b. 2003 20.28, LeVA don ÄÃllet: > > If I start kde from kdm, I lose my localisation settings in kde. I am > using hu_HU in locales. If I start kde from a console with startx, > everything is Ok. But when I am starting kde from kdm, the programs that > uses the translated .m4 or .po files, or just have some translated > files, does not seems to be in hungarian language (ex.: xchat, licq). > They are in english. In the kde control center, I can set up kdm to > display the kdm buttons and messages (login, shutdown etc...) in > hungarian. So that is ok. The problem is when I start kde from the kdm > login manager, it seems, that kdm "resets" the localisations, and sets > the lang to en, or en_US (or something like that). If I start a konsole > from kde, and run this: > > echo $LANG > I get "hu_HU". > > That is why I can not understand this problem. It seems, that I am using > hu_HU locales, but the kde programs, and other (for > example Xchat, or Licq) programs doesn't recognise the hu_HU locales, > and falls back to english. And this is all because I started kde from > the kdm login manager, and not from console with startx. > This is because, when starting from kdm, your ~/.profile (or where ever your environment variables are specified) aren't read. I have a .xsession file that goes something like this: #!/bin/sh export LANG=se_NO.UTF-8 exec /usr/bin/startkde This way the LANG variable is inherited by all programs in the session. Hope this helps. Regards, BÃrre Gaup, Kiruna, Sweden pgpW7pjTPlrAw.pgp Description: signature
kpersonalizer Debian Woody, KDE 3.12
Filed a bug report, but this may be Debian Specific. kpersonalizer works perfectly, when run on a new user, but once the user has run it once, and you try to run it again, it uses 100% of memory, before getting killed. Anyone else running into this? Repeatable on every Woody installation we have. -- -- "Catch the Magic of Linux..." Michael Peddemors - Senior Consultant LinuxAdministration - Internet Services NetworkServices - Programming - Security Wizard IT Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com LinuxMagic is a Registered TradeMark of Wizard Tower TechnoServices Ltd. (604)589-0037 Beautiful British Columbia, Canada
Re: Packaging very large i18n material
> The question is how to actually package it. All of the available options have > clear drawbacks. The > options as I see it are as follows. > > 1) Build a single koffice-i18n binary package. > 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n). I would make a compromise from 1 & 2. Have 10 or 16 binary packages /w 4 i18n each. This won't have one big package, but also won't clutter up the archive too badly. Sadly this is a maintainer non-friendly solution. Since all packages could have this problem, it would be better for every one if there was a standered way of deviding up il8n. The user would know, be told, that his il8n are in *-i18n-af vs *-i18n-gl... Seams poor and bad I know, just an idea. __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
Re: kdeeject - unmouting media patch
Am Mittwoch, 11. Juni 2003 20:10 schrieb Christian Hubinger: > Hi! > > sorry for the cross-posting but i think this should go to both > lists. Fine, have a look at what I wrote below and forward it to the other list. > > On Wednesday 11 June 2003 11:42, Volker Krause wrote: > > On Tuesday 10 June 2003 13:27, Christian Hubinger wrote: > > > not really :-( > > > here on my woody ejectt unmounts the device when i type eject > > > /cdrom BUT if i'm using the device name eject /dev/cdrom (which > > > is a symbolic link) eject does not umount and throws an error. > > > i don't know if thats special to the debian version of eject > > > but here it definately does not work with the real device names > > > (as used in /etc/fstab) > > > > > > [EMAIL PROTECTED]:~$ mount /dev/cdrom > > > [EMAIL PROTECTED]:~$ eject /dev/cdrom <- does not work > > > eject: unable to eject, last error: Invalid argument > > > > > > ^^^ [EMAIL PROTECTED]:~$ umount /dev/cdrom > > > [EMAIL PROTECTED]:~$ eject /dev/cdrom <- works > > > > > > [EMAIL PROTECTED]:~$ mount /dev/cdrom > > > [EMAIL PROTECTED]:~$ eject /cdrom <- works > > > > > > so this seems to be a bug in eject. But i think for a quick > > > workaround of that situation the patch i sent should be ok. > > > > > > Please let me know if this behaviour is special to the debian > > > version of eject, so that i can fill a bugreport about it. > > > > seems to work here with eject from SuSE 8.2: > > vkpc3:/home/vkrause # eject -V > > eject version 2.0.13 by Jeff Tranter ([EMAIL PROTECTED]) > > can anyone else reproduce this strange eject behaviour with woody? > If yes i will send a bugreport. I did investigate this problem lately. man eject told me: ... Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to. ... So, it's not a bug, it's a feature :-> If you put the "real" device file (not a symlink) in /etc/fstab, eject works fine with mounted devices! Actually, this should be discussed in the debian-user* or some other lists rather than debian-kde. On this list, you should discuss why kdeeject does not work (which uses eject to do its job) :-) > > greetings, > chris > Tobias -- /"\ ASCII Ribbon Campaign - against HTML mail \ / No proprietary formats in attachments without request X i.e. *NO* WORD, POWERPOINT or EXCEL documents / \ Respect Open Standards http://www.fsf.org/philosophy/no-word-attachments.html http://www.goldmark.org/netrants/no-word/attach.html Registered Linux User #293344
smb:// authentification broken in unstable
Hi, I am running samba and KDE from sid and authentication to other systems stopped working. The authentication dialog comes up (btw, why doesn't the cursor blink in the password field? This is totally annoying!) but the values stated there are all empty. Entering the pass, the dialog comes up again and again and... The work-around: smbclient -L host -U username and entering the same password once, works. Obviously, samba has some caching and from now on smbkio works. Any recommendations? 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.org pgpWxc9VOaOEE.pgp Description: signature
kmailcool
Hi.. .i'm quite confused with kmail cool. What's exactly supposed to be? A kmail fork to be merged into kontact? A kmail version with more features? What's the future of kmail and kmail cool? :-/ Regards, RAfa Rodriguez -- Night confuses me
kdm locale problem
Hi! I have a rather complicated problem with kdm, and I am from Hungary, but I will try to be as clear as I can :) Hope that someone could help me. So, let's start. Some background information: I am using Debian with woody (stable) packages. This comes with xfree 4.1.0. I have added an apt source for the new kde binaries (http://download.kde.org... etc...). I have installed kde 3.1.2 from that apt source. Everything is just fine :) But :) I have installed xfree 4.2.1, but not from Debian mirrors, instead from www.xfree86.org. I have downloaded the new binaries and installed it. Wow it is cool. Faster than the older 4.1.0. Unfortunately the kdm which came from the kde.org's apt source is not running. In the log it says there is some xdcmpwrapper problem. Oh well, I wrote to some of my friends, and they gave me an advice, that I should compile kdm from the kdebase sources to make it work with the new (4.2.1) xfree86. Ok. It took sooo long... :)) But when it finished I could not wait to try it. Yeah it is working. The kdm runs, and I am using 4.2.1 xfree. But you know in every good thing, there is something bad :) And here comes the real problem: If I start kde from kdm, I lose my localisation settings in kde. I am using hu_HU in locales. If I start kde from a console with startx, everything is Ok. But when I am starting kde from kdm, the programs that uses the translated .m4 or .po files, or just have some translated files, does not seems to be in hungarian language (ex.: xchat, licq). They are in english. In the kde control center, I can set up kdm to display the kdm buttons and messages (login, shutdown etc...) in hungarian. So that is ok. The problem is when I start kde from the kdm login manager, it seems, that kdm "resets" the localisations, and sets the lang to en, or en_US (or something like that). If I start a konsole from kde, and run this: echo $LANG I get "hu_HU". That is why I can not understand this problem. It seems, that I am using hu_HU locales, but the kde programs, and other (for example Xchat, or Licq) programs doesn't recognise the hu_HU locales, and falls back to english. And this is all because I started kde from the kdm login manager, and not from console with startx. Is there some extra option which I must add when I configure kdebase to support other languages? Or it is autodetect everything? Or is there a kdm binary, which is working with 4.2.1 xfree (don't have the Xdcmpwrapper failure), and "acts" like the kde.org's kdm binary (is working with locales :) ? I hope you understand everything, and can help me. Please write me, if some info is missing, or you need to test something. Thanks for the answer! Daniel Levai -- LeVA
Re: kdeeject - unmouting media patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! sorry for the cross-posting but i think this should go to both lists. On Wednesday 11 June 2003 11:42, Volker Krause wrote: > On Tuesday 10 June 2003 13:27, Christian Hubinger wrote: > > not really :-( > > here on my woody ejectt unmounts the device when i type eject /cdrom BUT > > if i'm using the device name eject /dev/cdrom (which is a symbolic link) > > eject does not umount and throws an error. > > i don't know if thats special to the debian version of eject but here it > > definately does not work with the real device names (as used in > > /etc/fstab) > > > > [EMAIL PROTECTED]:~$ mount /dev/cdrom > > [EMAIL PROTECTED]:~$ eject /dev/cdrom <- does not work > > eject: unable to eject, last error: Invalid argument > > ^^^ > > [EMAIL PROTECTED]:~$ umount /dev/cdrom > > [EMAIL PROTECTED]:~$ eject /dev/cdrom <- works > > > > [EMAIL PROTECTED]:~$ mount /dev/cdrom > > [EMAIL PROTECTED]:~$ eject /cdrom <- works > > > > so this seems to be a bug in eject. But i think for a quick workaround of > > that situation the patch i sent should be ok. > > > > Please let me know if this behaviour is special to the debian version of > > eject, so that i can fill a bugreport about it. > > seems to work here with eject from SuSE 8.2: > vkpc3:/home/vkrause # eject -V > eject version 2.0.13 by Jeff Tranter ([EMAIL PROTECTED]) can anyone else reproduce this strange eject behaviour with woody? If yes i will send a bugreport. greetings, chris - -- Windows is a 32 bit shell for a 16 bit extension to an 8 bit Operating System designed for a 4 bit microchip by a 2 bit company which can't stand one bit of competition. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+53B+AgmexFOwd6YRAs0RAJ9jdWmdcvtBFN5/aDYr5XBxZ3wiBACdF6Zm eNJBxJwiqOOd9Uvr1URELBc= =e2sp -END PGP SIGNATURE-
Re: Konqueror and SSL - how do I make it work?
On Wed, Jun 11, 2003 at 10:09:34AM -0500, Irish, Jon D BAE SYSTEMS wrote: > Wookey, > Make sure that you have libssl09 installed. It worked for me. thanx for that tip, but I already have libssl09 installed. What else can I check? > -Original Message- > From: Wookey [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 11, 2003 4:56 AM > To: debian-kde@lists.debian.org > Subject: Konqueror and SSL - how do I make it work? > > > Hi people - I'm not on this list - please CC:me > > I recently tried KDE and found that it was very good. I find konqueror > particularly satisfactory as it does a reasonable impersonation of MC > when file browsing. > > However The absence of SSL support is giving me a lot of grief at the > moment. I've googled around a bit and looked at man pages and debian > readme's but I can't work out what I need to do to make it work. I am > assuming that it can be made to work under Debian? > > I'm running testing. Konq verion is 4:2.2.2-14. If I go to View-security > I get 'SSL support is not enabled in this version of Konqueror'. > > I can find no 'konqueror-ssl' package. > Messages from last year tell me I need to install kdelibs3-crypto but > that only seems to exist in stable. What is needed for Testing? > > Newer messages suggest that kdelibs3 needs libssl0.9.6 installed (it's a > recommends). Seems fair enough. But I've got that installed. I've also > got libssl0.9.7. > > Is there some option somewhere that I need to turn on to make this work? > The whole thing does seem to be rather newbie-proof? > > Any clues most welcome. > > TIA > > > > -- > Wookey > -- > Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 > 811679 > work: http://www.aleph1.co.uk/ play: > http://www.chaos.org.uk/~wookey/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
RE: Konqueror and SSL - how do I make it work?
Wookey, Make sure that you have libssl09 installed. It worked for me. Sincerely, Jon -Original Message- From: Wookey [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 4:56 AM To: debian-kde@lists.debian.org Subject: Konqueror and SSL - how do I make it work? Hi people - I'm not on this list - please CC:me I recently tried KDE and found that it was very good. I find konqueror particularly satisfactory as it does a reasonable impersonation of MC when file browsing. However The absence of SSL support is giving me a lot of grief at the moment. I've googled around a bit and looked at man pages and debian readme's but I can't work out what I need to do to make it work. I am assuming that it can be made to work under Debian? I'm running testing. Konq verion is 4:2.2.2-14. If I go to View-security I get 'SSL support is not enabled in this version of Konqueror'. I can find no 'konqueror-ssl' package. Messages from last year tell me I need to install kdelibs3-crypto but that only seems to exist in stable. What is needed for Testing? Newer messages suggest that kdelibs3 needs libssl0.9.6 installed (it's a recommends). Seems fair enough. But I've got that installed. I've also got libssl0.9.7. Is there some option somewhere that I need to turn on to make this work? The whole thing does seem to be rather newbie-proof? Any clues most welcome. TIA -- Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Konqueror and SSL - how do I make it work?
Hi people - I'm not on this list - please CC:me I recently tried KDE and found that it was very good. I find konqueror particularly satisfactory as it does a reasonable impersonation of MC when file browsing. However The absence of SSL support is giving me a lot of grief at the moment. I've googled around a bit and looked at man pages and debian readme's but I can't work out what I need to do to make it work. I am assuming that it can be made to work under Debian? I'm running testing. Konq verion is 4:2.2.2-14. If I go to View-security I get 'SSL support is not enabled in this version of Konqueror'. I can find no 'konqueror-ssl' package. Messages from last year tell me I need to install kdelibs3-crypto but that only seems to exist in stable. What is needed for Testing? Newer messages suggest that kdelibs3 needs libssl0.9.6 installed (it's a recommends). Seems fair enough. But I've got that installed. I've also got libssl0.9.7. Is there some option somewhere that I need to turn on to make this work? The whole thing does seem to be rather newbie-proof? Any clues most welcome. TIA -- Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
compiling kdelibs4/arts failing in linker stage
Hello kde packagers and hackers, I've been trying to compile kdelibs4 from CVS against current (unstable) Debian infrastructure and I'm failing in the arts directory. To me it looks like libvorbis0a (from unstable, together with libvorbis-dev) was not built with current gcc-3.2. Could anybody who did succeed in compiling kdelibs give me a hint? It would be very, very, very wellcome since it is the 4th attempt on my laptop at home and I've been compiling it for 5 days straight now :-/ Help would be very, very wellcome. (compiling against qt from unstable, libvorbis(0a/-dev) from unstable, gcc-3.3 from unstable) --- Making all in kde make[1]: Entering directory `/home/tpo/sync_tpo2/src/projects/karmCVS/KDE/CVS/kdelibs/arts/kde' /bin/sh ../../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts - O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_ NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION-o libartskde.la.closure libartskde_la_closure.lo -L/u sr/X11R6/lib -L/home/tpo/src/projects/karmCVS/KDE/kde-HEAD/lib -no-undefined -version-info 3:0:2 artskde.lo kioinput stream_impl.lo kplayobject.lo kplayobjectfactory.lo kartsfloatwatch.lo kartsdispatcher.lo kaudiorecordstream.lo kartss erver.lo kdatarequest_impl.lo kaudioconverter.lo kvideowidget.lo kplayobjectcreator.lo ../../kio/libkio.la -lqtmcop -l soundserver_idl libtool: link: warning: `-version-info' is ignored for programs .libs/artskde.o(.text+0x18): In function `Arts::KFloatWatchProxy_base::_create(std::basic_string, std::allocator > const&)': : undefined reference to `Arts::ObjectManager::the()' .libs/artskde.o(.text+0x20): In function `Arts::KFloatWatchProxy_base::_create(std::basic_string, std::allocator > const&)': : undefined reference to `Arts::ObjectManager::create(std::basic_string, std::allocator > const&)' .libs/artskde.o(.text+0xac): In function `Arts::KFloatWatchProxy_base::_fromString(std::basic_string, std::allocator > const&)': : undefined reference to `Arts::ObjectReference::ObjectReference[in-charge]()' and so forth Thanks, *t -- Why is the US governement lying? http://democrats.com/images/lindh-naked.jpeg
xml-based config files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hello, perhaps this is a bitt offtopic... would it be possible to base configfiles to a xml format so that there is only a need of one gui which is abel to interpret these config files and show it to the user in a nice way. this would provide grafic based configuration dialogs to every programm using this xml config files. wolfgang - -- Wenn Du es könntest wie weit würdest Du sie zurückdrehen - die Zeit? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+5vlJuEUiBhld/2URAghxAJ4mmX1a9nRVHCPdFh826ZA1nKeJ+gCaAhPV UsKjp9o5RKBHHVaq87z1w0Y= =wqpN -END PGP SIGNATURE-
