pkg-kde: commit - rev 18 - tags/packages/kdenetwork
Author: ccheney Date: 2004-01-28 03:47:40 +0100 (Wed, 28 Jan 2004) New Revision: 18 Added: tags/packages/kdenetwork/kdenetwork-3.1.95-1/ Log: Tagging kdenetwork 3.1.95-1. Copied: tags/packages/kdenetwork/kdenetwork-3.1.95-1 (from rev 17, trunk/packages/kdenetwork)
Re: simplifying & enhancing kde manpages
On Tue, Jan 27, 2004 at 10:17:34PM +0100, Achim Bohnet wrote:
> Hi,
>
> looking at the kde man pages I note that the qt and kde standrd options
> are more or less listed and described. Often they hide the actual
> funtionality of the program. There's a good reason for --help-{qt,kde,all}
> and not just --help listing everything ;)
>
> My idea now was now to create a
> kde-options(?) manpage^Wsgml that describes the generic kde and
> qt options (later maybe in more detail). From all other manpages
> just use a reference to this manpage.If possible one could
> even create templates in kdelibs-dev that are included and allow to
> change these generic parts of each kde manpage at a central
> place.
>
> Does this sound reasonable?
Sounds good to me.
> Anyone knows a kde manpage that has a complete or maybe more
> in depth description of the standard options? Otherwise I would
> use kde-config.sgml as a start for kde-options.
Not sure about this...
> Btw. is there a script that generates from a --help ouput an sgml
> manpage skeleton?
I just manually did it for the manpages that are out there so far. There
is an example sgml manpage skeleton with nothing in it in the dh-make
package.
Chris
signature.asc
Description: Digital signature
Re: simplifying & enhancing kde manpages
Achim Bohnet writes: > My idea now was now to create a kde-options(?) manpage^Wsgml that > describes the generic kde and qt options (later maybe in more > detail). From all other manpages just use a reference to this > manpage. If possible one could even create templates in kdelibs-dev > that are included and allow to change these generic parts of each > kde manpage at a central place. > Does this sound reasonable? It does to me. It's great that you are going to work on the KDE program manpages. Especially for command line utilities like dcop*, this would be really useful. > Btw. is there a script that generates from a --help ouput an sgml > manpage skeleton? I wrote a script that generates nroff manpage code directly once. It's currently in kdesdk/scripts/kdemangen.pl. cheers domi
Bug#230006: kdelibs-bin: konqueror reports "Could not start process Can't talk to klauncher"
On Tue, Jan 27, 2004 at 11:03:39PM +0100, Adeodato Sim? wrote: > * Grant Grundler [Tue, 27 Jan 2004 13:44:15 -0800]: > > > Trying to start konqueror, I get: > > Could not start process Can't talk to klauncher > > > Sorry, I have no clue how to even begin debugging this problem. > > Konqueror has been working I ran "apt-get upgrade" last week. > > I try to upgrade the system about every week. > > Does it happen if you run KDE as a new user (i.e., empty ~/.kde)? > Or, if you can't/prefer not to create a new user, does it happen if > you temporarily move your ~/.kde somewhere else? I created a new user (kdetest) and it worked fine! What next? thanks, grant [EMAIL PROTECTED]:~# su - kdetest [EMAIL PROTECTED]:~$ konqueror konqueror: cannot connect to X server [EMAIL PROTECTED]:~$ export DISPLAY=:0 [EMAIL PROTECTED]:~$ konqueror Creating link /home/kdetest/.kde/socket-debian. Created link from "/home/kdetest/.kde/socket-debian" to "/tmp/ksocket-kdetest" _KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root iceauth: creating new authority file /home/kdetest/.ICEauthority QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used Creating link /home/kdetest/.kde/tmp-debian. Created link from "/home/kdetest/.kde/tmp-debian" to "/tmp/kde-kdetest" QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used kbuildsycoca running... File kio_httprc, id kioslave.upd:kde2.2/r1 File kioslaverc, id kioslave.upd:kde2.2/r1 File kio_httprc, id kioslave.upd:kde2.2/r2 File kioslaverc, id kioslave.upd:kde2.2/r3 File kdeglobals, id kded.upd:kde3.0 File kcookiejarrc, id kcookiescfg.upd:kde2.2/b1 File kcookiejarrc, id kcookiescfg.upd:kde3.1/cvs File kdeprintrc, id kdeprintrc.upd:kde-3.1-toolbar File dummy, id favicons.upd:kde3 File kdeglobals, id kaccel.upd:kde3.1/r3 File kcmdisplayrc, id kcmdisplayrc.upd:kde3 File kdeglobals, id socks.upd:kde3.0/r1 Running script 'useragent.pl' Script: Writing entries to /tmp/kde-kdetest/kconf_updatezX2nOa.tmp Script: Filtered entries written to /tmp/kde-kdetest/kconf_update928Kaa.tmp Running script 'proxytype.pl' Script: Writing entries to /tmp/kde-kdetest/kconf_updatelief6a.tmp Script: Filtered entries written to /tmp/kde-kdetest/kconf_update7qnQmb.tmp Write ViewMenuBar -> false Remove Key 'General'/'ViewToolBar' Running script 'move_favicons.sh' Script: Writing entries to /tmp/kde-kdetest/kconf_updateLBV7Db.tmp Script: Filtered entries written to /tmp/kde-kdetest/kconf_updateDJOqha.tmp Running script 'convertShortcuts.pl' Script: Writing entries to /tmp/kde-kdetest/kconf_updatetOi9Ga.tmp Script: Filtered entries written to /tmp/kde-kdetest/kconf_updateZzBkac.tmp WARNING: Can't open /home/kdetest/.kde/share/apps/konqueror/bookmarks.xml kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found QPixmap: Cannot create a QPixmap when no GUI is being used QPixmap: Cannot create a QPixmap when no GUI is being used kbuildsycoca running...
kdenonbeta/kdedebian/kapture
CVS commit by mornfall: - DROP KDE 3.1 SUPPORT (it's quite simple to bring it back, just you'll have to hack the auto* files a bit). However, it's a nightmare to maintain with regards to kmdi. - update TODO - slight code reformatting (add more folding, etc) - implement debtags interface in libcapture (save the pointers to OpSet holding the tagset in the PkgCache::ExtState), add tag loading to PkgManager - create debtags (tagexpr) filter - scrap ::registerFactory (), add macro (MAKE_GROUPER_FACTORY) to make ::factory definition shorter - disable most of debug code in pkgcache.cpp, move the selection printing to pkgcache-test.cpp - fix the problem with (unwanted) postfix bumping wanted priority of netbase - reduce code duplication in pkgcache.cpp - rename some filters to reflect that they act on packages (add Pkg prefix) - add tag display to PkgDetailsDetails CCMAIL: [EMAIL PROTECTED] Alibcapture/tagcollbuilder.cpp 1.1 [LGPL] Alibcapture/tagcollbuilder.h 1.1 [LGPL (v2+)] M +1 -4 Makefile.am 1.3 M +2 -5 README 1.5 M +62 -8 TODO 1.9 M +2 -3 configure.in.in 1.4 M +1 -1 kapture/Makefile.am 1.10 M +2 -2 libcapture/Makefile.am 1.6 M +1 -0 libcapture/feeder.h 1.3 M +72 -68libcapture/filters.cpp 1.2 M +16 -3 libcapture/filters.h 1.2 M +77 -82libcapture/grouper.cpp 1.4 M +2 -1 libcapture/grouper.h 1.4 M +19 -0 libcapture/pkgcache-test.cpp 1.4 M +69 -74libcapture/pkgcache.cpp 1.4 M +33 -22libcapture/pkgcache.h 1.4 M +74 -2 libcapture/pkgmanager.cpp 1.5 M +15 -3 libcapture/pkgmanager.h 1.5 M +1 -1 libkapture/Makefile.am 1.6 M +3 -1 libkapture/acqprogress.cpp 1.2 M +6 -6 libkapture/acqprogress.h 1.3 M +1 -1 libkapture/kapturemanager.cpp 1.5 M +9 -0 libkapture/pkgdetailsdetails.cpp 1.2 M +68 -34libkapture/pkgdetailsdetailsui.ui 1.2 M +7 -3 libkapture/pkglistview.cpp 1.4 M +1 -1 part/Makefile.am 1.5
Re: simplifying & enhancing kde manpages
> My idea now was now to create a > kde-options(?) manpage^Wsgml that describes the generic kde and > qt options (later maybe in more detail). From all other manpages > just use a reference to this manpage. FWIW, I think this is an excellent idea. Ben.
Bug#230006: kdelibs-bin: konqueror reports "Could not start process Can't talk to klauncher"
* Grant Grundler [Tue, 27 Jan 2004 13:44:15 -0800]: > Trying to start konqueror, I get: > Could not start process Can't talk to klauncher > Sorry, I have no clue how to even begin debugging this problem. > Konqueror has been working I ran "apt-get upgrade" last week. > I try to upgrade the system about every week. Does it happen if you run KDE as a new user (i.e., empty ~/.kde)? Or, if you can't/prefer not to create a new user, does it happen if you temporarily move your ~/.kde somewhere else? -- Adeodato Simó (a.k.a. thibaut) EM: asp16 [ykwim] alu.ua.es | IM: my_dato [jabber.org] | PK: DA6AE621 signature.asc Description: Digital signature
Bug#230006: kdelibs-bin: konqueror reports "Could not start process Can't talk to klauncher"
Package: kdelibs-bin Version: 4:3.1.5-1 Severity: important Trying to start konqueror, I get: Could not start process Can't talk to klauncher grundler <503>konqueror kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found konqueror: ERROR: ERROR 3: couldn't create slave : Can't talk to klauncher ASSERT: "m_widget" in ../../kdeui/kaction.cpp (2993) ASSERT: "m_widget" in ../../kdeui/kaction.cpp (2993) grundler <504> Sorry, I have no clue how to even begin debugging this problem. Konqueror has been working I ran "apt-get upgrade" last week. I try to upgrade the system about every week. thanks grant -- System Information: Debian Release: testing/unstable Architecture: hppa Kernel: Linux debian 2.4.23-pa1 #1 Mon Dec 1 20:36:24 PST 2003 parisc Locale: LANG=C, LC_CTYPE=C Versions of packages kdelibs-bin depends on: ii kdelibs4 4:3.1.5-1 KDE core libraries ii libart-2.0-2 2.3.16-1 Library of functions for 2D graphi ii libarts1 1.1.5-2 aRts Sound system ii libasound2 0.9.8-2 Advanced Linux Sound Architecture ii libaudio2 1.6b-1The Network Audio System (NAS). (s ii libaudiofile0 0.2.3-4 The Audiofile Library ii libbz2-1.0 1.0.2-1 A high-quality block-sorting file ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libcupsys2 1.1.20final-3 Common UNIX Printing System(tm) - ii libfam0c1022.6.10-6 client library to control the FAM ii libfontconfig1 2.2.1-13 generic font configuration library ii libfreetype6 2.1.7-1.1 FreeType 2 font engine, shared lib ii libgcc11:3.3.3-0pre2 GCC support library ii libmad00.15.0b-3 MPEG audio decoder library ii libogg01.1.0-1 Ogg Bitstream Library ii libpng12-0 1.2.5.0-4 PNG library - runtime ii libqt3c102-mt 3:3.2.3-2 Qt GUI Library (Threaded runtime v ii libstdc++5 1:3.3.3-0pre2 The GNU Standard C++ Library v3 ii libvorbis0a1.0.1-1 The Vorbis General Audio Compressi ii libvorbisenc2 1.0.1-1 The Vorbis General Audio Compressi ii libvorbisfile3 1.0.1-1 The Vorbis General Audio Compressi ii libxcursor11.0.2-4 X Cursor management library ii libxft22.1.2-5 FreeType-based font drawing librar ii libxml22.6.3-1 GNOME XML library ii libxrender10.8.3-5 X Rendering Extension client libra ii libxslt1.1 1.1.2-3 XSLT processing library - runtime ii netpbm 2:10.0-1 Graphics conversion tools ii python 2.3.3-5 An interactive high-level object-o ii xlibmesa3-gl [libgl1] 4.2.1-12.1Mesa 3D graphics library [XFree86] ii xlibs 4.2.1-14 X Window System client libraries ii zlib1g 1:1.2.1-3 compression library - runtime -- no debconf information
simplifying & enhancing kde manpages
Hi,
looking at the kde man pages I note that the qt and kde standrd options
are more or less listed and described. Often they hide the actual
funtionality of the program. There's a good reason for --help-{qt,kde,all}
and not just --help listing everything ;)
My idea now was now to create a
kde-options(?) manpage^Wsgml that describes the generic kde and
qt options (later maybe in more detail). From all other manpages
just use a reference to this manpage.If possible one could
even create templates in kdelibs-dev that are included and allow to
change these generic parts of each kde manpage at a central
place.
Does this sound reasonable?
Anyone knows a kde manpage that has a complete or maybe more
in depth description of the standard options? Otherwise I would
use kde-config.sgml as a start for kde-options.
Btw. is there a script that generates from a --help ouput an sgml
manpage skeleton?
Achim
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- [EMAIL PROTECTED]
Bug#229990: konsole 2.2.2-14.7: deleting a letter crashes konsole
Package: konsole Version: 2.2.2-14.7 $ setxkbmap hu $ konsole kdecore (KLocale): WARNING: found no definition of PluralForm -- Now in the new konsole window, type: tét Then press Ctrl+A, and Delete (to delete the first letter of the word). The konsole window will disapear. The letter "é" is located in the hungarian keyboard at: asdfghjklé konsole depends on the following packages: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii kdelibs3 2.2.2-13.woody.8 KDE core libraries (runtime files) ii libc62.2.5-11.5 GNU C Library: Shared libraries and Timezone dat ii libfam0 2.6.6.1-5.2 client library to control the FAM daemon ii libjpeg626b-5 The Independent JPEG Group's JPEG runtime librar ii libpng2 1.0.12-3.woody.3 PNG library - runtime ii libqt2 2.3.1-22 Qt GUI Library (runtime version). ii libstdc++2.10-gl 2.95.4-11woody1 The GNU stdc++ library ii xlibs4.1.0-16woody1 X Window System client libraries ii zlib1g 1.1.4-1.0woody0 compression library - runtime ii kdebase-libs 2.2.2-14.7 KDE libraries and modules for kdebase ii xfonts-base 4.1.0-16woody1 standard fonts for X ii xutils 4.1.0-16woody1 X Window System utility programs $ uname -a Linux nemeth 2.4.20 #1 Fri Nov 21 20:41:15 CET 2003 i686 unknown NMarci
Bug#194248: lo interface
I've seen this if the lo interface is not up in KDE. =a= -- === Aaron Straus [EMAIL PROTECTED]
pkg-kde: commit - rev 16 - tags/packages/kdemultimedia
Author: ccheney Date: 2004-01-27 10:35:14 +0100 (Tue, 27 Jan 2004) New Revision: 16 Added: tags/packages/kdemultimedia/kdemultimedia-3.1.95-1/ Log: Tagging kdemultimedia 3.1.95-1. Copied: tags/packages/kdemultimedia/kdemultimedia-3.1.95-1 (from rev 15, trunk/packages/kdemultimedia)
Bug#229665: kmail: After downloading the first mail, KMail uses100% CPU and does nothing.
olberd writes: > Domi writes: >> Rune Schjellerup writes: >> >>> The bug is reproducible, as long as I have this mail in my mailbox >>> KMail halts... >> >> We would need the exact mail with all headers and everything. >> Saving it to a file would be best... > Well I did some ekstra work to ensure that this was the mail causing > the problem. I downloaded the mail using ftp and put it in a > Maildir on my hdd. Then I added that Maildir to KMail. The second I > press "check for new mail" KMail freezes. Great ! > I have attached the mail in question. You seem to have forgotten the attachment :) cheers domi
Bug#229665: kmail: After downloading the first mail, KMail uses100% CPU and does nothing.
Domi writes: > Rune Schjellerup writes: > >> The bug is reproducible, as long as I have this mail in my mailbox >> KMail halts... > > We would need the exact mail with all headers and everything. > Saving it to a file would be best... Well I did some ekstra work to ensure that this was the mail causing the problem. I downloaded the mail using ftp and put it in a Maildir on my hdd. Then I added that Maildir to KMail. The second I press "check for new mail" KMail freezes. I have attached the mail in question. Rune Schjellerup
Re: Consider building ksysguardd without libsensors support for now?
On Mon, Jan 26, 2004 at 02:42:26PM -0600, Chris Cheney wrote: > On Mon, Jan 26, 2004 at 05:43:07PM +, Colin Watson wrote: > > Probably the biggest task remaining for sarge as I see it is getting > > meta-kde and all its dependencies ready. Now, I know there are various > > build issues and things, most of which seem to be finally crawling > > towards resolution, but one thing that currently looks like a > > showstopper is that ksysguardd (and indirectly ksysguard) depend on > > libsensors2, and lm-sensors is having major problems getting itself > > ready for sarge which have been discussed quite extensively on > > debian-devel without resolution, and which seem to be fairly intractable > > at the moment. > > The various build issues are not coming any closer to being resolved. Or > at least don't look that way to me. The incompetent buildd admins are > still around and still have not retried builds they should never have > failed in the first place (all the g++ related ones). If I were you, in future, I'd use a versioned Build-Depends: to make sbuild automatically upgrade g++, or at the very least a Build-Conflicts: on the problematic versions. Looking through the wanna-build states, every build that's maybe-failed for this reason is in state Building, not Failed. The builds may not actually have happened yet, but the buildd maintenance looks reasonable to me. > > I notice that the lm-sensors dependency is i386-specific, so presumably > > it's just an optional feature. I'd really like to remove this roadblock > > so that we can get on with other things, and maybe put it back later if > > and when lm-sensors gets sorted out. Would you consider building > > ksysguardd without lm-sensors support for now? > > The lm-sensors problem with kdebase is minor compared to all the other > problems KDE has currently, but yes once the other problems are resolved > if lm-sensors is still an issue I will upload a version of kdebase with > no dependency on lm-sensors. I think it's fairly clear that it will still be an issue, and the reason I brought it up now is that there's no point waiting for builds of kdebase when the current version clearly isn't going to get into testing any time soon ... I'm trying to get problems resolved in parallel rather than in series. Cheers, -- Colin Watson [EMAIL PROTECTED]
Bug#210606: sorry for not responding
yes, this bug is resolved.
