Bug#359197: konqueror crashes. No specific reason. Backtrace attached.
Package: konqueror Version: 4:3.5.1-1 Severity: normal I was working on files I was browsing on konqueror. With no apparent reason, konqueror crashed. Find attached a backtrace dump. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.4-p4s Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages konqueror depends on: ii kcontrol 4:3.5.1-1 control center for KDE ii kdebase-kio-plugins 4:3.5.1-1 core I/O slaves for KDE ii kdelibs4c2a 4:3.5.1-2 core libraries for all KDE applica ii kdesktop 4:3.5.1-1 miscellaneous binaries and files f ii kfind 4:3.5.1-1 file-find utility for KDE ii libacl1 2.2.35-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.31-1 Extended attribute shared library ii libaudio2 1.7-5 The Network Audio System (NAS). (s ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libfam0 2.7.0-9Client library to control the FAM ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.3-1 GCC support library ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libidn11 0.5.18-2 GNU libidn library, implementation ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libkonq4 4:3.5.1-1 core libraries for Konqueror ii libpng12-01.2.8rel-5 PNG library - runtime ii libqt3-mt 3:3.3.5-4 Qt GUI Library (Threaded runtime v ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libstdc++64.0.3-1The GNU Standard C++ Library v3 ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxcursor1 1.1.3-1X cursor management library ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxi66.9.0.dfsg.1-4 X Window System Input extension li ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display ii libxrandr26.9.0.dfsg.1-4 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii zlib1g1:1.2.3-11 compression library - runtime konqueror recommends no packages. -- no debconf information (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234257248 (LWP 7959)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (
Bug#359219: kdelibs-bin: no manpage for /usr/bin/ghns
Package: kdelibs-bin Version: 4:3.3.2-6.4 Severity: wishlist Nothing much to add to the subject really. I discovered ghns whilst command-completing "gh" to see if I had the glasgow haskell compiler installed, I ended up with ghns. "man ghns" to find it what it was, but there is no manpage. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-jmtd Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages kdelibs-bin depends on: ii kdelibs4 4:3.3.2-6.4 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libbz2-1.0 1.0.2-7 high-quality block-sorting file co ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcupsys2-gnutls1 1.1.23-10sarge1 Common UNIX Printing System(tm) - ii libfam0c1022.7.0-6sarge1 client library to control the FAM ii libfontconfig1 2.3.1-2 generic font configuration library ii libgcc11:3.4.3-13GCC support library ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxft22.1.7-1 FreeType-based font drawing librar ii libxml22.6.16-7 GNOME XML library ii libxrender10.8.3-7 X Rendering Extension client libra ii libxslt1.1 1.1.12-8 XSLT processing library - runtime ii menu-xdg 0.2 freedesktop.org menu compliant win ii netpbm 2:10.0-8sarge2Graphics conversion tools ii perl 5.8.4-8sarge3 Larry Wall's Practical Extraction ii python 2.3.5-2 An interactive high-level object-o ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359246: kmailcvt should probably depend on corresponding version of kmail
Package: kmailcvt Version: 4:3.4.3-1 Severity: minor I have set my preferred distribution to etch but have forced in some packages from sid, among them kmail. Kmailcvt 3.4.3-1 fails (somewhat unsurprising) to communicate with Kmail 3.5.1 over DCOP (producing one message box per mail). Upgrading Kmailcvt to 3.5.1-2 fixes that problem. If Kmailcvt is supposed to work across versions, let me know and I'll improve the bug report. -- Magnus Holmgren [EMAIL PROTECTED] -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (90, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-proffe1 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Versions of packages kmailcvt depends on: ii kdelibs4c2a 4:3.5.1-4 core libraries for all KDE applica ii kmail 4:3.5.1-1 KDE Email client ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libgcc1 1:4.0.3-1 GCC support library ii libqt3-mt 3:3.3.5-4 Qt GUI Library (Threaded runtime v ii libstdc++64.0.3-1The GNU Standard C++ Library v3 kmailcvt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359262: kmail: Allow to block some attachment types
Package: kmail Version: 1.9.1 Severity: wishlist *** Please type your report below this line *** Hi, Its important for security reasons to be able to block by default some attachment files. For an example, please check this http://www.exchangefaq.org/faq/Exchange-5.5/Martin-Blackstone's-List-of-Danger/sectionID/1017 Best regards, Mohammad -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 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]
KDE cdbs files
I noticed that the KDE maintainers keep their own patched copies of some of the cdbs files. I'm integrating the uuencoded patch support now, which should take care of the fork of simple-patchsys.mk. The files debian-qt-kde.mk and kde.mk, however, seem to have quite a bit of extra code in there that I don't fully understand. Does anyone want to undertake explaining this stuff to me and declaring it fit for general use so it can be merged with "upstream" cdbs? In particular, what's supposed to be the difference between those two files? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE cdbs files
Le Lun 27 Mars 2006 19:33, Peter Eisentraut a écrit :
> I noticed that the KDE maintainers keep their own patched copies of
> some of the cdbs files. I'm integrating the uuencoded patch support
> now, which should take care of the fork of simple-patchsys.mk. The
> files debian-qt-kde.mk and kde.mk, however, seem to have quite a bit
> of extra code in there that I don't fully understand. Does anyone
> want to undertake explaining this stuff to me and declaring it fit
> for general use so it can be merged with "upstream" cdbs? In
> particular, what's supposed to be the difference between those two
> files?
first of all, that's great news :)
if I look at our kde.mk compared to the cdbs one, trhough vimdiff, there
is mostly 4 diffs.
1st block:
DEB_BUILDDIR is used to compile the package outside from the sources.
we add support for it when the packaging uses the 'tarball in the
tarball' approach. (used by kdepim)
2nd block:
use standard ${libdir} ... instead of /usr/lib, ...
I suppose this is useful to create package of KDE that cohabit with
official ones (like KDE HEAD packages). I'm not sure this has to go in
cdbs kde.mk
3rd block:
--enable-debug is not correct, --enable-debug=yes is.
I can't remember why --disable-debug has to be forced else, maybe
someone else can say why.
4th block:
DEB_COMPRESS_EXCLUDE need more extensions, especially needed for KDE
docs.
and then a block is appended, aka apidox related block, it's used to
generate API documentations using doxygen and graphiz. if
DEB_KDE_APIDOX is non empty, then API dox are generated, which is not
default in kde upstream packages.
==
debian-qt-kde.mk are things we often do in our packages, but that are
not meant to be merged (in our opinions) into kde.mk
it contains usual common settings (like the fact that we build all our
packages with ENABLE-FINAL mode on).
we also have our own DEB_DH_MAKESHLIBS_ARGS_ALL and related hacks. Maybe
your recent commit will permit us to reduce that, I've not investigated
more than that atm, so I just cannot say.
bits of code contain (in order of appearance):
line 10-17 and 88-97:
small bit of code that autogenerate configure and friends from
admin/Makefile.common.
--> it's used for packages that use the tarball in the tarball
approach, and that need relibtoolization of the package.
we usually do that at packaging time, but kdepim cannot do that
because of the tarball in the tarball approach, and
re-libtoolization is done at build time.
the process is controlled by the DEB_KDE_CVS_MAKE variable.
--> it's also used for packages that do not have configure and friends
to generate them.
==> I personnaly don't like that, because it puts quite a lot of
burden on the buildds and that it can generate unpredictable
behaviour. I'm not in favor of inclusion into kde.mk
not meant to go into kde.mk, I think it's only used for kdepim and
tarball because sometimes it's
admin/Makefile.cvs or another one. THough, as it has to be called
*BEFORE* inclusion of autotools.mk, we prefer to have it here.
line 28-39:
code we use to generate man pages from sgml templates:
every debian/man/*.sgml is converted into debian/man/out/*.man[1-9]
guessing the man section from the generated man page.
--> it's a cool hack (IMHO), but do not belong to kde.mk at all, it's
a problem that is more general than that.
line 40-56:
this hack is used to guess the KDE version we are packaging (e.g.
3.4.2 atm). this is used for some substvars we use in kde packaging,
to tighten some dependencies.
--> has no sense out of the KDE official modules.
line 58-62:
clean of our hacks
line 64-86:
generate HTML docks from applications doocbooks.
--> I don't know if it could go in kde.mk or not. maybe other members
of the team may have more insight on this.
=
sorry for the very long answer, I hope the other will be able to fill
the gaps I've left, and that you can sort that a bit out ;)
PS: all of that work is on svn.debian.org, in the pkg-kde repository:
under svn(+ssh)://pkg-kde/trunk/, you'll find :
* cdbs/ (our cdbs-like own files)
* packages/$pkg/debian : debian/ directory for package $pkg
* common-patches/ are patches applied to every sources, and you
don't really care about them
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpE3fjEagj4q.pgp
Description: PGP signature
Re: KDE cdbs files
Le Lun 27 Mars 2006 20:53, Pierre Habouzit a écrit : > Le Lun 27 Mars 2006 19:33, Peter Eisentraut a écrit : > > I noticed that the KDE maintainers keep their own patched copies of > > some of the cdbs files. I'm integrating the uuencoded patch > > support now, which should take care of the fork of > > simple-patchsys.mk. The files debian-qt-kde.mk and kde.mk, > > however, seem to have quite a bit of extra code in there that I > > don't fully understand. Does anyone want to undertake explaining > > this stuff to me and declaring it fit for general use so it can be > > merged with "upstream" cdbs? In particular, what's supposed to be > > the difference between those two files? > [...] > not meant to go into kde.mk, I think it's only used for kdepim and > tarball because sometimes it's > admin/Makefile.cvs or another one. THough, as it has to be > called *BEFORE* inclusion of autotools.mk, we prefer to have it here. > this is garbage in my mail, sorry. > line 64-86: in fact it's line 75-86 > generate HTML docks from applications doocbooks. > > --> I don't know if it could go in kde.mk or not. maybe other > members of the team may have more insight on this. and I forgot: line 64-73: two hacks in one. * we have our packaging system handle debian/$(pkg).lintian as the lintian overrides for the package. * we do the same for debian/$(pkg).presubj for the reportbug $(pkg) presubj magic files. both are quite useful (especially the first one) IMHO deserve to be integrated in cdbs, but is really more general than kde.mk sorry for those two errors in my previous mail. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpbe3fcXkQaV.pgp Description: PGP signature
Bug#358972: Icons available for application compiled with 4.1.0
I wanted to add, that in packagesearch compiled with 4.1.0 the icons are displayed fine even with an installed QT 4.1.1. So it must be something in the development library. Best regards Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
