Bug#252366: konsole: fds not closed before execing shell
Package: konsole Version: 4:3.2.2-1 Severity: normal [EMAIL PROTECTED]:~[0]$ ls -l /proc/self/fd total 5 lrwx--1 cesarb cesarb 64 Jun 2 19:38 0 -> /dev/pts/70 lrwx--1 cesarb cesarb 64 Jun 2 19:38 1 -> /dev/pts/70 lrwx--1 cesarb cesarb 64 Jun 2 19:38 2 -> /dev/pts/70 lr-x--1 cesarb cesarb 64 Jun 2 19:38 3 -> /proc/12024/fd lrwx--1 cesarb cesarb 64 Jun 2 19:38 4 -> /dev/dri/card0 This happens within konsole. Looks like it forgot to close all file descriptors before execing the shell (/dev/dri/card0 should not be open on the shell). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.6-flower Locale: LANG=C, LC_CTYPE=en_US.UTF-8 Versions of packages konsole depends on: ii kdelibs4 4:3.2.2-2 KDE core libraries ii libart-2.0-2 2.3.16-5 Library of functions for 2D graphi ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5client library to control the FAM ii libgcc1 1:3.3.3-9 GCC support library ii libice6 4.3.0.dfsg.1-1 Inter-Client Exchange library ii libpng12-01.2.5.0-6 PNG library - runtime ii libqt3c102-mt 3:3.2.3-2 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-1 X Window System Session Management ii libstdc++51:3.3.3-9 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-1 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-1 X Window System event recording an ii xlibs 4.3.0.dfsg.1-1 X Window System client libraries m ii zlib1g1:1.2.1.1-3compression library - runtime -- no debconf information
kdenonbeta/kdedebian/kapture
CVS commit by mornfall: Get rid of KMdi in kapture. We are now using a (sane) mix of KDockWidgets and KTabWidgets. Other than that, i adjusted some column widths in listviews (listtreeview, acqstatus) and changed layout of summaryview slightly (again). M +89 -34kapture/kapture.cpp 1.11 M +52 -70kapture/kapture.h 1.7 M +3 -3 libkapture/acqprogress.cpp 1.15 M +4 -0 libkapture/listtreewidget.cpp 1.7 M +2 -19 libkapture/summaryviewui.ui 1.4
Processed: Re: FW: Bug#248653: Acknowledgement (debian apt-get problems)
Processing commands for [EMAIL PROTECTED]: > reassign 248653 arts Bug#248653: debian apt-get problems Bug reassigned from package `apt' to `arts'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: QT needs new maintainer(s), or at least an NMU
Martin Loschwitz <[EMAIL PROTECTED]> writes: > However, as already said -- I would love to see people help me; I am > thinking of doing a Qt 3.2.x upload to fix at least one of the two > outstanding release critical bugs. Additionally, re-enabling STL is > something one might take into consideration. I (and many others) consider the lack of STL support to be release-critical as well. -- You win again, gravity!
apt-get compatible repository
Hi, it seems finally Debian packages for 3.2.2 have been uploaded, but they're not apt-get compatible: Failed to fetch http://download.kde.org/stable/latest/Debian/dists/stable/main/binary-i386/Packages.gz 404 Not Found Dirk
Bug#252257: krdc: Copy Paste no longer works
Package: krdc Version: 4:3.2.2-1 Severity: normal I am using KRDC to connect to Windows Terminal Server, it appears that normal Copy-Paste procedures between remote host and local host no longer work. In the past I used KRDC with VNC and the copy paste issue didn't occur. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.5 Locale: LANG=C, LC_CTYPE=C Versions of packages krdc depends on: ii kdelibs4 4:3.2.2-2 KDE core libraries ii libart-2.0-2 2.3.16-5 Library of functions for 2D graphi ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an ii libgcc1 1:3.3.3-8 GCC support library ii libice6 4.3.0.dfsg.1-1 Inter-Client Exchange library ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libpng12-01.2.5.0-6 PNG library - runtime ii libqt3c102-mt 3:3.2.3-2 Qt GUI Library (Threaded runtime v ii libslp1 1.0.11-7 OpenSLP libraries ii libsm64.3.0.dfsg.1-1 X Window System Session Management ii libssl0.9.7 0.9.7d-2 SSL shared libraries ii libstdc++51:3.3.3-8 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-1 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-1 X Window System client libraries m ii zlib1g1:1.2.1.1-3compression library - runtime -- no debconf information
Bug#252249: kde and other kde packages have dependency problems
Package: kde Severity: normal Whenever I do an "apt-get install kde" or kdm or kdanything I get kdm: Depends: kdelibs4 (>= 4:3.2.2) but it is not going to be installed Depends: kdebase-bin but it is not going to be installed i've tried installing kdelib4 but I get a message that it's been replaced by another package (something like libcupsys, I could find it in my terminal). I do an apt-get install libcupsys and it installs but I still get the same dependency errors and I'm stuck. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.6-1-k7 Locale: LANG=C, LC_CTYPE=C
Re: QT needs new maintainer(s), or at least an NMU
Tuesday 01 June 2004 20:19, Martin Loschwitz rašė: > As far as I am concerned, KDE 3.2 is still not officially certified for > running with Qt 3.3, is it? Hm... I saw some incidents with Qt 3.3 and KDE 3.2 somewhere on the web. But why shouldn't we ask on KDE mailing lists? > Anyway, Qt 3.3 should not go into Sarge, I think. I share your opinion. I know nothing about Sarge release plans and I'm really afraid Qt 3.3 and Qt 3.3 linked KDE just won't catch the train. > However, as already said -- I would love to see people help me; I am > thinking of doing a Qt 3.2.x upload to fix at least one of the two > outstanding release critical bugs. Additionally, re-enabling STL is > something one might take into consideration. (running in circles and screaming "Thank you! Thank you!") :) Now seriously. How can I help? -- Marius Žalinauskas
