KOffice 1.3 Beta1 and Gideon
Hello, is anyone planing to make debian packages of KOffice 1.3 Beta 1 and Gideon Alpha 4 for SID. If noone makes packages, what is the best method to install these packages parallel to the existing debs of the stable versions? Using Konstruct? Thanks Michael
Re: KOffice 1.3 Beta1 and Gideon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op vrijdag 25 april 2003 11:13, schreef Michael Thaler: > Hello, > > is anyone planing to make debian packages of KOffice 1.3 Beta 1 and > Gideon Alpha 4 for SID. If noone makes packages, what is the best You can get from Gideon from deb http://debiantoday.dnip.net/debian ./ I don't know about KOffice. - -- Casper Gielen [EMAIL PROTECTED], [EMAIL PROTECTED] - -- Wiggle your mouse. Its just a screensaver. _Sprocket_ on Slashdot -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+qQH+IhQIPPgOSvcRAgj+AJ9YHsVJ8DZxvx2DBaaEpdoQWYsM5wCfYoor dXJqnJMN6ZUmDg2J3Af7Lzc= =sx6D -END PGP SIGNATURE-
Re: SSH problem with cervisia
On Wednesday 23 April 2003 01:13, Felix Homann wrote: > Can you be a little more precise? What's happening on the console? Does > your problem occur using ssh directly or from within another application? directly. > Why don't you use ssh from Sid? What's different in Woody? (BTW, no > problems here on Sid...) > > You might even like to take a look at ssh-agent and keychain. For more > information look at > http://www-106.ibm.com/developerworks/library/l-keyc.html. [EMAIL PROTECTED]:~$ ssh localhost Linux dionysos 2.4.21-pre5-ac3 #1 Wed Apr 23 19:51:33 CEST 2003 i686 unknown unknown GNU/Linux Most of the programs included with the Debian GNU/Linux system are freely redistributable; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Apr 25 11:33:38 2003 [EMAIL PROTECTED]:~$ ... in between the ssh command and the welcome message an ugly box will show up asking for the password. The weird thing is that it works from the console if I run ssh as root (just noticed by accident, I never ssh as root): dionysos:~# ssh localhost [EMAIL PROTECTED]'s password: Last login: Fri Apr 25 12:02:04 2003 from dionysos on pts/0 Linux dionysos 2.4.21-pre5-ac3 #1 Wed Apr 23 19:51:33 CEST 2003 i686 unknown unknown GNU/Linux Most of the programs included with the Debian GNU/Linux system are freely redistributable; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Apr 25 12:02:04 2003 from dionysos dionysos:~# -- Frank Van Damme| "Saying 8MB of RAM doesn't do as much anymore is http://www.| like saying a gallon of water holds more than it openstandaarden.be | did in 1988."--George Adkins
Re: KOffice 1.3 Beta1 and Gideon
> I don't know about KOffice. KOffice will be coming after I return from a particularly intensive computer science school where I'm teaching for another week. b. :)
KDE apps not docking in kicker 'systray' when using Sawfish
I use KDE 3.1.1 with Sawfish as WM (it's my favorite WM - don't want to switch to kwin). All KDE apps which should dock in 'systray' part of kicker open small window with icon in it. I saw this in KNotes, Kopete, Psi. All of them docks when I use kwin instead of sawfish. Where is a bug? Gaim 0.6x docks perfectly in panel. I start X using gdm with X Session: #!/bin/bash export GDK_USE_XFT=1 export QT_XFT=1 source ~/.bash_profile export KDEWM=`which sawfish` /usr/bin/gnome-settings-daemon & /usr/bin/X11/unclutter & /usr/bin/X11/xmodmap ~/.xmodmap source `which startkde` -- APT: deb http://www.hrw.one.pl/apt/ sid/
Re: KDE 3 for woody
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 23. April 2003 17:36 schrieb Marc Meier: > Hello, > > where can I get KDE 3.1.x for woody? try: www.apt-get.org wolfgang - -- Und dann hat er Sie geküsst Wo das Meer zu Ende ist Ihre Lippen schwach und blass Und seine Augen werden nass Ramms+ein - Mutter - Nebel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+qRyVuEUiBhld/2URAgcOAJ0VX4eGvWI585uzoG+WRe8P+DWjpQCeIHDs qpKf/FWP9f276dAasF+Ye9I= =9Mpr -END PGP SIGNATURE-
sessreg before Kde starts
Hi, since I tried to install Quanta (html-editor) I have no chance to login to kde and strangly NO icons for kde in gnome (means they are not pictured in its bar) BUT I can use all of them and Qunata is working fine, too. I get the following after my gdm login: /etc/gdm/PreSession//Default: Registering your session with wtmp and utmp /etc/gdm/PreSession//Default: running: sessreg -a -w /var/log/wtmp -u/var/log/utmp -x "/var/lib/gdm/:0.Xservers" -h " " -l :0 lasius +WM=kde2 +cd /dev/null/home/lasius/.kde2-errors +chmod 600 /home/.kde2-errors +exec What happened? What to do? I am working on a dell laptop Inspiron 5000e within debian woody 2.2.20-idepci. gdm2, kde2, gnome2.2.. thx and be well j:ork
DSA-293-1, DSA-284-1
DSA-284-1 and DSA-293-1 both state For the unstable distribution (sid) this problem will be fixed soon. What exactly is "soon", and what is holding this back? A fix has been available for ages now. Yes, yes, yes I know that people are doing this on their spare time (thanks!) and that this is what comes from running unstable.. All I'm asking is at least a comment on the issue - are we waiting for GCC 5.7 and XFree 8.5 to hit unstable along with Kernel 2.8.21 or only until the first KMail worm declares "Kindly open the attached PDF file"? regards, Volker -- philosophy: The ability to bear with calmness the misfortunes of our friends.
Re: Komba.. (More reasons why it has to reap mounts)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 23 Apr 2003 17:34, Michael Peddemors <[EMAIL PROTECTED]> wrote: > On Wednesday 23 April 2003 06:22, Paul Cupis wrote: > > Deleted users if a much different scenario than users who have > > logged off and left 'long' running processes running. > > Yes, but both have to be handled. Can you think of a basic premise > where if a user doesn't have a process running, he needs the mounts > still? Cron jobs, delayed execution of programs/scripts. > > > Well, we should be able to detect if > > > 1) the user has active processes > > > 2) the user is logged in (Actually that will be covered by 1) > > > > > > If not, the mount can be reaped. > > > > How do you propose to reap the mounts? This is not, AFAIK, > > something which komba is concerned with. > > I heard that, but if the program is used to mount the shares, it > should be able to look after unmounting them.. It can unmount them - doesn't necessarily mean it should reap them. Perhaps you feel the same way about the other mount tools, and smbmount GUIs? > > Description: KDE Samba browser > > Komba2 is a GUI machine and share browser for the > > SMB protocol. Komba2 allows you to scan any number > > of subnets for machines with SMB. The workgroups, > > machines and share are shown in a tree-view. > > For each machine you can then view the list of > > shares, and mount, unmount or browse them. You can > > > > > If you want users to unmount things when they log off, perhaps this > > could be added as an option to komba ( [X] Always unmount upon > > logoff ), but it should not be on by default. if you want unused > > mounts on your system to be unmounted, you need some daemon to do > > that. I am nt currently aware of any such daemon, though I'm sure > > one could be coded. But unmounting something accidentally or > > incorrectly could be disasterous. > > It needs to be addressed, in any case, and if at least any mounts > created by Komba were reaped when unused, then we would be a long > way. Any shares mounted manually, (ie not via Komba) it doesn't have > to deal with.. Then noone has to deal with the whole debian system > logic as a whole, and deal with it strictly in the package that > handles 'mounting and unmounting'. > > Maybe a seperate 'mtab style' record keeping, and a cron job to clean > them would be the simplest, or a Komba Reaper Daemon, and this could > have 'as an option' the ability to clean up system mounts, but this > should not be the default. > > > Perhaps automatic unmounting-upon-closing-komba could be added as a > > They already have that.. > > > user-definable option, but I think that would be a bad idea. One > > should not have to have komba running the entire time one wants to > > use a share mounted _via_ komba. Having an unmount-upon-logoff > > would be better, but > > Yes, precisely > > > would require some part of komba to be called upon KDE logoff to do > > the unmounting. > > But that doesn't handle disco's So a reaper would have to be in > place anyways, so might as well let the reaper do all the work. As > well, it may need to be at the user logoff, and not KDE logoff, > however that might be more satisfying for those liking 'Microsoft > Style' Discos? If you want to take mounting/unmounting out of the users hands, maybe try autofs/automount/whatever it is called. > > I can understand the problem you percieve, but I do not agree with > > your proposed solutions. Users should unmount shares when they have > > finished > > SHOULD??? We aren't dealing with educated users, and expecting 100 > users to remember to do this every day on an xterminal system is > impractical. Educate the users, then? They must have been educated enough to _mount_ the shares, why not unmount them? > > If they do not unmount them, perhaps they had a good reason > > No, it shoudl be that if they have a NEED to keep shares opened after > all their tasks are completed, they should perform some special > operation to do so, but this SHOULD NOT be the default behavior in a > robust system. Some special operation? Like mounting the shares? I assume you mean that auto-reaped shares should be the default, persistant shares should be an option? Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+qbezIzuKV+SHX/kRAg6zAJ0WdqQmUSRlXIZCPnig8uWkgbxeLQCdFhKx CJx/WkOGdNf8PKR961x/qTI= =VmQc -END PGP SIGNATURE-
Re: kprinter still dying in sid
Christophe Prud'homme wrote: [ Wednesday 23 April 2003 09:34 ] | Hi! | | 2-3 weeks ago I asked about the well known problem with kprinter | crashing. After 2 weeks being abroad I come back and see that the | problem is still not solved. | | Can we expect in sid a solution soon? The solution is in KDE CVS and backported to the 3.1 branch for quite some time. It seems that the debian packages didn't follow A bug should be filled if it has not been done yet Best regards C Hi ! I am working with KDE 3.1.1 since it was avaible in SID. Until approximately a week ago kprinter was running without any problem. But I was reading in this newsgroup that other people have problems with kprinter. What I do not understand is, that I have now the same problems (I think that I have the same problem). What I see is: kprinter kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent() called but no data available! Where can I find the log files which are caused by "apt-get dist-upgrade" (I can not see anything at dir /var/log/), because I want to analyze the reason of the misconduct since the last update on the 24.04.2003 ? Best regards FR
Re: Komba.. (More reasons why it has to reap mounts)
On Friday 25 April 2003 15:33, Paul Cupis wrote: > > Yes, but both have to be handled. Can you think of a basic premise > > where if a user doesn't have a process running, he needs the mounts > > still? > > Cron jobs, delayed execution of programs/scripts. Still, default in user land should NOT be to leave these around, and hard mount them if they are going to need this type of behavior. > It can unmount them - doesn't necessarily mean it should reap them. > Perhaps you feel the same way about the other mount tools, and smbmount > GUIs? Yep, but the tool I am dealig with is Komba :) Each mount tool shoudl deal with this issue. Maybe a userland .kde mtab that takes precedence over /etc/mtab? Every KDE app at least can use the same one. > > Educate the users, then? They must have been educated enough to _mount_ > the shares, why not unmount them? Hehehe I see you don't work in the real world.. I hear this often from Linux Developers, but in the real world hard enough to get them to follow simple rules. If they (average office user) can find a way to screw it up, assume they will :) > Some special operation? Like mounting the shares? I assume you mean that > auto-reaped shares should be the default, persistant shares should be > an option? Exactly... But ps, automount won't work (Don't think).. it's great for making a cdrom or floppy available, when you know the path .. -- -- "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: DSA-293-1, DSA-284-1
On Fri, Apr 25, 2003 at 08:37:58PM +0200, Volker Schlecht wrote: > DSA-284-1 and DSA-293-1 both state > > For the unstable distribution (sid) this problem will be > fixed soon. > > What exactly is "soon", and what is holding this back? A fix has been > available for ages now. > > Yes, yes, yes I know that people are doing this on their spare time (thanks!) > and that this is what comes from running unstable.. > > All I'm asking is at least a comment on the issue - are we waiting for > GCC 5.7 and XFree 8.5 to hit unstable along with Kernel 2.8.21 or only > until the first KMail worm declares "Kindly open the attached PDF file"? > > regards, > Volker Anyone with the ability to upload a fixed version to sid feel free to do so. I have approximately 3 weeks left before I graduate from uni so am quite busy. Otherwise expect it to be in sid around May 19. Thanks, Chris
