Bug#476217: psi vs Qt4.4.0-3 segmentation fault
Hi Sune, (Cc: to all the other addresses, because just removing the 3 patches may not give meaningfull results.) On Sun, Jul 06, 2008 at 05:51:24PM +0200, Sune Vuorela wrote: Try on a updated unstable system: apt-get source qt4-x11 open debian/patches/series with your favourite editor and comment the following 3 patches: (add a # at the beginning of the line) 72_generic_arch_atomic_header_fix.diff 73_from4.4.1_no__when_ipv6_disabled.diff 0230-qtextcontrol-selectnextword.diff build. install. test. I just did a similar thing: I did not comment the three patches, but just added a single if(isnan(...)) abort(); for debugging purposes. But now, the segfault doesn't occur any more. AFAICT, there are only two possible explanations: Either the bug doesn't happen with my toolchain (perhaps the compiler version is different than the one used to compile the debian qt package?), or it's some missoptimization by gcc which went away with the additional code line. Next, I'll try it with an unmodified source. If this still 'fixes' the problem, the core of the bug is much more difficult to find. The good news would be, that a simple recompile of qt on an up-to-date system probably would solve (or work around) the segfault. Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476217: psi vs Qt4.4.0-3 segmentation fault
On Mon, Jul 07, 2008 at 11:31:31AM +0200, Jan Niehusmann wrote: I'll try with 4.3.0-5 first, as, according to the changelog-dates, may be the version used to compile the qt packages. Direct comparison shows that the segfault occurs if libQtGui.so is compiled with gcc 4.3.0-5, and it doesn't occur if libQtGui.so is compiled with gcc 4.3.1-1. Therefore I guess this bug is caused by a compiler bug in gcc 4.3.0, and it'll be resolved with the next upload of Qt. Perhaps a proper build-dependency would be good, to assure all buildds use recent enough versions of gcc. Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476217: psi vs Qt4.4.0-3 segmentation fault
On Sun, Jul 06, 2008 at 05:51:24PM +0200, Sune Vuorela wrote: I'm one of the Qt4 maintainers - but I'm not a psi user and have no real clue on how to try/retry this bug, but it would be very nice if some of you had some spare cpu cycles to spend on this problem. As another data point, this bug seems not to be debian specific: On the psi forum, I found a posting where a gentoo user reports exactly the same segmentation fault: http://forum.psi-im.org/thread/4983 Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476217: Bug#485597: psi vs Qt4.4.0-3 segmentation fault
This definitely looks like a qt bug: I just wrote a relatively simple
test program to reproduce it without using psi.
The attached files contain a simple application, which just opens a
window containing a single QTextEditor, and, from a timer, continously
adds '.' characters with the QTextCharFormat::SpellCheckUnderline style.
On my computer, it reproducibly crashes within less than a second.
I hope this helps debugging.
Jan
#include QApplication
#include QLabel
#include QTextCharFormat
#include QTextDocument
#include QTextEdit
#include QTextCursor
#include QColor
#include QTimer
#include main.h
App::App(int argc, char *argv[]) : QApplication(argc,argv) {
tcf = new QTextCharFormat();
tcf-setUnderlineColor(QColor(255,0,0));
tcf-setUnderlineStyle(QTextCharFormat::SpellCheckUnderline);
QTextDocument *document = new QTextDocument();
QTextEdit *hello = new QTextEdit();
hello-setDocument(document);
hello-resize(100, 30);
hello-show();
cursor = new QTextCursor(document);
QTimer *timer = new QTimer(this);
connect(timer, SIGNAL(timeout()), this, SLOT(update()));
timer-start(10);
}
void App::update() {
cursor-insertText(.,*tcf);
}
int main(int argc, char *argv[])
{
App app(argc, argv);
return app.exec();
}
##
# Automatically generated by qmake (2.01a) Mon Jul 7 00:18:03 2008
##
TEMPLATE = app
TARGET =
DEPENDPATH += .
INCLUDEPATH += .
# Input
SOURCES += main.cpp
HEADERS += main.h
CONFIG += qt debug
#include QApplication
#include QLabel
#include QTextCharFormat
#include QTextDocument
#include QTextEdit
#include QTextCursor
#include QColor
#include QTimer
class App : public QApplication
{
Q_OBJECT
public:
App(int argc, char *argv[]);
public slots:
void update();
private:
QTextCharFormat *tcf;
QTextCursor *cursor;
};
Bug#475825: FTBFS: ERROR: could not build a simple Qt program.
I just reproduced this problem. First, I got the following problem: Checking Qt version...no! ERROR: incorrect Qt version found: **Unknown** The **Unknown** strings comes from a call to qmake -query QT_VERSION. This seems to be a problem of qt3: [EMAIL PROTECTED]:/tmp/qbrew-0.4.0$ qmake-qt4 -query QT_VERSION 4.4.0-rc1 [EMAIL PROTECTED]:/tmp/qbrew-0.4.0$ qmake-qt3 -query QT_VERSION **Unknown** Therefore, there are two possibilites to fix this: Either a Build-Conflicts against qt3-dev-tools, or an explicit call to qmake-qt4 instead of just calling qmake. However, as buildds probably don't have qt3-dev-tools installed, this probably is not the cause of the FTBFS bug. So I tried again in a clean changeroot. Here, I got the following error: /usr/bin/ld: cannot find -lfontconfig This can be fixed by adding CONFIG -= link_prl to the .pro files (qbrew.pro as well as the ones dynamically generated by configure.) With the following patch, qbrew builds again inside a clean chroot: diff -ur qbrew-0.4.0.orig/configure qbrew-0.4.0/configure --- qbrew-0.4.0.orig/configure 2008-04-14 20:25:19.0 +0200 +++ qbrew-0.4.0/configure 2008-04-14 20:26:31.0 +0200 @@ -141,6 +141,7 @@ TARGET = config CONFIG += qt $BUILDMODE CONFIG -= app_bundle +CONFIG -= link_prl QT -= gui HEADERS += config.h SOURCES += config.cpp @@ -193,6 +194,7 @@ cat testfunc.pro EOT TARGET = testfunc CONFIG -= app_bundle qt +CONFIG -= link_prl SOURCES += testfunc.cpp EOT $QMAKE testfunc.pro /dev/null 21 diff -ur qbrew-0.4.0.orig/qbrew.pro qbrew-0.4.0/qbrew.pro --- qbrew-0.4.0.orig/qbrew.pro 2008-04-14 20:25:19.0 +0200 +++ qbrew-0.4.0/qbrew.pro 2008-04-14 20:13:49.0 +0200 @@ -5,6 +5,7 @@ TARGET = qbrew TEMPLATE = app CONFIG += qt warn_on +CONFIG -= link_prl QT += xml MOC_DIR = build -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: qca2_2.0.0~beta7-2_i386.changes REJECTED
On Sun, Aug 19, 2007 at 12:50:23PM +, Joerg Jaspert wrote: rejected. The source seems to be duplicated in the qca subdirectory. And This is a known upstream packaging bug. It's reported upstream and so I expect the next beta (or release) version will fix this. I intentionally didn't change the upstream tarball as I prefer unchanged .orig.tar.gz files as long as they don't contain files we can't redistribute. I hope this is not a real blocker - if you really prefer it, I could of course delete the duplication from the upstream tarball. I also miss the source for the apidocs/refman.pdf. This is generated by doxygen directly from the source files, so the qca source is the source for apidocs/refman.pdf. You also want to read http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html and fix your copyright file, there are multiple different licenses and (C) holder not mentioned. You are right, some copyright holders were missing and parts of the source are licensed under BSD-style licenses. I just updated debian/copyright accordingly and will reupload soon. Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318765: libqt4-dev: got broken alternatives symlink for moc
Package: libqt4-dev Version: 4.0.0-1 Severity: minor Compiling a simple test program with qt4 failed with this error message: $ qmake $ make (cd /src/tools/moc make) /bin/sh: line 0: cd: /src/tools/moc: No such file or directory make: *** [/usr/bin/moc] Error 1 The reason is, that I somehow ended up with a broken alternatives symlink for moc: $ ls -al /etc/alternatives/moc lrwxrwxrwx 1 root root 20 Nov 5 2003 /etc/alternatives/moc - /usr/lib/qt2/bin/moc $ ls -al /usr/lib/qt2/bin/moc ls: /usr/lib/qt2/bin/moc: No such file or directory Unfortunately, update-alternatives seems to be unable to correct this: # update-alternatives --config moc There is only 1 program which provides moc (/usr/bin/moc-qt4). Nothing to configure. Of course, the fix is trivial (manually correct the symlink). I have no idea how this happened, but I surely didn't manually mess with the alternatives. Probably some interesting sequence of installs and uninstalls of different versions of qt. If I'm the only one with this problem, just close the report. So, other people with the same symptoms, please speak up ;) Jan -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libqt4-dev depends on: ii libaudio-dev 1.7-2 The Network Audio System (NAS). (d ii libc6-dev2.3.2.ds1-22GNU C Library: Development Librari ii libfreetype6-dev 2.1.10-1FreeType 2 font engine, developmen ii libjpeg62-dev6b-10 Development files for the IJG JPEG ii libmng-dev 1.0.8-1 M-N-G library (Development headers ii libpng12-dev [libpng12-0 1.2.8rel-1 PNG library - development ii libqt4-core 4.0.0-1 Qt 4 core non-GUI functionality ru ii libxcursor-dev 1.1.3-1 X cursor management library (devel ii libxft-dev 2.1.7-1 FreeType-based font drawing librar ii libxrender-dev 1:0.9.0-2 X Rendering Extension client libra ii xlibmesa-gl-dev [libgl-d 6.8.2.dfsg.1-2 Mesa 3D graphics library developme ii xlibmesa-glu-dev [libglu 4.3.0.dfsg.1-14 Mesa OpenGL utility library develo ii xlibs-dev6.8.2.dfsg.1-2 X Window System client library dev ii xlibs-pic6.8.2.dfsg.1-2 X.Org static PIC libraries transit ii zlib1g-dev 1:1.2.2-9 compression library - development Versions of packages libqt4-dev recommends: ii libqt4-gui4.0.0-1Qt 4 core GUI functionality runtim ii qt4-dev-tools 4.0.0-1Qt 4 development tools -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312730: konqueror lockup for no reason
Hi, just for the statistics: I observed this lockup behaviour as well. It seems to happen at random - I don't know a way to reproduce it, although it already happend at least 10 times. Yours, Jan signature.asc Description: Digital signature
