Re: Trinity
On July 12, 2012 06:40:28 AM Modestas Vainius wrote: Hello, On 2012 m. of July 12 d., Thursday 00:10:57 Bruce Sass wrote: On July 9, 2012 01:54:05 PM hrvojes wrote: On Monday 09 of July 2012 15:48:01 john Culleton wrote: BTW KDE has gone down hill of late. It gets as many complaints as Vista it seems. My solution is simple. I use Trinity which is a clone of KDE 3.5. Try it, you might like it (or not.) Yes, the obvious solution is moving to obsoleted DE. I think you mean, STABLE, not obsoleted... Trinity is actively being developed (albeit slowly), and is a sane, somewhat lighter weight[1], alternative to the resource hungry bleeding edge which is KDE 4, for those who want a KDE experience without all the blood. Trinity discussion is completely irrelevant for debian-kde mailing list because: 1) Trinity is not in Debian. True, but it has been packaged for Stable and Oldstable based systems which makes it more likely to eventually appear in Debian than some random piece of source out there. 2) Trinity is not and has never been KDE despite its origins Despite its orgins as a continuation of the KDE-3.5 codebase, eh. ;) So unless any of above changes, this is not a place for KDE is crap, Trinity rulez. Nowhere is a good place for: KDE is crap, Trinity rulez! However, given Trinity's origins (as KDE-3.5) and goals (be installed alongside and work with KDE-4 and apps), debian-kde is the best place within Debian for someone looking at introducing it into the archive to bring it up-- this is where the DD/DM expertise wrt KDE-3.5 and 4 resides, and this is the place with the most potential for finding interested users. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207121355.17951.bms...@shaw.ca
Re: Trinity
On July 12, 2012 02:10:33 PM Modestas Vainius wrote: Hello, On Thursday 12 July 2012 13:55:17 Bruce Sass wrote: 1) Trinity is not in Debian. True, but it has been packaged for Stable and Oldstable based systems which makes it more likely to eventually appear in Debian than some random piece of source out there. FIY, nobody stepped up to take over maintainance of Qt 3 in Debian. So you can basically forget about KDE 3.5 at this point. 2) Trinity is not and has never been KDE despite its origins Despite its orgins as a continuation of the KDE-3.5 codebase, eh. ;) Everything about KDE 3.5 is long dead. No matter how good or bad it was, its base system (Qt 3) is not supported anymore. Trinity uses the KDE3.5 code and maintain Qt3 themselves, so it is not long dead nor unsupported. So unless any of above changes, this is not a place for KDE is crap, Trinity rulez. Nowhere is a good place for: KDE is crap, Trinity rulez! However, given Trinity's origins (as KDE-3.5) and goals (be installed alongside and work with KDE-4 and apps), debian-kde is the best place within Debian for someone looking at introducing it into the archive to bring it up-- We had this discussion before. It ended up in trolling and left a bad taste for everyone involved. That is unfortunate. :( this is where the DD/DM expertise wrt KDE-3.5 and 4 resides, and this is the place with the most potential for finding interested users. If anyone wanted to bring trinity to Debian, (s)he would have already done it. But every maintainer understands that it is impossible to provide good packages for outdated and basically abondoned software. It may be outdated from the perspective of KDE, but if people are working on it and maintaining its core then it is not abandoned. All you do is encourage people to install random packages of bad quality. Eventually users will face problems and/or break systems, many have already broke. random packages of bad quality... we must be talking about two different things... I am only considering Trinity--KDE-3.5, bits of KDE-4, and the toolkit it is built upon--not arbitrary packages which depend on Qt3. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207121522.05475.bms...@shaw.ca
Re: Trinity
On July 12, 2012 03:37:38 PM Diederik de Haas wrote: Bruce Sass bms...@shaw.ca wrote: Bla bla bla Seriously ??? Yup -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207121542.09568.bms...@shaw.ca
Re: Trinity
On July 12, 2012 02:13:20 PM Pino Toscano wrote: Hi, Alle giovedì 12 luglio 2012, Bruce Sass ha scritto: 1) Trinity is not in Debian. True, but it has been packaged for Stable and Oldstable based systems which makes it more likely to eventually appear in Debian than some random piece of source out there. Not really; consider for example that qt3 has been removed recently from Debian (so squeeze is the last stable release with qt3), so any kind of reintrouction of it into the archive will not be that welcome. That's a good thing... nobody should want old and unmaintained Qt3 apps in the archive. However, it may open the door a little more for the introduction of Trinity since there is now no pressure to accommodate arbitrary Qt3 based apps. So unless any of above changes, this is not a place for KDE is crap, Trinity rulez. Nowhere is a good place for: KDE is crap, Trinity rulez! However, given Trinity's origins (as KDE-3.5) and goals (be installed alongside and work with KDE-4 and apps), debian-kde is the best place within Debian for someone looking at introducing it into the archive to bring it up-- this is where the DD/DM expertise wrt KDE-3.5 and 4 resides, and this is the place with the most potential for finding interested users. No, debian-kde is definitely *not* the place for advertising Trinity in any form, nor for finding your users. Please bring Trinity away from this list, thank you. Sure... all I wanted to do was correct some BS about Trinity being an obsolete clone of KDE-3.5. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207121540.31442.bms...@shaw.ca
Trinity
On July 9, 2012 01:54:05 PM hrvojes wrote: On Monday 09 of July 2012 15:48:01 john Culleton wrote: BTW KDE has gone down hill of late. It gets as many complaints as Vista it seems. My solution is simple. I use Trinity which is a clone of KDE 3.5. Try it, you might like it (or not.) Yes, the obvious solution is moving to obsoleted DE. I think you mean, STABLE, not obsoleted... Trinity is actively being developed (albeit slowly), and is a sane, somewhat lighter weight[1], alternative to the resource hungry bleeding edge which is KDE 4, for those who want a KDE experience without all the blood. Also... it is not a clone of KDE-3.5, it is KDE-3.5, plus backports from KDE-4 and some bits to enable both it and KDE-4 to coexist. I do agree that the `KDE-4 broken, try Trinity instead' way it is being mentioned here recently is uncalled for--it would have been better if a thread looking for comments with respect to getting it into Debian had been started by Trinity's promoter(s) instead. - Bruce [1] Based on my experience of having a couple boxes where KDE-3.5 ran nicely, but KDE-4 turns them into doorstops... one still runs KDE-3.5, the other uses UDE + KDE-4 apps... both would be better served by Trinity. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207111510.58136.bms...@shaw.ca
Re: desktop effects suspended with latest nvidia packages
On April 24, 2012 04:02:44 PM Diederik de Haas wrote: On Tuesday 24 April 2012 18:28:30 Seb wrote: Hi, After upgrading to the lates nvidia packages in sid (currently 295.40-1), KDE suspends desktop effects because they are too slow (I get the notification to that effect in the taskbar). Trying to switch them back on with Alt-Shift-F12 does turn them on, for it is way too slow, and then KDE suspends them again. Is anybody experiencing that? I'm using the Air theme with the OpenGL Compositing type with nvidia latest drivers and I'm not having any issues. That is the Desktop theme, ya... which Window Decorations theme are you using and which video card? I have a GeForce Go 6100. So far I've tried Air and Oxygen on the Desktop, with B II and Oxygen (the light one, not the one labelled by Sean Wilson) for Window Decorations. I have not tried creating a fresh account, yet. If we can pin this down wrt card, themes, or configs we may be able to determine if a bug report is warranted and who should get it. A report at this time would amount to a fairly useless, `it don't work', IMO. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204251759.35692.bms...@shaw.ca
Re: desktop effects suspended with latest nvidia packages
On April 24, 2012 10:28:30 AM Seb wrote: Hi, After upgrading to the lates nvidia packages in sid (currently 295.40-1), KDE suspends desktop effects because they are too slow (I get the notification to that effect in the taskbar). Trying to switch them back on with Alt-Shift-F12 does turn them on, for it is way too slow, and then KDE suspends them again. Is anybody experiencing that? Thanks, yes, see: http://lists.debian.org/debian-kde/2012/04/msg00028.html -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204241437.34403.bms...@shaw.ca
Re: konsole: Inappropriate ioctl for device
On April 22, 2012 05:42:13 PM I wrote: bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Forgot to mention... this is an up to date Unstable amd64 system. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204221749.35930.bms...@shaw.ca
konsole: Inappropriate ioctl for device
Hi, I have a profile set up with the command: su -c /bin/bash and recently (since KDE 4.7, maybe 4.6, or perhaps kernel 3.2.0) it has started spitting out: bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell which causes things like pre-configuring to fail when running apt-get upgrade from the session. It is no big deal ATM (Command: su - works fine) but I'm wondering if it is a KDE/Konsole or kernel thing and if there is a work around. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204221742.14510.bms...@shaw.ca
kwin using 100% CPU
Hi, Kwin has started using 100% CPU when Desktop Effects are enabled right after the non-free Nvidia driver in Unstable upgraded today (from 295.33 to 295.40). Is anyone else seeing that behaviour? Anyone not using the non-free Nvidea driver seeing it? I'm guessing that it is Nvidia related. The last upgrade was a couple weeks ago and this batch also pulled in new: libc, libstdc++, libx11, linux-image, etc. so there is the possibility that Nvidia is not the problem. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204210542.32375.bms...@shaw.ca
Re: kwin using 100% CPU
On April 21, 2012 07:05:56 AM Andreas Cord-Landwehr wrote: On Saturday 21 April 2012 05:42:31 Bruce Sass wrote: Hi, Kwin has started using 100% CPU when Desktop Effects are enabled right after the non-free Nvidia driver in Unstable upgraded today (from 295.33 to 295.40). Is anyone else seeing that behaviour? Anyone not using the non-free Nvidea driver seeing it? I'm guessing that it is Nvidia related. The last upgrade was a couple weeks ago and this batch also pulled in new: libc, libstdc++, libx11, linux-image, etc. so there is the possibility that Nvidia is not the problem. Hi. If you are using Oxygen (i.e., standard setup for workspace appearance), try this as a workaround: System-Settings - Workspace Appearance - (Oxygen) Configure Decoration - DISABLE Enable animations That worked for my office PC with non-free Nvidia drivers. Greetings, Andreas Thanks I'm using B II for Window Decorations and Air for the Desktop Theme. Switching to Oxygen Window Decorations with animation disabled still results in KDE automatically disabling desktop effects. It is the OpenGL compositing selection which is causing kwin to freak out, and since Xrender works fine for the couple management effects I want (the rest is just eye candy I usually disable anyways) I'll live with that for now (or downgrade to 295.33 if the other user on this box complains :) ). - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204211641.25264.bms...@shaw.ca
Re: Task manager thumbnail popup delay (after 4.7 upgrade)
On March 29, 2012 01:50:42 PM Andrej Kacian wrote: On Thu, 29 Mar 2012 13:33:05 +0200 Martin Steigerwald mar...@lichtvoll.de wrote: I think this would be worth a bug report at https://bugs.kde.org, if not already done. I'm kind of hesitant of logging a bug there, since they are already on 4.8 which might have this (and few other nasties which started after upgrade from 4.6) fixed, while debian plods along one minor release behind. :) Ya, it's kind of sad that KDE doesn't fix bugs but instead moves onto a new release... I hope Debian can find enough C++/QT/KDE talent to fix one of their releases up to a higher standard. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203291538.50516.bms...@shaw.ca
Bug#640210: ssh doesn't shutdown after running kmail
When I run kmail from a ssh session I can't log out of the ssh session afterwards. The only symptom in the logs is .xsession-errors having the same SSLv2 messages mentioned above. * When run from the command line (login via SSH, then start kmail) the session hangs when logging out; closing the termial SSH was started on leaves instances of akonadi and nepomuk are left running on the remote host. * When started via a .desktop file (executing: ssh -X kmail, SSH public key on the remote host), sshd leaves a sshd user@notty process and all programs started by kmail's startup running. i.e... [cut'n'paste from top] 12212 12210 bsass 20 0 11880 3988 972 S 0.0 0.8 0:16.35 sshd bsass@notty 12218 1 bsass 20 0 3708 596 364 S 0.0 0.1 0:00.00 dbus-launch --autolaunch 294e50452620d234d6810d269bb91b00 --binary-syntax --close-stderr 12219 1 bsass 20 0 3412 896 556 S 0.0 0.2 0:01.02 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 12225 1 bsass 20 0 33444 4892 3764 S 0.0 1.0 0:00.10 kdeinit4: kdeinit4 Running... 12226 12225 bsass 20 0 44592 8932 7580 S 0.0 1.7 0:00.17 kdeinit4: klauncher [kdeinit] --fd=8 12229 1 bsass 20 0 81352 14m 12m S 0.0 3.0 0:00.68 kdeinit4: kded4 [kdeinit] 12236 1 bsass 20 0 34200 4500 3680 S 0.0 0.9 0:00.82 /usr/bin/akonadi_control 12239 12236 bsass 20 0 160m 7760 5924 S 0.0 1.5 0:00.58 akonadiserver 12242 12239 bsass 20 0 190m 22m 5580 S 0.0 4.6 0:02.87 /usr/sbin/mysqld --defaults- file=/home/bsass/.local/share/akonadi//mysql.conf --datadir=/home/bsass/.local/share/akonadi 12267 12236 bsass 20 0 83740 16m 14m S 0.0 3.3 0:00.45 /usr/bin/akonadi_birthdays_resource -- identifier akonadi_birthdays_resource_0 12268 12236 bsass 20 0 84100 16m 14m S 0.0 3.4 0:00.46 /usr/bin/akonadi_ical_resource -- identifier akonadi_ical_resource_0 12269 12236 bsass 20 0 84100 16m 14m S 0.0 3.4 0:00.46 /usr/bin/akonadi_ical_resource -- identifier akonadi_ical_resource_1 12270 12236 bsass 20 0 81700 16m 14m S 0.0 3.2 0:00.44 /usr/bin/akonadi_maildir_resource -- identifier akonadi_maildir_resource_0 12271 12236 bsass 20 0 82220 16m 14m S 0.0 3.3 0:00.66 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent 12272 12236 bsass 20 0 89824 16m 14m S 0.0 3.2 0:00.48 /usr/bin/akonadi_nepomuk_contact_feeder --identifier akonadi_nepomuk_contact_feeder 12273 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.42 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_0 12274 12236 bsass 20 0 81704 16m 14m S 0.0 3.2 0:00.42 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_10 12275 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.43 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_11 12276 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.42 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_6 12277 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.43 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_7 12278 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.43 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_8 12279 12236 bsass 20 0 81672 16m 14m S 0.0 3.2 0:00.43 /usr/bin/akonadi_vcard_resource -- identifier akonadi_vcard_resource_9 12318 1 bsass 20 0 34708 5640 4720 S 0.0 1.1 0:00.12 /usr/bin/nepomukserver
Re: akonadi
On August 26, 2011 10:30:22 AM Ritesh Raj Sarraf wrote: Are people here using akonadi or any of the tools using the akonadi framework, in their regular workflow? (Email, PIM) Maybe, but not because I want to... at this point I see my options for that box as: check if KDE-4 can be built without akonadi; Oldstable with KDE-3.5.10; Stable + Trinity's KDE-3.5.12; not-KDE Also, the same with Nepomuk. Are people using it or is it just sitting disabled in everyone's config? Disabled as a service in itself, but it still gets started by akonadi. :( AFAICT, ATM: I have no use for the nepomuk/strigi semantic desktop stuff; Akonadi is just simply overkill for me, and it doesn't help that the box I currently use for email can't afford the extra/unnecessary overhead (even if it didn't leave soprano and nepomuk processes lying around after a ssh -X host kmail). - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261528.09688.bms...@shaw.ca
Re: akonadi
On August 26, 2011 03:28:09 PM Bruce Sass wrote: if it didn't leave soprano and nepomuk processes lying around after a hmm, make that, virtuoso and nepomuk... PID PPID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25283 1 user 20 0 45388 5772 5364 S 0.0 1.1 0:00.30 /usr/bin/nepomukserver 25293 1 user 39 19 50004 33m 6272 S 0.0 6.7 1:04.17 /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_X25288.ini +wait -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261543.14835.bms...@shaw.ca
Re: kdebug defaults/build options
On August 26, 2011 03:06:58 PM Carsten Pfeiffer wrote: Am Friday, 19. August 2011 schrieb Bruce Sass: How about using logrotate for .xsession-errors? Sure, it is more of a bandage than anything else though, eh. Frankly, no. IMHO that would be a sensible thing to do. .xsession-errors can grow indefinitely when people are using suspend-to-* and keep their session running until some package update needs a reboot. So there's no difference to the logfiles in /var/log. That doesn't legitimate apps to produce so many log entries, though. OK, bandage was directed at the specific case of using logrotate to deal with overly verbose software. Why is Debian's KDE so verbose? Is it a concious decision by KDE and individual users are expected to use kdebugdialog if they don't like it? Is there a system wide setting so the admin of a multi-user box can set the debug/warn/error messaging behaviour for everyone? Is Debian neglecting to set a flag somewhere which would quiet things down? Should we be talking to the developers of individual apps because it is not really a KDE problem? I have no idea what Debian's policy is, so I can only pass my very own opinion. Apps and libs should be as quiet as possible by default. They should only log assertion failures, i.e. critical problems. It should be possible to launch an app in a terminal (in the background) and keep working in the same terminal. Everything other than critical problems should be made available on demand, e.g. through kdebugdialog. Thanks! -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261546.29761.bms...@shaw.ca
Bug#638621: forget that patch...
tags 638621 - patch stop I found this issue at bugs.kde.org and it turns out there is more wrong here than just the escaped single quotes. See: https://bugs.kde.org/show_bug.cgi?id=265730 If the 4.6.5 packages are going to have a life in Debian I suggest backporting at least the fix to get rid of the error messages as was applied to 4.7. - Bruce -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108221538.55064.bms...@shaw.ca
Bug#638621: error parsing /usr/share/kde4/apps/kate/externaltools
Package: kate Version: 4:4.6.5-1 Severity: normal Tags: patch While running kate from the command line, with all messages disabled via kdebugdialog, I noticed this error repeated a few times: KConfigIni: In file /usr/share/kde4/apps/kate/externaltools, line 8: Invalid escape sequence \'. Removing the escaped single quotes in the file and line indicated in the error message fixes the problem. The attached diff -u output changes the text from: The file \'%filename\' is not under revision control. to The file: %filename, is not under revision control. An escaped double quote (\) is also an invalid escape sequence. The other problem, that of the message being spit out in spit of that behaviour being disabled, is probably an upstream issue with some other KDE component. - Bruce -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kate depends on: ii kdebase-runtime 4:4.6.5-1 runtime components from the offici ii libc6 2.13-16Embedded GNU C Library: Shared lib ii libkde3support4 4:4.6.5-2 KDE 3 Support Library for the KDE ii libkdecore5 4:4.6.5-2 KDE Platform Core Library ii libkdeui5 4:4.6.5-2 KDE Platform User Interface Librar ii libkfile4 4:4.6.5-2 File Selection Dialog Library for ii libkio5 4:4.6.5-2 Network-enabled File Management Li ii libknewstuff2-4 4:4.6.5-2 Get Hot New Stuff v2 Library for ii libknewstuff3-4 4:4.6.5-2 Get Hot New Stuff v3 Library for ii libkparts44:4.6.5-2 Framework for the KDE Platform Gra ii libktexteditor4 4:4.6.5-2 KTextEditor interfaces for the KDE ii libplasma34:4.6.5-2 Plasma Library for the KDE Platfor ii libqt4-dbus 4:4.7.3-7 Qt 4 D-Bus module ii libqt4-qt3support 4:4.7.3-7 Qt 3 compatibility library for Qt ii libqt4-sql4:4.7.3-7 Qt 4 SQL module ii libqt4-xml4:4.7.3-7 Qt 4 XML module ii libqtcore44:4.7.3-7 Qt 4 core module ii libqtgui4 4:4.7.3-7 Qt 4 GUI module ii libstdc++64.6.1-6GNU Standard C++ Library v3 kate recommends no packages. Versions of packages kate suggests: ii aspell 0.60.7~20110707-1 GNU Aspell spell-checker ii ispell 3.3.02-5 International Ispell (an interacti ii khelpcenter4 4:4.6.5-1 help center ii konsole4:4.6.5-1 X terminal emulator -- no debconf information -- debsums errors found: debsums: changed file /usr/share/kde4/apps/kate/externaltools (from kate package) --- externaltools.orig 2011-01-19 15:07:44.0 -0700 +++ externaltools 2011-08-19 22:27:16.0 -0600 @@ -5,7 +5,7 @@ [externaltool_CompareCurrentDocumenttoRCS] acname=externaltool_CompareCurrentDocumenttoRCS cmdname=document-diff -command=if [ -z %directory ] then kdialog --title Error --msgbox The document has never been saved and thus cannot be compared to RCS.; fi\ncd %directory\nif [ -d .svn ] grep %filename .svn/entries 21 /dev/null ; then\n svn diff %filename|kompare -o -\nelif [ -d CVS ] grep %filename CVS/Entries 21 /dev/null ; then\n cvs diff -ub %filename|kompare -o -\nelif [ -d .git ] echo $(git ls-files) | grep %filename 21 /dev/null ; then\n git diff %filename|kompare -o -\nelse\n kdialog --title Error --msgbox The file \'%filename\' is not under revision control.\nfi\n +command=if [ -z %directory ] then kdialog --title Error --msgbox The document has never been saved and thus cannot be compared to RCS.; fi\ncd %directory\nif [ -d .svn ] grep %filename .svn/entries 21 /dev/null ; then\n svn diff %filename|kompare -o -\nelif [ -d CVS ] grep %filename CVS/Entries 21 /dev/null ; then\n cvs diff -ub %filename|kompare -o -\nelif [ -d .git ] echo $(git ls-files) | grep %filename 21 /dev/null ; then\n git diff %filename|kompare -o -\nelse\n kdialog --title Error --msgbox The file: %filename, is not under revision control.\nfi\n executable=kompare icon=kompare mimetypes=
Re: kdebug defaults/build options
On August 20, 2011 01:33:42 AM Diggory Hardy wrote: But you're saying you can't actually use long KDE sessions? IIRC, it was the 4.5 and/or the early 4.6.x's which filled up .xsession-errors to the point of KDE shutting stuff down because /home was running out of room every 2-3 days--the box sees kiosk-like use for email, printing, burning, and long running processes like bittorrent, it only gets a restart if the power goes down or a core lib gets upgraded. Prior to this recent fiddling it had been frozen wrt to upgrades at whatever ws in unstable when KDE-4.4 arrived, and running a local build of kde-3.5.10+qt-copy pretty much non-stop for over 230 days. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108200337.49388.bms...@shaw.ca
Re: kdebug defaults/build options
On August 19, 2011 02:28:39 AM Diggory Hardy wrote: [sorry for the late response] If the only symptom was the huge log file then it could be argued that: had debug messages been disabled, there wouldn't have been a problem... :D That makes sense, but I was just joking around... it is much better, imo, to get rid of the source of the messages (fix the buggy code or turn off messages by default) where feasible than toss them into the bit bucket via redirection to /dev/null or logrotate. (a) I disabled everything in kdebugdialog and truncated .xsession-errors to 100kB a few days ago, and now it's 16MB so still some traffic (over half from kio_xxx). That size of log file isn't an issue (for me at least), though most of the entries appear pretty uninteresting (e.g. HTTP requests). That's good to hear. The box I was having .xsession-errors trouble with has been pretty well behaved during the current 13 day KDE session. The log file is only 1.2M and a large chunk of it is: QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method true (which appears to be a consequence of SSHing to the box and running kmail). While that is much better than having to restart the session every couple of days, one can't read too much into it thought since during the last 13 days the only KDE apps started have been 4.6 Konqueror and Kate locally 4-5 times each, K3b from KDE 3.5.10 (local build of 3.5.10+qt-copy) a few times, and Kmail remotely about a half dozen times. A more useful number may be 116k in 4hrs for the current pure Unstable KDE session on this box, comprised mostly of one-time startup messages. (b) many debug options are active by default, so new users are going to keep coming across nuisance messages (either in terms of .xsession-errors size or output on command-line when running things like kwrite). So, turning off everything in kdebugdialog didn't silence kwrite on the comand line? It doesn't for Kate, but all messages appear to be a result of actual bugs. Any more thoughts on how much debug output is reasonable? Obviously it makes some sense for errors and warnings to be reported, but a lot of the output is only trace type debug output which is often only useful to people debugging or optimising applications so IMO shouldn't be enabled by default (although feel free to disagree if you have a use for such output). Of my current 16 line log file, 2600 lines are matched by 'egrep -i warn' and another 800 by 'egrep -i error'. Turn off everything. :) Where does that leave us? Put up with it as is? Rebuild without debugging output enabled? Just disable all entries in kdebugdialog by default (this solves my issues anyway)? Ask KDE devs what their intentions are (maybe there are some KDE devs on this list)? Debian should default to disabling all messages via kdebugdialog. To accommodate any desire for packages to have different behaviour depending on a Unstable, Testing, or a Stable based box, it may be beneficial to adjust the kdebugdialog settings at install-time. Simply putting DisableAll=true at the start of /usr/share/kde4/config/kdebugrc, or not, depending on the contents of /etc/debian_version and admin input (requiring the use of dpkg- reconfigure if they ever want to change the default) is probably good enough. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108192116.47955.bms...@shaw.ca
Re: kdebug defaults/build options
On August 13, 2011 04:01:54 PM Xavier Brochard wrote: Bruce Sass wrote: On August 10, 2011 02:13:49 PM Xavier Brochard wrote: Bruce Sass wrote: 2. At times I've been annoyed by the number of spam messages kwrite/kate leave on the console when run that way. Looking into it, these messages are kDebug outputs. The kde techbase suggests [1] this output is intended to be disabled in releases. Would you have any objections to doing this in the future, with kwrite at least? There's not many programs I've had problems with, but I do wince when running kwrite from a console every so often. [1]: http://techbase.kde.org/Development/FAQs/Debugging_FAQ#Is_there_a_preferred _way_to_print_debug_output_on_stderr.3F My work-around to this problem is to tack /dev/null onto the end of all cmdline issued KDE commands... An easier approach is to simply run kdebugdialog then select/deselect the apps that you want to not send debug output If I ever run Stable's KDE I probably will--assuming Debian hasn't already-- No, but I don't know what is the good choice: On one Debian squeeze install, I've got a .xsession-errors which grows very fast (a few hours) to 320 Go. It was on a multi users system and was very problematic. It was purely a kde problem (with Nepomuk/Akonadi), which I solved. But, if debug output were disable, it might be possible that I would never know about it. [sorry for the late response] If the only symptom was the huge log file then it could be argued that: had debug messages been disabled, there wouldn't have been a problem... :D I'm assuming that this [disabling debug messages] would be a change in the default kdebugdialog settings, and as such would be reversible by the admin/user. So, it would still be possible to discover the problem you ran into although there may be a bit of a delay until kdebugdialog is discovered and adjusted. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108181626.47946.bms...@shaw.ca
Re: kdebug defaults/build options
On August 10, 2011 02:13:49 PM Xavier Brochard wrote: Bruce Sass wrote: 2. At times I've been annoyed by the number of spam messages kwrite/kate leave on the console when run that way. Looking into it, these messages are kDebug outputs. The kde techbase suggests [1] this output is intended to be disabled in releases. Would you have any objections to doing this in the future, with kwrite at least? There's not many programs I've had problems with, but I do wince when running kwrite from a console every so often. [1]: http://techbase.kde.org/Development/FAQs/Debugging_FAQ#Is_there_a_preferred _way_to_print_debug_output_on_stderr.3F My work-around to this problem is to tack /dev/null onto the end of all cmdline issued KDE commands... An easier approach is to simply run kdebugdialog then select/deselect the apps that you want to not send debug output If I ever run Stable's KDE I probably will--assuming Debian hasn't already-- with Unstable though I prefer keeping the system as close to as-installed as is reasonably possible because I'm working under the (perhaps misguided shrug) assumption that it is the default configuration which is most important to Debian, and fiddling with lower level stuff like that could interfere with its characterization (finding, reporting, and verifying bugs and quirks). Another way to look at this annoyance is via the learning curves. Currently, everyone who runs Debian's KDE programs from the cmdline will run into the too much verbosity problem and consequently the kdebugdialog will be on their Debian-KDE learning curve; If the messages were of by default the only ones who would have need for kdebugdialog in their learning curve would be those actually interested in debugging Debian's KDE. IOW, spewing mostly useless messages as a default the behaviour increases the length and steepness of a regular user's Debian-KDE learning curve, when it should really be the user who wants to non-usual stuff (like debugging) who's curve should be longer and steeper. - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108121758.54912.bms...@shaw.ca
Re: kdebug defaults/build options
On August 9, 2011 10:04:41 AM Diggory Hardy wrote: Nice to see someone agrees with me but I was kinda expecting some sort of response from one of the package maintainers. Is it best to file a bug or just wait till this catches someone else's attention? If you want to persue it, file a wishlist severity bug report against the kde pseudo-package, or maybe the individual apps you commonly run from the command line. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108091544.49227.bms...@shaw.ca
Re: kdebug defaults/build options
On August 4, 2011 12:37:37 PM Diggory Hardy wrote: Hi all Regarding default debug output in kde on debian: 1. A while ago I reported this: https://bugs.kde.org/show_bug.cgi?id=269882 Perhaps disabling logging kget's debug messages makes sense? Or perhaps this is occasionally useful less often a problem? I don't have a strong opinion on this really. 2. At times I've been annoyed by the number of *spam* messages kwrite/kate leave on the console when run that way. Looking into it, these messages are kDebug outputs. The kde techbase suggests [1] this output is intended to be disabled in releases. Would you have any objections to doing this in the future, with kwrite at least? There's not many programs I've had problems with, but I do wince when running kwrite from a console every so often. [1]: http://techbase.kde.org/Development/FAQs/Debugging_FAQ#Is_there_a_preferred _way_to_print_debug_output_on_stderr.3F My work-around to this problem is to tack /dev/null onto the end of all cmdline issued KDE commands... ...but, ya, it would be real nice if that wasn't necessary and could open the door to wider use of Debian's KDE. e.g.: I'd love to run a KDE based system off a USB flash drive but all those (typically useless during normal operation*) messages will drastically shorten the flash drive's life--I expect the same would be true of any device using solid state HDDs. I have also run into apps dying when /home gets flled up by .xsession-errors, this is more of a PITA than anything else but lowering the bar a bit by reducing the HDD overhead--and consequently improving startup times--will allow KDE to run better on slower systems or those with limited HDD space (or with /home as a network FS!) than it does currently. If Debian rebuilt packages for each archive I'd say an argument could be made to leave it as it is for Unstable, reduce the output to only errors for Testing, and turn them all off for Stable--but since packages migrate into the archives (prehaps soon even those in Experimental will start migrating) it may be best to turn off all messages from the start and educate users on the use of kdebugdialog when problems arise. - Bruce * Here is a short extract from the end of my current .xsesion-errors... QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active plasma-desktop(2975)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application plasma-desktop(2975)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application plasma-desktop(2975)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application QSslSocket: cannot resolve SSLv2_client_method QSslSocket: cannot resolve SSLv2_server_method QGraphicsLinearLayout::removeAt: invalid index 1 QGraphicsLinearLayout::removeAt: invalid index 1 true ... if one knew the messages were the result of turning on output for a specific app or subsystem they may be useful in tracking down a problem, but without that context they appear to be just noise. This may be a case where less output could improve debuggabilty (sp. :) ). -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108041817.39854.bms...@shaw.ca
`updates available' popup
Hi, Does anyone know where the info popup telling me that I may want to upgrade my system because there are newer packages available is coming from (what package it resides in)? - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107101602.43976.bms...@shaw.ca
krfb and krdc
Hi, With KDE 3.5 (and earlier, never tried with KDE 4) I told Krfb to allow uninvited connections, closed the Krfb window, and was then able to connect via Krdc as long as that user was running a KDE session--through reboots and regardless of whether Krfb was taking up a taskbar slot or not. After upgrading to KDE 4.6.x (from unstable) it appears that I can't connect unless the Krfb app is running. Is there any way to get the old behaviour back? - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107080328.32481.bms...@shaw.ca
Bug#589683: reportbug: spews useless information messages when spawing editor
retitle 589683 Kate needs a quiet option stop Hi, Fair enough... I'm so use to verbose KDE apps that I automatically put them in the background and redirect output when I start one from a command line--of course everyone else should do the same. :D I tried a couple other visual editors, xjed and xemacs, neither of them sent any output to the X-term. So, indeed, this is a problem with Kate which makes it rather less than suitable as a system's VISUAL editor. Note: although I use a local build of KDE3 (KDE4 eats up too many resources on this older box), and the Kate that comes with KDE4 is somewhat less verbose than the one from KDE3, it still spews out a lot of generally useless messages and doesn't appear to have a quiet option. - Bruce On July 19, 2010 11:25:19 pm Sandro Tosi wrote: reassign 589683 kate thanks Hello Bruce, this seems to me a bug (even if at wishlist severity) in kate: if you want them to stop print those lengthy messages, ask them :) I can't redirect all output from text editor to dev/null or so: there might be cases when having their output on screen is useful, without going to look in another place (or in no place at all, as in /d/null), but I understand the startup of kate is really verbose. I'm assigning this bug to the kate package. Regards, Sandro On Tue, Jul 20, 2010 at 00:42, Bruce Sass bms...@shaw.ca wrote: Package: reportbug Version: 4.12.4 Severity: wishlist It would be really nice if reportbug sent the information messages generated by Kate (KDE text editor) to /dev/null or a log file instead of the screen when not in debug/verbose mode. Here is a transcript of a session so you can see just how ugly the current behaviour is: bs...@onegee:~$ reportbug chkrootkit *** Welcome to reportbug. Use ? for help at prompts. *** Detected character set: us-ascii Please change your locale if this is incorrect. Using 'Bruce Sass bms...@shaw.ca' as your from address. Getting status for chkrootkit... Verifying package integrity... Checking for newer versions at packages.debian.org, incoming.debian.org and http://ftp-master.debian.org/new.html Will send report to Debian (per lsb_release). Querying Debian BTS for reports on chkrootkit (source)... 9 bug reports found: Outstanding bugs -- Important bugs; Patch Available (1 bug) 1) #580491 chkrootkit: 1)with nfs mounted the silent don't work 2)can't exclude legacy sniffer (dhcpd, snort, ntop e Outstanding bugs -- Normal bugs; Unclassified (7 bugs) 2) #535942 chkrootkit: fix for chkproc race 3) #548582 chkrootkit: Chkrootkit isn't quiet with -q and excluded suspicious files 4) #564147 chkrootkit: false positive: scalper rootkit and ser2net debian package both listen on port 2001 by defaul 5) #566687 chkrootkit: False positive for SMTPs (Courier, Postfix) 6) #576470 chkrootkit: false positives for libsmlnj-smlnj 7) #586897 Meaningless error message when option -e is used without argument 8) #588121 chkrootkit: false positive bitlbee, /usr/bin/find 'head' terminated signal 13 Forwarded bugs -- Normal bugs (1 bug) 9) #488558 False positive for vdr (1-9/9) Is the bug you found listed above [y|N|b|m|r|q|s|f|?]? Maintainer for chkrootkit is 'Giuseppe Iuculano iucul...@debian.org'. Looking up dependencies of chkrootkit... Getting changed configuration files... *** The following debconf settings were detected: * chkrootkit/run_daily: true * chkrootkit/run_daily_opts: -q -n * chkrootkit/diff_mode: false Include these settings in your report [Y|n|q|?]? Please briefly describe your problem (max. 100 characters allowed; you can elaborate in a moment). This will be the bug email subject, so write a concise summary of what is wrong with the package, for example, fails to send email or does not start with -q option specified (type Ctrl+c to exit). $egrep used unset Rewriting subject to 'chkrootkit: $egrep used unset' Enter any additional addresses this report should be sent to; press ENTER after each address. Press ENTER on a blank line to continue. How would you rate the severity of this problem or report? 1 critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should
Bug#397073: something deeper going on
Hi, .bashrc is read as expected from the documented behaviour when I start Konsole outside of KDE (specifically, UDE) then start a GIT session. Compare this diff with the one attached to a previous message... - --- env.cmdline 2006-11-14 15:19:42.985477511 -0700 +++ env.session 2006-11-14 15:19:09.568135878 -0700 @@ -2,7 +2,7 @@ MINICOM=-c on GIT_SHELL=/bin/bash LANGUAGE=en_CA:en_US:en_GB:en -KONSOLE_DCOP_SESSION=DCOPRef(konsole-16463,session-2) +KONSOLE_DCOP_SESSION=DCOPRef(konsole-16463,session-3) USER=bsass MAIL=/var/mail/bsass GIT_EDITOR=jed @@ -14,6 +14,7 @@ COLORTERM= LOGNAME=bsass HOSTDISPLAY=onegee:1.0 +_=/usr/bin/gitfm WINDOWID=16777223 COLUMNS=88 GIT_BROWSER=sensible-browser @@ -28,7 +29,7 @@ LESSCLOSE=/usr/bin/lesspipe %s %s UDEdir=/usr/share/ude/ GIT_PAGER=less -PWD=/home/bsass +PWD=/home/bsass/tmpfs PRINTER=lj5n LINES=49 GIT_RMAIL=mail - Something is broken in KDE which causes Konsole to misbehave, but I don't know where or how to track it down... (useful :-) suggestions appreciated. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 03:11, Sune Vuorela wrote: On Monday 13 November 2006 05:33, Bruce Sass wrote: Is it something for konsole to run _instead_ of bash? or? hmmm, ya, sure... hmm... so you expect konsole to read conffiles for bash when it is actually running another shell/program. That makes little sense to me---Konsole is a fancy x-terminal and should be doing the equivalent of bash -c someprogram with session programs. It is not konsole that reads your .bashrc, it is bash that reads it. Have another look at the output from env I sent, it contains: SHELL=/bin/bash So, ~/.bashrc should have been read, and it used to work correctly... If I remember correct, kde sources entire .kde/env/* when it boots, so if you adds a file containing #! /bin/bash if [ -e ~/.bashrc ] then .bashrc fi you will have your environment vars set in your .bashrc in entire kde. Alternatively just set the ones you like GITPAGER=foo SOMEVAR=bar and add it to a file in .kde/env/ (If you don't have .kde/env/, you can just create it) ...without polluting the environment for all of KDE, or needing to configure the same thing in multiple places. Your solution is also not good if one wanted a different environment for sh, bash, etc., where the same variable may need to take on different values. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 16:13, Sune Vuorela wrote: On Monday 13 November 2006 23:38, Bruce Sass wrote: You seem to be doing a lot of guessing... :-/ which is why I am sending a copy to your Application Manager. Thank you. You are most welcome to show my application manager that I do a hard work on the kde bugs. Or how you tackle reports about programs for which you have limited knowledge---sessions are a key feature of konsole, they get their own tab in the config dialog, yet you were unaware of them and blindly went ahead tagging the report as unreproducible. Kurt, please have a look at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073 If you read the bash manpage, it says that bash only read .bashrc when invoked interactively. Since when is a Konsole session not interactive? bash is not interactive when not connected to a terminal. This is bash behaviour, not konsole behaviour. From the bash manpage: An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. and this is how bash is supposed to work - so this is not a bug neither in konsole or in bash. You are wrong. Please point me where. Konsole should behave like any other x-terminal (which are interactive), sessions are like bash -c somecommand (you have admitted as much)... both point to .bashrc being read. .bashrc is not some random configuration file, and a program should not be required to read a shell's profile or runtime configuration files! .bashrc is just a random canfiguration file. Just try ask any zsh user. What does zsh have to do with Konsole putting SHELL=/bin/bash in the environment? I think you should remove the wontfix tags and get some help from a knowledgeable DD, or send it upstream. I actually have discussed this with several knowledgeable DDs and they agree with me. Then you should send it upstream because sessions are crippled... it should not matter if one starts a shell session then types in a command vs. uses a pre-defined session to start the command. Please stop being abusive. How have I been abusive? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 17:27, Clint Adams wrote: An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. The underlying bug is either that you want konsole to exec 'bash -i -c whatever' or that you expect bash to behave differently can it does. That is not correct; Konsole is for interactive use so -i should not be necessary. Furthermore... help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. However, that is not what is happening as the attached diff of GIT started from a Konsole commandline and as a KonsoleApplication shows. help:/konsole/menubar.html has a note which says... See the file README.linux.console in the Konsole source package for detailed information on how the Linux® console differs from a typical UNIX® console. ...and help:/konsole/introduction.html contains... Konsole is what is known as an X terminal emulator, often referred to as a terminal or a shell. It gives you the equivalent of an old-fashioned text screen on your desktop, but one which can easily share the screen with your graphical applications. ...yet there is nothing in README.linux.console which indicates such a significant departure from standard x-terminal behaviour, and the README simply states: Konsole is an X terminal emulation. Clearly, it would be a bug if bash was used on an old-fashioned text screen and it didn't read .bashrc... so why is it OK for Konsole to not make sure bash is started in a like manner? - Bruce --- env.cmdline 2006-11-13 17:43:57.691322496 -0700 +++ env.session 2006-11-13 17:43:28.446396194 -0700 @@ -1,22 +1,18 @@ -LESSOPEN=| /usr/bin/lesspipe %s KDE_FULL_SESSION=true -MINICOM=-c on GS_LIB=/home/bsass/.fonts DM_CONTROL=/var/run/xdmctl GIT_SHELL=/bin/bash LANGUAGE=en_CA:en_US:en_GB:en -KONSOLE_DCOP_SESSION=DCOPRef(konsole-28686,session-1) +KONSOLE_DCOP_SESSION=DCOPRef(konsole-28686,session-2) USER=bsass -GIT_EDITOR=jed +GIT_EDITOR=sensible-editor SSH_AGENT_PID=1821 SHLVL=1 HOME=/home/bsass XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched,rsvd,method=classic DESKTOP_SESSION=kde -PAGER=less GTK_RC_FILES=/etc/gtk/gtkrc:/home/bsass/.gtkrc:/home/bsass/.kde/share/config/gtkrc DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-K3fvdVLN8B,guid=673558459f7175b0e4354a51639d5400 -VISUAL=kate COLORTERM= LOGNAME=bsass _=/usr/bin/gitfm @@ -30,15 +26,11 @@ XCURSOR_THEME=Chameleon-DarkSkyBlue-Regular KONSOLE_DCOP=DCOPRef(konsole-28686,konsole) DISPLAY=:0.0 -LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35: SSH_AUTH_SOCK=/tmp/ssh-jsYQNr1776/agent.1776 GIT_VMSTAT=free SHELL=/bin/bash -LESSCLOSE=/usr/bin/lesspipe %s %s KDE_MULTIHEAD=false -GIT_PAGER=less -PWD=/home/bsass -PRINTER=lj5n +GIT_PAGER=sensible-pager +PWD=/usr/src/kdebase-3.5.5a.dfsg.1/konsole LINES=49 GIT_RMAIL=mail -EDITOR=jed
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 17:35, Sune Vuorela wrote: On Tuesday 14 November 2006 00:55, Bruce Sass wrote: Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. Maybe. xterm behaves same way. [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass .bashrc ###press alt-f2 - type env kdeenv [EMAIL PROTECTED]:~$ grep TESTVAR kdeenv ###press alt-f2 - type xterm -e env xtermenv [EMAIL PROTECTED]:~$ grep TESTVAR xtermenv [EMAIL PROTECTED]:~$ grep SHELL xtermenv SHELL=/bin/bash XTERM_SHELL=/bin/bash [EMAIL PROTECTED]:~$ so when having xterm invoke another program instead of bash also not read .bashrc - I find it correct for konsole to behave like xterm here. Good point, but I am not doing `konsole -e gitfm' and that is not how sessions are supposed to work according to the Konsole docs. ... this says that .bashrc is _not_ read when doing bash -c It turns out this is not relevent because sessions are supposed to work as if you opened a new shell and were going to issue that command. That is clearly not what is happenning (see my response to Clint's message... for that reason alone this report should be forwarded upstream so they can determine if Konsole sessions are broken or behaviour has changed and the docs need to be updated. I have been using Konsole sessions for years and the lack of behaviour I am describing is recent. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 18:02, Sune Vuorela wrote: On Tuesday 14 November 2006 01:35, Sune Vuorela wrote: [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass .bashrc woops. Typo here - it should have been echo export TESTVAR=brucesass shrug So, does that change the outcome? I don't see it as relevent since Konsole is an x-terminal and I'm not doing konsole -e ... which would have been the equivalent of your experiment. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 18:34, you wrote: That is not correct; Konsole is for interactive use so -i should not be necessary. Furthermore... You are misunderstanding the bash man page. The '-c' makes bash non-interactive. I understand that, it turns out I was wrong in assuming a Konsole session is like a bash -c ..., it is supposed to be like starting a shell then typing a command---which results in an interactive session. So, ya, a red herring but it doesn't change the buggy behaviour I am seeing. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 20:00, Sune Vuorela wrote: On Tuesday 14 November 2006 02:10, Bruce Sass wrote: help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. Maybe this line has been thru the sales department, but I can also open new shells that don't read my .bashrc The line maybe could say Enter a command as you normally would if you opened a new shell and were to issue that command. The command will be invoked with sh -c /command/ or maybe: Enter a command as you normally would in a shell. This command will be executed instead of your shell But that is not what it says, maybe you should stop guessing and making things up. Why not take the docs for what they say, or ask upstream. I have looked more into it. I cannot find any evidence that konsole actually invokes bash -c yourcommand, but instead I seem to suggest ... Yes, bash -c ... was an error on my part, and I do have a .profile with the relevent bits just in case Konsole was lying by using sh instead of the indicated SHELL=/bin/bash... as it turns out that is not relevent to this bug. Debian's Konsole behaviour differs from both documented and past behaviour in a way that cripples the use of sessions. Either Debian's Konsole is broken, Konsole is broken, or the behaviour changed and the documentation didn't... any of those situations warrants a bug report and no amount of maybes, guesses, or attempts to remember on your part is going to change that. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
Hi, A konsole shell is fine, but session programs are not. I have a session which starts GNU Interactive Tools (apt-get install git) using the command gitfm. The output of env from within that session is... - KDE_FULL_SESSION=true GS_LIB=/home/bsass/.fonts DM_CONTROL=/var/run/xdmctl GIT_SHELL=/bin/bash LANGUAGE=en_CA:en_US:en_GB:en KONSOLE_DCOP_SESSION=DCOPRef(konsole-22261,session-3) USER=bsass GIT_EDITOR=sensible-editor SSH_AGENT_PID=1820 SHLVL=1 HOME=/home/bsass XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched,rsvd,method=classic DESKTOP_SESSION=kde GTK_RC_FILES=/etc/gtk/gtkrc:/home/bsass/.gtkrc:/home/bsass/.kde/share/config/gtkrc DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-r6t9xCKC71,guid=444e5045b49d499aec2c0e679a125000 COLORTERM= LOGNAME=bsass _=/usr/bin/gitfm WINDOWID=48234503 COLUMNS=88 GIT_BROWSER=sensible-browser TERM=xterm GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/bsass/.gtkrc-2.0:/home/bsass/.kde/share/config/gtkrc-2.0 SESSION_MANAGER=local/onegee:/tmp/.ICE-unix/1876 PATH=/home/bsass/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/bin XCURSOR_THEME=Chameleon-DarkSkyBlue-Regular KONSOLE_DCOP=DCOPRef(konsole-22261,konsole) DISPLAY=:0.0 SSH_AUTH_SOCK=/tmp/ssh-EFGVug1775/agent.1775 GIT_VMSTAT=free SHELL=/bin/bash KDE_MULTIHEAD=false GIT_PAGER=sensible-pager PWD=/home/bsass LINES=49 GIT_RMAIL=mail Press almost any key to continue - ...but GIT_PAGER should be =less and there should be the results of eval `lesspipe` (LESSOPEN=| /usr/bin/lesspipe %s and LESSCLOSE=/usr/bin/lesspipe %s %s) in the environment. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
hmm.. What is a session program? A program started via the Session menu, maybe I should be calling them Konsole Applications. How do I set up a session program? - start konsole - select Configure Konsole from the Settings menu - select the Session tab - put a descriptive name in the Name field - put a text mode command in the Execute field - put a path to cd to in the Directory field - choose an appropriate Icon, Schema, etc. - hit the Save Session button You'll end up with a .desktop file in ~/.kde/share/apps/konsole, e.g: --- ssh to bms.desktop --- [Desktop Entry] Cwd= Exec=ssh -X bms Font= Icon=konsole KeyTab= Name=ssh to bms Schema= Term=xterm Type=KonsoleApplication -- which shows up in the Session menu as New ssh to bms and starts a SSH login with X-forwarding on the host named bms. Is it something for konsole to run _instead_ of bash? or? hmmm, ya, sure... - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
Package: konsole Version: 4:3.5.5a.dfsg.1-1 Severity: important When starting session programs ~/.bashrc is not being read, which results in some programs not operating as configured. For example... My ~/.bashrc contains: eval `lesspipe` export GIT_PAGER=less which tells gitfm to use less as its pager and less to automatically uncompress files for viewing. However, because .bashrc is not read the ^xv key command results in a may be a binary file. See it anyway? message and forces me to type (and often escape) a zless ... command. This is a minor annoyance with short filenames, but with long names it requires cutting back to one pane to see the entire name, and with very long names it requires that plus widening the Konsole window to full width and greatly reducing the font size before the entire name is visible for cut'n'pasting onto the command line... effectively rendering GIT's ^xv command useless. This is a regression from the v3.4.x behaviour (afaict), and I think it is important because it can have a major affect on the useability of programs run in Konsole. - Bruce -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-onegee Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages konsole depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-3 core libraries and binaries for al ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libgcc11:4.1.1-19GCC support library ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension konsole recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374939: the related wishlist for cabextract
The cabextract wishlist bug related to this #377868. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377868 - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374939: kdelibs-data: mimelnk/application/x-mscabinet.desktop file needed
Package: kdelibs-data Version: 4:3.5.3-1 Severity: wishlist Tags: patch Cabextract is getting Konqueror servicemenu entries and needs a mimetype definition for Microsoft Cabinet archives[1]. This appears to be the minimum required: --- /usr/share/mimelnk/application/x-mscabinet.desktop --- [Desktop Entry] Comment=Microsoft Cabinet Archive Hidden=false MimeType=application/x-mscabinet Patterns=*.cab;*.CAB Type=MimeType --- Please advise if I've missed anything. - Bruce [1] discussion with cabextract Maintainer - Date: Wed, 21 Jun 2006 10:30:07 -0400 From: Eric Sharkey [EMAIL PROTECTED] To: Bruce Sass [EMAIL PROTECTED] Subject: Re: cabextract enhances KDE? The first file, */share/apps/konqueror/servicemenus/cabextract.desktop, (* = $HOME/.kde | /usr) defines functions which appear in the Actions submenu of the context menu. Ok. I can add that to the cabextract package. $ dpkg -S x-msdos-program.desktop kdelibs-data: /usr/share/mimelnk/application/x-msdos-program.desktop Should kdelibs-data also provide x-mscabinet.desktop? Yes, that should not be in the cabextract package. You want the mime type to be defined even if cabextract is not installed, and the action to be available only if it is, so the first file should be included in the cabextract package, and the second packaged with kdelibs-data. ... Eric - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DRM weirdness?
Hi, I've never been able to get DRM working when doing startx /usr/bin/startkde ..., the Xorg.1.log file always points to DRIScreenInit (in the i810 driver) failing because of drmSetBusid ... permission denied. I don't know where drmSetBusid lives (not the kernel or i810 driver), but permissions look fine, afaict (not entirely sure if I know what to look for though): However, it works if I stop the boot-launched KDM first. Conversely, sessions started from KDM don't have hardware 3-D if startx was run first. Is that normal? Is it an X-thing (i.e., only one server is allowed to do DRI at a time) or a KDE-thing (e.g., hogging the interface)? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 1024x768 resolution assistance
On Sat, 28 Jan 2006, D. Michael 'Silvan' McIntyre wrote: On Saturday 28 January 2006 5:25 pm, Hendrik Sattler wrote: I strongly object to that. The debconf actually only cover the basics, even my wacom tablet needs manual editing (which is neither unusual nor a weird resolution). Additional, two monitors might need that too. Second that. I had the same problems as the OP here after switching to a new LCD monitor. It refused to do anything higher than 640x480, which looked absolutely dismal on a 19 screen hard wired for 1280x1024. I finally worked it out by copying bits of a KNOPPIX-generated conf file into my debconf-generated one. The Debian auto config bits always did the wrong thing no matter how many different front door tactics I tried. If all else fails, hack the thing and get it over with. Of course. However, a monitor that only does 1280x1024, graphics tablets, and dual monitors all qualify as unusual or weird for a typical desktop, imo. Keep in mind that you are responding to someone moving from Mandrake to Debian/unstable who thinks that a new graphics card is required because Debian doesn't autoconfigure as well as Mandrake... they are probably already pushing their envelope (a good thing I woudn't want to discourage), how helpful is `edit the configs' gonna be if it is likely they don't even know what the front door or all else is. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kded from kdelibs 3.5.1 crashing
Hmmm, It appears the latest kdelibs packages (v3.5.1) doesn't like the KDE currently in the archive (v3.5.0). kded keeps crashing with signal 6. Unstable users not wanting to be bothered by a constant stream of drkonqi windows may want to put the kdelibs packages[1] on hold until more of v3.5.1 enters the archive. - Bruce [1] kdelibs-bin kdelibs-data kdelibs4-dev kdelibs4-doc kdelibs4c2a kdelibs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 1024x768 resolution assistance
On Fri, 27 Jan 2006, Richard Wegner wrote: Hi there, I recently had Debian 3.1 unstable version on my system, but my X windows kept on going bad. I did some diagnostics and found out that my video card was one of those that it didn't really like that much. What I am wondering is for some suggestions for a video card that does work quite well with Debian 3.1 unstable with high resolutions. With the current one I have, it currently goes only 800x600 on my resolution no matter what I try and do. Actually stating what you tried, instead of leaving it to our imaginations, would have been good. Have you looked in /var/log/Xorg... which will tell you if the higher resolutions you are after are failing or simply not being tried (a likely scenario, as pointed out in another message). I had to revert to Mandrake 10.1 Community Edition for the time being till I can find a good enough video card that will work. Something working with one flavour of Linux but not another is most likely a configuration issue. Look up your monitor's specs, or print out the X configs used by Mandrake, then: # dpkg-reconfigure xserver-xorg For a typical desktop box, it shouldn't be necessary to manually edit X's configs unless you are doing something unusual or want to support weird resolutions. Generally, manually tweaking a config file which debconf scripts also have their fingers into can be tricky - especially when running unstable because those are the kind of package UI issues which get worked out in unstable. hth - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window mini-icon (kwin)
On Sat, 28 Jan 2006, Nate Bargmann wrote: This is probably a silly (read obvious) question, but how does one change or specify the mini-icon of windows kwin only uses the generic X for? I've Googled and read some KDE docs, but I've not figured out the answer. I use several apps, Mutt in a xterm and xfte that I would like to use their icons on their respective windows. Ideas? Compare the infrastructure (menu templates, .desktop files, etc.) used by a programs which `work' and those which don't... look for missing lines and/or patterns of use. e.g.: Icon=kate vs. Icon=/some/path/to/icon.format The more the app looks like a KDE app, the more likely it is that KDE will display it the same as a native app. Don't forget to file wishlist bugs with patches against those packages you get to work properly. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDM - Command equivalence to K Menu-Switch User-Start a new session?
On Wed, 14 Sep 2005, MEGE Christophe wrote: ... Is there a command that does the same thing than K Menu-Switch User-Start a new session, so that I can start a new session from another 'wm' than kde, or switch to an existing other session? ... - Btw, it's possible to switch from one session to another using Meta-Fxx, but not creating a new one... You could switch to an unused VT, login, then do... $ startx /usr/bin/startkde -- :1 or make an alias of it in .bash_profile... alias kde='startx /usr/bin/startkde -- :1 /dev/null ' ...so all you need to do is: $ kde ENTER hth - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDM - menu?
On Wed, 14 Sep 2005, Curt Howland wrote: On the subject of KDM, before my latest round of re-installation of Sid (trying to make up for the kdelibs4 transition) which I'm running now, all of the window managers that I had loaded showed up in the KDM menu: twm, olwm, olvwm, kde, gnome, failsafe, etc. However, now it's not being populated with the other window managers, and for the life of me I cannot find where the menu list is or where it's defined. /usr/share/xsessions - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unmet dependencies
On Thu, 25 Aug 2005, Phillip Pi wrote: Here's the problem with apt-get commands after updating: # apt-get upgrade Reading package lists... Done Building dependency tree... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: kdelibs: Depends: kdelibs-data (= 4:3.3.2-7) but 4:3.3.2-6.1 is installed E: Unmet dependencies. Try using -f. I hacked around this problem by editing the kdelibs entry in /var/lib/dpkg/status so that... Depends: kdelibs-data (= 4:3.3.2-6) ^^^ ...which was: * quick, only one entry needed to be changed * easy, as in keeping the system happy with an existing situation vs. forcing the system to do something it doesn't want to do * automatically reversed, when the new kdelibs got installed Generally, one does not want to manually edit the status file. However, if the required hack is quick, easy and a one-time thing shrug why not, eh. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320628: incorrect Exec= in kdm/sessions/ude.desktop
Package: kdm Version: 4:3.3.2-1 Severity: important /usr/share/apps/kdm/sessions/ude.desktop... contains: Exec=ude TryExec=ude should be: Exec=/usr/bin/uwm TryExec=/usr/bin/uwm -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bug somewhere, but I can't figure where (CD copying)
On Wed, 6 Apr 2005, James Tappin wrote: Hi everyone, I'm confused by the following problem: If I 1) mount a CD-ROM by clicking on the device icon on the desktop. 2) Copy the data from that CD to hard disk with cp from the command line (in a konsole that was NOT started from the konqueror window with the CD ROM). 3) The CD is dodgy and there are i/o errors in the copy. 4) Close the konqueror window that is viewing the CD (via control-Q or the menu). It is then not possible to unmount or eject the CD-ROM. fuser -mav /cdrom1 tells me that a kdeinit process still has the cd or something on it open. Killing that kdeinit process kills most of my konqueror filemanager windows showing that it is konqueror and not konsole that is holding the cd device. If there are no i/o errors there is no problem. I'm using KDE 3.3.2 from Sarge on x86. Does anyone have any clues as to which component is likely to be at fault? Anytime this happens to me (using Sid's KDE)... # lsof /cdrom ...says that famd is holding onto the mount point... # /etc/init.d/fam stop ...releases it. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Launching KPPP from desktop with root loses dsktop icons and wallpapers...
On Fri, 4 Feb 2005, Phillip Pi wrote:
I placed KDE v3.3.1's KPPP icon on my desktop on my Debian v3.1 box
...
I could only guess as to what is going on since I have never used
KPPP. Make sure the user is a member of the dip and dialout
groups (use the groups command), then try it without the su to root.
To get an icon on the desktop without using KPPP I did the following:
As root...
# pppconfig
and setup for your ISP, then place the ppptoggle script in
/usr/local/bin and do
# chmod a+x /usr/local/bin/ppptoggle.sh
to make sure it is executable.
--- /usr/local/bin/ppptoggle.sh ---
# ppptoggle
#
# toggles ppp network access
# synopsis: ppptoggle provider
# provider is the name of a provider configured with pppconfig
pppup=`/sbin/ifconfig | grep ppp0 | cut -d -f1`
if [ $pppup = ppp0 ]; then
poff \
sed -i 's/Icon=nfs_mount/Icon=nfs_unmount/' \
$HOME/Desktop/${1}.desktop
else
pon $1 \
sed -i 's/Icon=nfs_unmount/Icon=nfs_mount/' \
$HOME/Desktop/${1}.desktop
fi
---
A user places the following *.desktop file on their Desktop and clicks
to connect or disconnect. Note: replace all occurrences of ISP with
the name you used with pppconfig (default: provider).
--- $HOME/Desktop/ISP.desktop ---
[Desktop Entry]
Encoding=UTF-8
Exec=/usr/local/bin/ppptoggle.sh ISP
GenericName=toggle the PPP network interface
Comment=connect/disconnect from ISP
Icon=nfs_unmount
Name=ISP
StartupNotify=false
Terminal=false
Type=Application
X-DCOP-ServiceType=none
---
Bugs:
The icon can get out of sync with the state of the ppp connection if
you (or a script) does poff or pon instead of ppptoggle, it will
sync with the next click. ppptoggle assumes ppp0. Errors not
handled.
Improvements:
- create ppp_on and ppp_off icons
- integrate with RBM-Create New-Device
- integrate with pppconfig
- support other desktops
- ...
- Bruce (hoping he didn't make any typos while cleaning it up :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian bugreports
On Mon, 10 Jan 2005, Anders Ellenshøj Andersen wrote: I didn't want to cut up your nice writing below, so I will just state my own small comment up here. Thanks (that you think the writing is nice :-) Let me just say that I personally would never ever consider filing any obvious KDE related bug with the debian bug tracking system. I always go straight to upstream. I have seen it work, and it seems KDE encourages this because they put the bug reporting option, that goes straight to their homepage, in the Help menu of every KDE application. KDE is big and complex enough that it needs a bug tracking system, and it would be bordering on negligence if they didn't offer a way to report - I don't think that means they intend bugs to be reported to them only, and would probably like if all the distros filtered reports from their users so they (KDE's developers) don't end up chasing bugs which have resulted from interactions with a particular distro's take on things. I think Debians bug tracking systems primary function is to sort out packaging problems and possibly security stuff for stable. Here it works well. I agree in principle, but it is not always obvious if a bug is KDE's or Debian's... especially if the Debian-KDE Maintainers are modifying things, and considering the majority of us probably don't have a clue as to how KDE works or what the Debian-KDE team may have done to get KDE to fit well in Debian. - Bruce
Re: disabling kpersonalizer
On Sat, 6 Nov 2004, Ulrich Fürst wrote: On Fri, 5 Nov 2004 10:33:52 +0100 Igor Genibel [EMAIL PROTECTED] wrote: You should also try to use the kiosk mode directives globaly Why should someone have a program installed, nobody's using. (or nobody should use) If I don't want to use ssh and I want to disable someone else to ssh to my (desktop) computer I don't try firewall rules, but simply deinstall it... Or am I missing something? Yup, you are missing something. If your firewall is on a separate box you can avoid having the desktop box needing to deal with attempts to use (say) ssh. If you have a combination firewall/desktop it probably doesn't make much difference.
Bug#272417: what's wrong and how to fix it
kdelibs-data is providing mimelnk .desktop files for sun formats, specifically: (Reading database ... 289586 files and directories currently installed.) Preparing to replace openoffice.org-mimelnk 1.1.2-3 (using .../openoffice.org-mimelnk_1.1.2-4_all.deb) ... Unpacking replacement openoffice.org-mimelnk ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.calc.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.chart.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.draw.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.impress.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.math.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.writer.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.stardivision.writer-global.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.sun.xml.calc.template.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.sun.xml.draw.template.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.sun.xml.impress.template.desktop', which is also in package kdelibs-data dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/mimelnk/application/vnd.sun.xml.writer.template.desktop', which is also in package kdelibs-data Setting up openoffice.org-mimelnk (1.1.2-4) ... The solution is to break the .desktop files out of openoffice.org-mimelnk and put them into their own package, which kdelibs-data should depend (suggest or recommend, as is deemed appropriate) upon. - Bruce
Re: Lots debian packages (wine, zapping, gst-plugins0.8, Qcad, etc.) can't enter to Sarge because of arts :(
On Fri, 17 Sep 2004, AKL. Mantas Kriauciunas wrote: There is a pretty big problem with arts (core sound system of KDE) - many debian packages (wine, zapping, gst-plugins0.8, Qcad, zinf and lots of kde packages) can't enter to Sarge because of arts :( The problem is, that arts in unstable is at version 1.3.0 and has release critical bug #269132, named arts 1.3 completely untested against kde 3.2 and lots of packages, which don't need exactly this version (works fine with version from testing) can't enter to Sarge, because they are compiled with arts 1.3.0 Sounds like the problem is with the packages whose preferred versions are not in testing. The best solution would be if the packages in testing were compiled using testing dev libraries (like libartsc0-dev), but current Debian politics doesn't allow this, so there always are lots of problems in situations like this (especially in the middle of the release cycle) I don't know what you mean. All packages in testing, including the dev packages, are derived from sources in the pool flagged as being in testing... no? So, I found 2 temporary solutions: 1. Allow to enter arts 1.3.0 into Sarge (look at the bugreport for more info - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269132 ) 2. Downgrade arts in unstable to 1.2.3 and recompile all packages in unstable, which depends on arts. How about introducing arts-future_1.3.0 into unstable and creating wine-newer, zapping-newer, etc. which depend on it, then let them migrate into testing. QA is satisfied and only the affected packages need to make an effort. If having two versions of wine, etc. in Sarge is no good then maybe some games can be played via proposed-updates or manual intervention to drop the older versions and rename the newer ones. - Bruce
solved (possible bug) - Re: servicemenu not recognized
On Tue, 31 Aug 2004, Christian Schuerer wrote: your example works on my system, but I would... Exec=gunzip $F ... use %F here (seems to be a typo). Yup, a typo, thanks. Maybe the service-types are the problem why it doesn't show up on your system. E.g., this service menu didn't show up on archives from ark, only on files ending with .gz or .zip. Try using a set of the following mime-types: ... application/x-tgz, ... (taken from the ark-service menu) Hmmm, on my system I expect it to show up for files matching the following globs: *.gz, *.tgz, *.z, *.Z (the first two from x-gzip, the other two from x-compress (had to add in *.z); I missed the x-tgz mime type). The problem was that I was testing on files ending with .tgz and .tar.gz and expecting the x-gzip service-type to pick them up. As it turns out KDE classifies them as x-tgz. :-( I wonder if *.tgz appearing in both x-gzip and x-tgz is a bug; or maybe KDE not picking up *.tar.gz as an x-gzip is a bug. Hope I could help a bit, You found a typo I'd missed, a few times, and brought x-tgz to my attention... so, your hopes are fulfilled. :-) Thank You. - Bruce
Re: where do mixer settings come from?
On Sun, 29 Aug 2004, Silvan wrote: ... I don't have a kmix* or *kmix* or *mix* or mix* anywhere in any user's ~/.kde either. That doesn't sound good; didn't you say the settings were not being remembered from session to session - lack of a kmixctrlrc would do that. Something is still screwing with the mixer though. (Not the sound system either. That's turned off for every user.) or maybe are you just seeing the default settings - Bruce
Re: where do mixer settings come from?
On Sun, 29 Aug 2004, Adeodato Simó wrote: * Frans Pop [Sun, 29 Aug 2004 20:03:01 +0200]: No, it's not a tab in Sound System. On my system Mixer is an option on the same level as Sound System in the expanded list for Sound Multimedia. So, you don't choose Control Center / Sound Multimedia / Sound System but Control Center / Sound Multimedia / Mixer I don't have it either, but thanks. I have: - Audio CDs - CDDB Retrieval - Sound System - System Bell - System Notifications You can always resort to manually editing... $ ls $HOME/.kde/share/config/kmix*
drag'n'drop multiple files
Sorry, lost the original message (and too lazy to look in the archive). Someone noticed problems with dropping multiple selections... I've noticed (with the aid of slow cpus, 50 and 133MHz) that if you drop before the outline of the slecected stuff is redrawn after the drag, the stuff gets deselected in the source and the move/copy/link menu doesn't popup. Solution: slow down; select, drag, pause, drop. - Bruce
Bug#266144: kscd: creating cddb entries fail
Package: kscd Version: 4:3.3.0-1 Severity: normal The CD Database Editor popup complains that At least one track title must be entered. when track tiles have been entered, then closes without updating the DB. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C Versions of packages kscd depends on: ii kdelibs4 4:3.3.0-1 KDE core libraries ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libartsc0 1.3.0-1aRts Sound system C support librar ii libasound21.0.5-1Advanced Linux Sound Architecture ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5client library to control the FAM ii libgcc1 1:3.4.1-5 GCC support library ii libglib2.0-0 2.4.6-1The GLib library of C routines ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library ii libidn11 0.5.2-2GNU libidn library, implementation ii libkcddb1 4:3.3.0-1 cddb library for KDE ii libpng12-01.2.5.0-7 PNG library - runtime ii libqt3c102-mt 3:3.3.3-1 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-6 X Window System Session Management ii libstdc++51:3.3.4-9 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m ii zlib1g1:1.2.1.1-5compression library - runtime -- no debconf information
Bug#263571: lisa: starts when it shouldn't
Package: lisa Version: 4:3.2.3-1 Severity: normal Upgrading lisa starts the daemon, even when there is no S* link in the current /etc/rc?.d dir. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C Versions of packages lisa depends on: ii debconf 1.4.30 Debian configuration management sy ii kdelibs4 4:3.2.3-4 KDE core libraries ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libc6 2.3.2.ds1-15 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5client library to control the FAM ii libgcc1 1:3.4.1-5 GCC support library ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library ii libpng12-01.2.5.0-6 PNG library - runtime ii libqt3c102-mt 3:3.2.3-4 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-6 X Window System Session Management ii libstdc++51:3.3.4-7 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m ii zlib1g1:1.2.1.1-5compression library - runtime -- no debconf information
Re: packages fetching tools
On Tue, 27 Jul 2004, David Pye wrote: On Tuesday 27 July 2004 05:53, Nate Duehr wrote: ... There are actually dependency issues that apt-get CANNOT resolve that dselect can. Specifically when a package is added to the archives and a new dependency is created, apt-get chokes on it saying that it will hold-back the old packages, whereas dselect will show the problem and allow you to accept the fix (adding another package) with a simple ENTER if you agree. Then, this is a bug or missing feature in apt-get. And I thought apt-get dist-upgrade resolved this, but anyways, either way, if this doesn't work with apt, it means apt should be fixed, not that dselect should be forced on people who don't like it. I don't think it is reasonable to expect any of the package handling tools to be able to deal with all of the possible dependency problems... especially when pulling from unofficial archives (where this thread started). If apt hadn't existed, I might even have been forced to give up using Debian because of the thought of having to use dselect for package management. Methinks you doth protest too much. ;-) I feel the same as the first poster, frankly. I don't like any curses or CUI based package managers. I want a CLI based one, and apt-get does the job very nicely, at least for me. I want a CLI for managing individual or small groups of packages; when potentially large or questionable upgrades come along (e.g., daily upgrades of unstable) I want the ability to snoop around the DB before doing anything. What I would really like is a version of dselect which can handle multiple available archives, and allows manual editing of /var/lib/dpkg/status... all the better if it is scriptable so using it from a CLI (or wrapping some KDE around it :) is feasible. - Bruce
Re: packages fetching tools
On Sun, 25 Jul 2004, Paul Johnson wrote:
Bruce Sass [EMAIL PROTECTED] writes:
On Sun, 25 Jul 2004, Nathaniel W. Turner wrote:
Since people keep telling us that apt-get is braindead, and that
aptitude does a better job, I tried that too, with similarly scary
results. Since aptitude's output is more compact, I include it here.
In my experience, aptitude has its own set of problems. Alas, nothing is
perfect.
Don't forget about dselect. If the APT tools are not giving you enough
control then maybe dselect will, especially if you don't use the apt
method for fetching packages.
If aptitude can't do it right, dselect surely won't do the right
thing...
I never claimed it would fix things automatically; and it is easier
than hacking /var/lib/dpkg/{status,available} to fix a problem.
- Bruce
packages fetching tools
On Sun, 25 Jul 2004, Nathaniel W. Turner wrote: Since people keep telling us that apt-get is braindead, and that aptitude does a better job, I tried that too, with similarly scary results. Since aptitude's output is more compact, I include it here. In my experience, aptitude has its own set of problems. Alas, nothing is perfect. Don't forget about dselect. If the APT tools are not giving you enough control then maybe dselect will, especially if you don't use the apt method for fetching packages. - Bruce
Re: KDE 3.3b1
On Fri, 16 Jul 2004, Stephen Cormier wrote: On July 16, 2004 05:34 am, Paul Johnson wrote: Daniel Andor [EMAIL PROTECTED] writes: Adding the experimental source lines and doing apt-get install gcc-3.4/experimental libgcc1/experimental allowed me to install new version of libqt3c102-mt. gcc-3.4 is probably not needed. What are these experimental source lines of which you speak? deb http://ftp.debian.org/debian ../project/experimental main contrib non-free [going back a bit and using my memory, maybe things have changed] Something to keep in mind when using experimental is the difference between package/experimental and -t experimental package. The former will grab package from experimental and dependencies from the default distribution while the latter will get package and any dependencies you need from experimental. When I was using dselect to get XFree from experimental I found it necessary to put APT::Default-Release experimental in /etc/apt.conf, then edit sources.list to control where I was getting packages from. A side-effect was that when the experimental line was commented out in sources.list I could easily see which packages came from experimental because the were in the Obsolete/Local section. When not commented out it was necessary to put stuff I didn't want to pull from experimental on hold. I don't think I would try to use dselect and experimental together today because there are many more packages in experimental than there was back then... there would be way too much holding and un-holding(?) going on, which, besides being a pain, could be more human error prone. - Bruce
Re: display problem (correction)
On Thu, 15 Jul 2004, Michael Rudmin wrote: So in Debconf, I selected VESA/8 bit/600x800, and told it to assign 512 MB to the card. correction, I meant 512 kB, or half a megabyte. that's better It sounds like you need to play with the modelines yourself, instead of taking the first one offered by XFree. Iirc, its been awhile, the startup logs (/var/log/XFree86.display.log) should have a list of modelines... pick a valid one for the resolution you want which is not marked as the default and enter it into /etc/X11/XF86Config-4. If there is nothing there then you may need to craft one yourself... ...good luck, I've always been real lucky and managed to find one without having to figure out how to do that. - Bruce
Re: When is the K-Menu going to lose the Debian submenu?
On Mon, 12 Jul 2004, Chris Cheney wrote: On Sun, Jul 11, 2004 at 03:41:59PM -0600, Bruce Sass wrote: It would be even nicer if Debian's KDE allowed the sysadmin and users to choose whether they wanted the KDE, Debian, or both styles of menu. It already does, the applications.menu file itself is under /etc/xdg/menu you just have to edit it to the style you want. The users menu can be stored under ~/.config/menu similar to how update-menus works already. I'm looking for simple config items, along the lines of... Choose a menu style for the KDE desktop: [ ] system default whatever the Debian-KDE developers have setup [ ] KDE onlyignores the Debian generated menu [ ] Debian only ignores the default KDE menu [ ] custom the sysadmin or user is on their own Editing the xml based applications.menu will not be so straight forward, especially when it comes time to merge sysadmin tweaks in with changes to the system default. - Bruce
Re: When is the K-Menu going to lose the Debian submenu?
On Sun, 11 Jul 2004, Chris Cheney wrote: On Sat, Jul 10, 2004 at 09:36:55AM -0500, Bud Rogers wrote: On Friday 09 July 2004 22:30, Doug Holland wrote: WHY is there a Debian submenu in the K Menu? Why are half of the utilities in K-Utilities, and the other half in K-Debian-Apps-Tools? Why is there not a unified set of menus? The submenu is a nuisance. It doesn't serve any useful purpose that I can see and it breaks the logical flow of the menus. The layout of the Debian menu is much different than the fdo menu so there isn't really a clean mapping between them. Debian for example puts graphic viewers, pdf/postscript viewers, and movie viewers (iirc) in the same category, for the fdo menu all three are broken out into separate categories and are in entirely separate sections. FWIW - Gnome menu breaks out the Debian submenu exactly the same as KDE. It would be really nice if Debian menu would switch to fdo menu soon since fdo menu categories are much more logical than the current Debian set amongst other improvements that moving to fdo would buy us. It would be even nicer if Debian's KDE allowed the sysadmin and users to choose whether they wanted the KDE, Debian, or both styles of menu. - Bruce
Re: install: kdelibs3 - error in unpacking
On Thu, 1 Jul 2004, Alexandr Rosen wrote: Hi, I am new to linux and debian and kde, and I have a problem with installing the system - the message kdelibs3 - error in unpacking Generally: If you can not find record of a problem with the package (check mail archives, bugs.debian.org) then you may have a bad download and will need to get a fresh copy. Either remove the package from the local cache (as root: rm /var/cache/apt/archives/kdelibs3...deb) and rerun the APT command you used for the upgrade, or manually download the package and install it (as root: dpkg -i /path/to/package...deb). occured during install, and dpkg --configure kdm says that this error will probably disappear when kdelibs3 gets sorted out errors were encountered while processing. Is there any easy solution? Hopefully, but it is sometimes hard to say without more information. In the very least you should tell us which Debian you are using; the command cat /etc/debian_version spits out what we want to know unless it mentions testing or unstable, in which case the date of the last upgrade may be significant. If you are not sure about what information is important you can run the reportbug command which will gather up the info for you (just don't send it off to the Bug Tracking System, BTS). hth - Bruce
$KDEHOME/cache-HOSTNAME
Hi, Has anyone tried linking a user's KDE cache dir to a tmpfs[1]? I would expect a performance boost but can't properly test it because I'm usually 40-60M into swap when running KDE + apps. The cache would need to be saved to HDD and restored for a reboot, but is preserved through logins. - Bruce [1] tmpfs is the one which runs out of VM and doesn't need to have a fs created in it before it can be used (kernel: CONFIG_TMPFS), probably shows up as: tmpfs47324 0 47324 0% /dev/shm in df's output if it is enabled.
Re: $KDEHOME/cache-HOSTNAME
On Mon, 28 Jun 2004, Hendrik Sattler wrote: Am Montag, 28. Juni 2004 22:20 schrieb Bruce Sass: Has anyone tried linking a user's KDE cache dir to a tmpfs[1]? I have tmpfs mounted on /tmp with no problems so far. Interesting is the usage of different tmp directories for links in ~/.kde: cache-linux - /var/tmp/kdecache-hendrik socket-linux - /tmp/ksocket-hendrik tmp-linux - /tmp/kde-hendrik Looking at /var/tmp/kdecache-hendrik, there is some konqueror stuff but nothing that could speed it up a lot. I can get hit pretty bad when kbuildsycoca kicks in, typically when I do an upgrade then go offline (wwwoffle rebuilding its index, apt/dpkg, ...) and the output of top indicates that disk i/o is the bottleneck (both the idle and wait Cpu stats 0.0%). It may turn out that only those with lots of RAM and not a lot of cpu cycles would benefit. Thanks - Bruce
Re: Help -- SVG Browser Needed
On Fri, 25 Jun 2004, Robert Tilley wrote: ... Can people chime in with their preferred methods for display, creation, and editing of SVGs? I wish to begin learning this new technology without having to go back to Windows and Illustrator. Have you tried Amaya? I'm not suggesting it is good, just curious about where it is wrt to those already mentioned. - Bruce
Re: Kicker: no Applications but Lost Found
On Wed, 23 Jun 2004, Michael Schuerig wrote: Some time ago the contents of the K-Menu (Kicker) have changed. There's no longer an application menu called Applications, instead now there is one called Lost Found containing some, but not all, items previously in Applications. Also, integration of Debian applications has changed I'm using the latest KDE packages on unstable. Now they have their own top-level menu whereas previously they were sorted thematically into the KDE menus. I liked the earlier state a lot better. Are these changes due to bugs or are they intentional? They appear to be intentional... shrug KDE-Debian menu integration has been going downhill since KDE-1, imo. If there was an option which would trash the KDE portion and leave me with just the Debian stuff I'd use it in a heartbeat. - Bruce
Re: HTTPS KIOSlave dies
I'm also doing daily updates from unstable and have been seeing flakiness with some kioslaves (e.g., dead ssh processes); but I wasn't going to worry about it because I have a mix of kde 3.2.2 and 3.2.3, built against different versions of Qt... I'm surprised more stuff hasn't started acting up. On Fri, 18 Jun 2004, Marcus Thiesen wrote: Hi, I know this is maybe to much a fuzzy problem, but it really kills me at the moment. My KIOSlave for HTTPS dies and I didn't find a way till now to fix it. This happens on any site, so it is not specific to a page or URL, it must happen directly when the slave is loaded. ...
Re: unstable: apt-get install cupsys
On Thu, 3 Jun 2004, Roy Bixler wrote: On Thu, Jun 03, 2004 at 03:39:33PM +0200, dekkker wrote: If I do apt-get install cupsys it says: cupsys: H?ngt ab: libcupsimage2 (= 1.1.19final-1) soll aber nicht installiert werden H?ngt ab: libcupsys2-gnutls10 (= 1.1.20final-1) soll aber nicht installiert werden H?ngt ab: libcupsys2-gnutls10 (= 1.1.20final+cvs20040330-4) soll aber nicht installiert werden H?ngt ab: gs-esp soll aber nicht installiert werden E: Kaputte Pakete So, libcupsimage2 etc. are not going to be installed. snip Any hints are appreciated. I must be doing something very wrong. -.- Thanks. I have the same situation. I downloaded each of the CUPS packages manually and installed them with a --force-depends flag. CUPS works now, but apt still wants to remove KDE every time I try an update. I don't think either of us are doing anything wrong, but the problem would seem to be a packaging error in CUPS. Probably one of the packages is missing an apropos Provides line. For now, I will see if there is a CUPS package update which fixes this problem. I found that putting the CUPS -dev pkg on hold is enough to keep APT from trying to remove most of KDE. - Bruce
Re: Downgrading KDE?
On Sun, 30 May 2004, Theo Schmidt wrote: Dear KDE-Debian list, I´ve been using Debian installed by Knoppix 3.2 sucessfully for some time, with KDE, but recently I installed digikam 0.6 with aptitude and this updated KDE at the same time to version 3.2.2. Now KDE has several problems: - Its all in English although I have the Geman version installed and the German and Swiss settings selected. - The right mouse button no longer works in the browser mode of Konqueror. - I keep getting three Konsoles opening when starting, they eat up all the CPU load, and can only be closed by killing. - I don´t like the new icons as well as the old ones. shrug For these reasons I would like to go back to the previous version, e.g. KDE 3.1.5. How can I do this without causing a major upset? The APT-Howto says that things can´t be removed without removing all dependencies as well. How can I thus deinstall KDE 3.2.2 without losing all KDE programs? Don't worry about it, all the KDE programs will be replaced by different versions when you install 3.1.5 (some system libs may get rplaced also). If APT, dselect, ..., doesn't do what you want, and you are certain it is what you want to do, you may need to resort to dpkg --purge --force-depends ... As it is derived from Knoppix, my installation is a mixture of testing and unstable. Testing is the default. Why not set your sources.list to unstable only, then do a dist-upgrade, :-) - Bruce
Re: How to uninstall kvim?
On Fri, 21 May 2004, VSJ wrote: I can't uninstall kvim, I'm using Debian sid with the latest kvim package (version 1:6.2-532+4). After using the dpkg --purge command, also the normal console vim (VI) becomes unusable! See below: ... Any ideas? Thanks in advance. $ locate vim.org vim.old then manually remove the diversions, then purge all (k)vi(m) packages and reinstall those you want - Bruce
Re: Removing Gnome and Related Packages?
On Sat, 16 Aug 2003, Robert Tilley wrote: Using aptitude, can anyone supply some information that would help me to remove Gnome and it's related libraries so that I can have as pure a KDE system as possible? I've looked into doing this to individual packages and the length of time required is prohibitive. `dpkg --purge' some of the lower level Gnome libs, follow up with deborphan. I would expect aptitude to work the same.
Re: true type fonts fixed...
Hi, Thought you may be interested. I managed to get all the installed tt fonts visible by manually deleting font.* files, then: # mkfontscale # mkfontdir in the appropriate dirs, followed by: # fc-cache -fv ...now using XF86-4.3 with the freetype module (still sid, was 4.2.1 with v3.3.6 Xservers and xfstt|xfs-xtt font servers). I have tt fonts either duplicated or linked in both /usr/X11R6/lib/X11/fonts and /usr/share/fonts... fc-cache is only generating fonts.cache-1 files under /usr/X11R6. fontconfig is seeing multiple versions of some fonts; x3 in the case of the larabie fonts, x2 was expected. :-/ Guess I can now reconfigure fontconfig to ignore /usr/share/fonts, eh. I noticed that some of the fonts.dir files were 2-bytes long, which is the result if there is no fonts.scale file when mkfontdir is run in a dir with scaleable fonts. Not sure if this is a result of my fiddling or an installation doing stuff in the wrong order. So, the problems for me appear to have been a result of mkfontscale not being run, or not being run before mkfontdir, and /usr/share/fonts being ignored (even though fc-cache appeared to be processing it)... exacerbated by me not really knowing what was/should be going on. I'm tempted to dpkg-reconfigure back to a v3.3.6 xserver, reinstall a tt font server or two, and see if I can get all fonts working (now that I have somewhat close to half a clue). - Bruce
Re: true type fonts fixed...
On Mon, 14 Jul 2003, Ross Boylan wrote: Unfortunately, I have no great wisdom, just some clarifications and speculations below. ditto ... big sigh My characters don't appear as boxes; they are simply blank or, (I think) sometimes horizontal lines. And they aren't all affected. For example, in my current KDE2 environment I see what I'm typing emacs now; I see stuff in Mozilla; but I don't see the text of KDE help (though I see the table of contents). Yikes! If I was having that much trouble I think I'd --purge *everything* and start with a clean slate. [Bruce said] I have had export QT_XFT=0 in .bashrc for awhile and have been starting KDE from the commandline, so I shouldn't have to worry about XftConfig making a contribution. (right?) What is QT_XFT supposed to do? I've never heard of it. Not sure anymore, actually forgot about it until you mentioned XftConfig. iirc, it sounded like the thing to do when anti-aliasing first arrived and I heard the v3 xservers couldn't do it... it either fixed a Qt problem or prevented one (hell of a way to run a system, eh :-) Remember I said I managed to get ttf via xfs-xtt... well, the ttf-larabie pkgs got installed but the fonts didn't appear in KDE so I went into the kcm font installer to see what would happen --- now I'm back to no tt fonts (tried both administrator and user mode, *.afm created in same dir as the *.ttf files this time). So, Arial and the rest of the ms core fonts have disappeared from the KDE font selectors and the only thing touched was the KDE font installer (which shows the tt fonts as installed and enabled)... Two more ideas about your problem: Since it appears that KDE can only handle fonts in one directory hierarchy, perhaps the installation of fonts in new places (assuming larabie and mscore fonts are in different directories) confused it. I don't think so. The ms and Larabie fonts are in /usr/share/fonts and the ms ones were served up by xfs-xtt, KDE's font installer showed nothing (no fonts installed and therefore nothing selected). It wasn't until after copying the ms fonts into the X11R6 hierarchy (the Larabie stuff was already symlinked in) and making KDE aware of the fonts via the font installer that tt fonts disappeared again. Could anything be broken in the utility programs (e.g., ttmkfontdir, or something like that) that set up the index files? Could be. I did notice a message during X startup indicating a problem with the Larabie fonts, X deleted them from the font path and suggested running mkfontdir... which I did, which did seem to make X happier, then I tried the KDE font installer (which had the effect of making the ms fonts disappear)... I probably should have just restarted xfs-xtt after doing mkfontdir (and perhaps ttmkfontdir if xfs-xtt still didn't see them). ...how do I disable KDE's font installer subsystem, it appears to be broken. Don't know. And do you want to? I though this was the only way that KDE became aware of fonts. From this perspective it looks like KDE can fall back to whatever the system provides, it only blows up after I run the KDE Font Installer. - Bruce
Re: true type fonts fixed...
Sorry 'bout the delay. On Fri, 11 Jul 2003, Ross Boylan wrote: On Thu, Jul 10, 2003 at 03:21:15PM -0600, Bruce Sass wrote: On Wed, 9 Jul 2003, Ross Boylan wrote: On Wed, Jul 09, 2003 at 01:41:26AM -0600, Bruce Sass wrote: scenario: sid, kde-3.1.2, xserver-svga (v3.3.6), X-4.2.1, xfstt Huh? Are you combining parts of X from 3.3 (xserver) and 4.2 (the rest)? I'd be surprised if that worked out. Why is that? Would you be surprised if a v3 remote X-terminal could connect to machine with XFree-4? Well, you're right that it should work, but whether it actually works is a different matter. It probably didn't get much testing. Ya, too bad considering the number of unsupported in XF4 graphics cards. It also might be particularly problematic in the case of fonts, since as far as I can tell some of the font functionality is migrating to the client (while perhaps also remaining on the server) with v 4. I'm not sure exactly what's where. Further study in this area seems to produce further confusion, at least sometimes! Too many cooks; clients should use what fonts are available through the underlying operating system, not try to do it themselves (imo). - KDE knows about the fonts but they are not rendered How do you know it knows? ...on a per-user basis: fonts were copied into ~/.kde, had a green checkmark, appeared in the font selector dialogs, but were always rendered as helvetica ...in admin mode: .afm's were created (iirc) under X11R6 when the fonts were in /usr/share/fonts (no surprise, eh)... green blah blah helvetica Well, that's an interesting variation on my problem. Mostly, I don't see anything at all, whereas you get some default font (maybe my default font is invisible?). I've never had a system wide `all characters are boxes' problem; maybe with one or two non-KDE apps, quite awhile ago, and definately not related to the current font problems. My symptoms: 1) Some text doesn't appear at all in Konqueror, or only as lines. For example, I only see the graphics on my KDE help pages (even in my vanilla Debian KDE 2.2 installation). never seen that 2) Some apps have drop down lists of styled texts. Some of the entries are blank. 3) Some apps give you a font chooser which lets you pick style, size, etc and shows a preview pane. When I pick some fonts, the preview pane is blank. seen these with specialized symbol fonts, but chaulked it up to a lack of anything to render (i.e., blanks at those `character codes') Hmmm, could having ttf available through both fontconfig (via x-ttfcidfont-config) and xfs-ttf be a problem... s/b xfs-xtt :-/ Well, I've been more thinking that not having fonts available through fontconfig is the problem. Someone recommended to me to make sure the TT fonts were in fontconfig. sounds reasonable except the v3 xservers don't know about fontconfig (???) I think there are too many cooks shrug, and am not sure why KDE is doing low level mucking about with fonts (especially at the system level). KDE apparently uses Qt to handle fonts. I'm not sure if the stuff in the control center is a straight interface to Qt or if KDE is adding something extra on top. I can understand Qt (needs to run under three different OSes) wanting to go low-level with font set up, but what is KDE's excuse. My understanding du jour of font configuration: - XftConfig is used by freetype v 1 and apps that depend on it. Probably none do. - fonts.conf is used by fontconfig and freetype v2. Most newer apps use this, including newer KDE. Note that freetype v2 is in the libfreetype6 package on Debian. - XF86Config-4 used by the X server itself. But in v4 the server is schizophrenic, getting some stuff the traditional way and some via freetype v 2 (or maybe X and Freetype both use the same core library?). - various spots for particular apps. Maybe one of those spots is aliasing everything to Helvetica? I have had export QT_XFT=0 in .bashrc for awhile and have been starting KDE from the commandline, so I shouldn't have to worry about XftConfig making a contribution. (right?) XF86Config-4 is not used by the v3 servers so I haven't touched it (looks ok, afaict, has the /var/lib/defoma/x-ttf... lines and correct ttf server port reference in the Files section). The only font infrastructure related pkgs I have sought out are ttf servers, anything else has been pulled in via dependencies (e.g., fontconfig, freetype v2.1.4-4, x-ttcidfont-conf) and configured however Debian defaults to doing it. Remember I said I managed to get ttf via xfs-xtt... well, the ttf-larabie pkgs got installed but the fonts didn't appear in KDE so I went into the kcm font installer to see what would happen --- now I'm back to no tt fonts (tried both administrator and user mode, *.afm created in same dir as the *.ttf files this time). So, Arial and the rest of the ms core
Re: true type fonts fixed...
On Wed, 9 Jul 2003, Ross Boylan wrote: On Wed, Jul 09, 2003 at 01:41:26AM -0600, Bruce Sass wrote: scenario: sid, kde-3.1.2, xserver-svga (v3.3.6), X-4.2.1, xfstt Huh? Are you combining parts of X from 3.3 (xserver) and 4.2 (the rest)? I'd be surprised if that worked out. Why is that? Would you be surprised if a v3 remote X-terminal could connect to machine with XFree-4? XFree86 v 4 does not require any font servers, and I think it works with a different set of font servers than 3.3. It handles TT builtin (provided you load the right module, freetype, in XF86Config-4). I think there's another module that also can handle TT). that's how I understand it also (at least for local sessions) Finally, KDE 3.1.2 (and probably earlier, but maybe not 2) has a control panel option for registering fonts, including specifically one for Type1 and one for TrueType. You need to go into administrative mode to make this effective for all users (there is a button on the panel to do so--you don't need to login as root). This seems to require that both directories be under the main font directory, which may require a symlink, esp for TrueType. didn't work either ways (usr|admin share/fonts|X11R6...fonts... - KDE knows about the fonts but they are not rendered How do you know it knows? ...on a per-user basis: fonts were copied into ~/.kde, had a green checkmark, appeared in the font selector dialogs, but were always rendered as helvetica ...in admin mode: .afm's were created (iirc) under X11R6 when the fonts were in /usr/share/fonts (no surprise, eh)... green blah blah helvetica ... Depending on where you got your TrueType fonts, you may have a huge number of them. You might want to pare down the list (the one in fonts.dir, fonts.scale, and related files) so it only has your favorites. That might speed things up. just the ms core tt fonts ... Hmmm, could having ttf available through both fontconfig (via x-ttfcidfont-config) and xfs-ttf be a problem... s/b xfs-xtt :-/ Well, I've been more thinking that not having fonts available through fontconfig is the problem. Someone recommended to me to make sure the TT fonts were in fontconfig. sounds reasonable except the v3 xservers don't know about fontconfig (???) I think there are too many cooks shrug, and am not sure why KDE is doing low level mucking about with fonts (especially at the system level). Oh well, it's probably moot for me now. I saved a P133 wth a 1G drive (installed stable) from the landfill recently, and just today fixed it up with 96M and the 30G drive (unstable) with my $HOME, it has an S3 Trio64V+ which is supported in Xfree-4.3... - Bruce
true type fonts fixed...
...sorta. scenario: sid, kde-3.1.2, xserver-svga (v3.3.6), X-4.2.1, xfstt - KDE knows about the fonts but they are not rendered - xfontsel works as expected Purging all the font related stuff I could without --force-depends, then manually removing any cruft which had built up over the years (originally a Debian 2.0 system), got KDE to the point where it knew nothing about ttf. Reinstalling and reconfiguring the font stuff brought it back to where it seemed to know about ttf, but still wouldn't render them. scenario: same as above except with xfs-ttf - KDE renders ttf - xfontsel works but thinks the majority of the ttfs are in the monotype family The sorta refers to the fact that while KDE is now displaying ttf, if I try to select fonts for Konqueror the system slows down (I'm on a 66MHz box, when I say slow it is really s-s-s-l-l-l-o-o-o-w-w-w :-) or freezes (CTRL-ALT-ESC closes the font selector dialog, without the skull and bones cursor appearing) and an additional 50M of swap gets used (about half of the VM is released when the dialog closes). Repeated use of the kcm khtml font module pushes the swap usage up by about 30M per use. Logging out of KDE recovers all the VM. True type fonts work fine with other wm's (fluxbox, uwm, xfce) and apps no matter which ttf server is in use --- so it appears to be a KDE problem, or perhaps a system problem that just happens to hit KDE hard. Hmmm, could having ttf available through both fontconfig (via x-ttfcidfont-config) and xfs-ttf be a problem... HTH anyone else with font problems. - Bruce
sid: konqueror, famd
Is anyone else noticing Konqueror freezing and famd eating up more CPU cycles than it should? - Bruce
cryptic error message (font installer)
Control Center - System Administration - Font Installer - Administrator Mode gets me: - Loading... - window prompting for root's password - Loading... - a window saying File does not exist and folder is not writeable. [I click on the OK button] - Loading... - a listing of fonts (all enabled, none of the .ttf's are actually rendered by KDE though) Does anyone know which file doesn't exist and which dir can't be written to? - Bruce
Re: Has anyone figured out why fonts are broken...
afaict (or know)... xserver-svga is a v3.3.6 server, so I need a tt font server. I don't think anti-aliasing works with v3 servers. I don't recall looking at /etc/fonts/... though. On Tue, 17 Jun 2003, R Sean Eidemiller wrote: I'm running KDE 3.1.2 and TT fonts are working great. Not only that, they look beautiful thanks to the new antialiased rendering provided by Xft2/fontconfig. I didn't use the msttcorefonts package (or whatever it is) but rather stole them from a win2k machine and placed them all in /usr/lib/X11/fonts/ttf. After that, I ran ttmkfdir, added the directory to my font path in XF86Config-4 (I don't use xfs or xfstt) and all was good. To get antialiasing to work, you will have to add the path to your TT fonts in /etc/fonts/local.conf file, like this... dir/usr/lib/X11/fonts/ttf/dir Restart the Xserver, and you should be good to go... -Sean ([EMAIL PROTECTED]) ...because I haven't seen a truetype font since KDE 3.1, and NONE of the tips passed out on this list has worked to get them back. I'm on a testing/unstable box running xserver-svga and xfstt. gsfonts-x11 and 100dpi fonts are visible and rendered. The Qt font config prg lists everything and shows them as selected, but Helvetica is rendered in their place. xfontsel is working (everything installed shows up and is rendered). HELP, please - Bruce
Re: Has anyone figured out why fonts are broken...
iirc, once or twice, but not recently (it is running now but will take awhile on this old box). When doing the font cache update command (don't remember what it is atm, currently being run by the dpkg-reconfigure, ya) messages indicated that lots of fonts were found and registered, but it didn't make any difference to KDE. On Tue, 17 Jun 2003, Anders Ellenshøj Andersen wrote: On Tuesday 17 June 2003 19:20, Bruce Sass wrote: ...because I haven't seen a truetype font since KDE 3.1, and NONE of the tips passed out on this list has worked to get them back. Did you try? # dpkg-reconfigure fontconfig Anders
Has anyone figured out why fonts are broken...
...because I haven't seen a truetype font since KDE 3.1, and NONE of the tips passed out on this list has worked to get them back. I'm on a testing/unstable box running xserver-svga and xfstt. gsfonts-x11 and 100dpi fonts are visible and rendered. The Qt font config prg lists everything and shows them as selected, but Helvetica is rendered in their place. xfontsel is working (everything installed shows up and is rendered). HELP, please - Bruce
depending on dh-make (was: different kde_htmldir)
On Wed, 14 May 2003, Daniel Stone wrote: On Wed, May 14, 2003 at 08:41:00AM +0200, Dominique Devriese wrote: Daniel Stone writes: This is another problem, indeed. Why don't the Debian KDE packages set the prefixes to /usr:/usr/local:/usr/local/kde, so that installing third party source packages goes as easy as possible ? Because you should be using packages where possible, anyway? KDE should recognize stuff under /usr/local. more reasons to support /usr/local ootb Afaict there is no place for an admin to make global mods to KDE. I have some-editor.desktop files I'd love to be used in preference to the ones KDE supplies; putting them under /usr gets them overwritten next upgrade, using kappfinder gets everyone their own copy in .kde (and the sysadmin loses control of the contents). It seems pretty typical of large multi-piece software packages to have a mechanism for including both admin and user supplied components (e.g.: emacs, tex, python, ocaml, octave, ruby, ...) /more reasons to support /usr/local ootb So my question is: Wtf is this patch intended to fix, and why does it not make sure that people installing third party kde apps from source can still read the documentation.. Daniel /usr/share/doc/HTML is documentation for the package called Daniel 'HTML'. If everyone put their documentation in there, it Daniel would be an utter mess. The dir belongs to dhelp; if KDE registered its docs there would be links in the HTML/*/index.html files. I don't think that just putting kde stuff in a different place solves anything, since in the HTML dir are only kde packages' documentation, and such the mess remains, it's just split in half. That's my point! KDE documentation should remain in /usr/share/doc/kde/HTML, where it belongs. (aesthetics aside) I don't see why they should remain or belong in any particular place, compatibility is just a symlink or reference away, right. KDE should look for stuff in user (.kde), local (/usr/local /opt) then system (/usr) space. Daniel I vote for 3 - just use the option to ./configure. tell your users to use the option to ./configure, you mean, I guess, which is why I don't like this option too much.. If you have that many Debian users, wouldn't it be easier to just make packages? yeah Do you think there is any way to make ./configure auto-detect this ? Could perhaps debianrules get another output target that would be usable in a shell, and ./configure could source this if it detects it's on a debian system ? Well, you could source debianrules, and use $(kde_options) or whatever. Detecting a Debian system is wrong and broken. I run a Debian system, but run HEAD, and all my stuff is in /opt/qt3 and /opt/kde3. I think the dh-make template should get its own package (placing it under /usr/share/debhelper/dh_make perhaps), and build-depend on dh-make. Building a debian-kde package: `dh_make -t... debian/rules...', or perhaps a more automated `kdepackage' (think kpackage) command. 3rd party developers could be given, and instructed on how to edit up, an overlay template... making the build command: dh_make -t... dh_make -o... debian/rules... downside: a more complex kdepackage is getting attractive What I would like to do (but would need to actually learn PERL first) is to break out the code which determines the values of the substitution targets in the templates, and place it into the template directory. i.e., putting #AUTHOR# in a template would trigger the path-to-template/#AUTHOR# (or whatever name would work :-) script, whose output would be used as the substitution. The result would have dh-make managing the application of templates, template authors determining their own destiny (.spec template(s)?), everyone using dh-made src automatically gets packages tailored to their system, developers get a flexible and relatively painless method of enforcing standards... ...which is really what the whole `stuff not being found' problem is about. imo - Bruce
Re: Odd pauses with KDE 3
On Wed, 30 Apr 2003, Craig Dickson wrote: On my only sid KDE 3 machine, I notice that the entire system seems to pause for a few seconds at a time. Launching a new Konqueror process (I ... Does anyone have any idea what could be causing this, or suggestions for things I should check? This problem does not occur under Gnome 2 or in other non-KDE environments, even on the same machine. TIA for any help that anyone can offer. KDE3 freezes when kbuildsycoca runs... It may be tough to see on a modern machine but on this old 66MHz box top (run from a text vt) clearly shows kbuildsycoca eating up all the CPU cycles it can get when KDE is unresponsive. You may be able to see it if you start top doing a fast update, then make changes to a directory containing *.desktop files. - Bruce
Re: Creating a private folder?`
On Thu, 20 Mar 2003, Ralf Nolden wrote: On Thursday 20 March 2003 08:56, Sven Bergner wrote: ... After that you can use the cryptoloop kernel-module to produce a encrypted partition. I think that's the way it works. More important however is if the KDE icons, when you click on a device icon, support passphrase entering when mounting a partition that has a passphrase lock. How does one get the KDE icons to support passphrase entering...?
Re: Text files in konqueror
On Wed, 19 Mar 2003, Joseph Schlecht wrote: ... the web, konq asks me to open or save as. If I select open, the file is downloaded but nothing happens; vim never opens ... Has anyone else encountered this problem? Is there a solution? Yes, when configured to use xless as an external viewer. I don't know about a solution. - Bruce
Re: gui for gpg
On Tue, 18 Mar 2003, Ralf Nolden wrote: deb http://ktown.kde.org/~nolden/kde woody main apt-get update apt-get install kgpg has someone built kgpg for sid? is there a general source for KDE apps not in sid? - Bruce
Re: KDE Usability survey
On Thu, 13 Mar 2003, Svenn Are Bjerkem wrote: On Thursday 13 March 2003 01:08, Frank Van Damme wrote: On Wednesday 12 March 2003 21:27, Randy Kramer wrote: ... * The optimization effort currently going on in kde. I wasn't really aware of this :-) ditto :-) It would be interesting to know why the bleeding edge people insist on using old hardware. - we like pushing the envelope in all directions - crippling a nice new machine with unstable software doesn't always work - easiest way out of a compatibility issue If you think that you want to draw people from win95 on a P100 to to linux offering KDE3.1 you miss your audience. I don't think the audience is missed, maybe small, and probably best targeted (can't expect to do all of KDE3+ on an old slow box, at least not all at the same time). ... I really hope I am wrong and that somebody is still developing the KDE1 and Debian Weekly News - February 11th, 2003: ...the [3]Turbo Desktop Environment aimed at users with older computers who still want to run a proper desktop. It is based on KDE 1 and Debian. 3. http://www.liniso.de/tde/ Anyone used TDE yet? - Bruce
Re: Rethinking Qt headers (should the header packages be recombined?)
On Thu, 27 Feb 2003, Karolina Lindqvist wrote: I think the README.Debian should be more accessible, and easier to read. Maybe it already is, and I just don't know how to do it? Something needed in the KDE project would be to make such information easily available on a mouse-click or similar. If you run KDE, you are not going to open a terminal window and type in less /usr/share/doc/xxx/README.Debian, or whatever. F2 then file:/usr/share/doc/pkg or xless /usr/share/doc... or maybe kpackage appear to be the least painful ways to get docs on demand Maybe the Microsoft way of popping up a folder, when installing, with the README file and other important information in, is not such a bad idea after all. This would need to be done through debconf; and probably end up being prioritized so it doesn't pop up unless you choose to see all the config stuff (so it would hardly ever be seen anyways). I did a little work quite awhile back where I was aiming for the syntax, seedocs package-name, with a list of all potential doc files in the package being spit out. I ended up with a scaled down version of kpackage for the core. - Bruce
which is broken, konq or my setup?
Hi, I've been having this problem since purging Karolina's KDE-3.1 and installing those in sid... Konqueror says it can't handle text/html; always when using a file type profile, sometimes even when using the browsing profile. If I (re)load the browsing profile I can access HTML, but end up losing everything I was doing (any tabs and whatever they were opened on). Konq like this is 1/2 as useful as it used too be, and GIT is getting much more use again. I like GIT, but :( Is anyone else seeing this behaviour? - Bruce
Re: Problem with a debian package (lib or not lib ?)
Hi, On Sat, 25 Jan 2003, Fabien Ventro wrote: I have a few problem with one debian package. It isn't currently in debian, but the author a the package provied a debian directory. The package is kbiff (kbiff.sf.net) I managed to build the package, but I have the following errors : Now running lintian... W: kbiff source: dh-make-template-in-source debian/prerm.ex W: kbiff source: dh-make-template-in-source debian/preinst.ex W: kbiff source: dh-make-template-in-source debian/postrm.ex W: kbiff source: dh-make-template-in-source debian/postinst.ex W: kbiff source: dh-make-template-in-source debian/menu.ex no need for dh-make template in Debianized source W: kbiff source: out-of-date-standards-version 3.5.2 Compare the templates in /usr/share/debhelper/dh_make and those which came with kbiff... bring them up to the current standard, re-Debianize, pass the new templates upstream. E: kbiff source: debian-files-list-in-source no need for files list in Debianized source E: kbiff: no-shlibs-control-file usr/lib/kbiff.so E: kbiff: postinst-must-call-ldconfig usr/lib/kbiff.so W: kbiff: postrm-should-call-ldconfig usr/lib/kbiff.so E: kbiff: unparsable-menu-item /usr/lib/menu/kbiff:6 this should get fixed when you bring the Debianization up to date E: kbiff: package-has-a-duplicate-relation xlibs ( 4.1.0), xlibs ( 4.2.0) Finished running lintian. hmmm... For the .ex file, I could remove them, but for the lib, I don't understand ! This package will not provide a library, only an app !For xlibs, I don't understand, too ! ~$ locate kbiff.so /usr/lib/kbiff.so Could someone help me understanding this ? ...it looks like you need to go through the Debian bits in the source, there may be some hard coded stuff that is in conflict with current reality. e.g., does xlibs ( 4.1.0) appear in the source, or is it auto generated when you build based on what libs you have installed, or is both happening. Thank you in advance . HTH - Bruce
Re: k3b
On Sat, 28 Dec 2002, Hendrik Sattler wrote: ... If there are really not packages available anywhere, where can I find exact steps to debianize a KDE program without too much work? Hmmm, dh-make, maybe. Awhile back I got a patch in that broke out the templates used to do a Debianization, KDE was the example template (provided by Ivan Moore) I used. I doubt it has been kept up to date, but it would probably not be too much work to bring it up to spec for the Debian-KDE3 build system. - Bruce
Re: Karolina's KDE 3.1RC5 packages - K Menu Issues...
I have the same problem as Doug (KDE was running when the upgrade happened, ?), plus I can't get cyan on the background (comes out as a blue; 8-bit color on XF336-svga video, ?). On Sat, 28 Dec 2002, Michael Hoodes wrote: I am running unstable KDE 3.1 (dresden w today's updates) and my K menu looks fine as does all the Debian submenus. On Saturday 28 December 2002 01:41 pm, Doug Holland wrote: I just apt-get updated my system today, which fetched a bunch of fresh KDE packages from http://wh9.tu-dresden.de/kde3/karolina, and now I noticed many of the items in my K menu are now gone. Specifically, the Debian menus are now missing, which contained all sorts of stuff. Is there any easy way to get them back?
Re: Fonts in konsole - again
On Fri, 27 Dec 2002, Cajus Pollmeier wrote: Just updated my kde box to kde-3.1.0+rc5+kl-1. All fonts in KDE are correct, except the ones in konsole. All normal fixed fonts get mapped to some Courier style font which can't display graphical characters used i.e. by dselect or mc. I'm editing several font configurations for hours now, but I can't get konsole to display a proper fixed font. Any hints? I'm using xfs-xtt. shrug Works for me, using xfstt and the XF336-svga driver on sid/sarge. Maybe your current or past fiddling has messed something up. Try (guessing): dpkg-reconfigure-ing stuff you've been playing with, take steps (whatever they may be) to force the regeneration of generated files (font directories, aliases, ?). Sorry I can't be more specific; I've never had a problem with fonts which Debian didn't fix before it was annoying enough for me to delve into the matter. HTH - Bruce
