the "clean" target of my
Makefile fixed the issue.
Regards
Ben
On Wed, 2017-11-15 at 20:40 +0100, Benjamin Mesing wrote:
> Hi,
>
> I tried adding the export QT_SELECT statement to the rules file with no
> difference. Also, I tried compiling on another porterbox
> (pa
Hi,
I tried adding the export QT_SELECT statement to the rules file with no
difference. Also, I tried compiling on another porterbox
(partch.debian.org) and everything did compile fine.
I am out of ideas. What do you mean by "ask for a give back".
Any other ideas?
Regards
Ben
On Thu, 2017-11
reproduce the bug? What could be special on the
buildds?
Regards
Ben
On Wed, 2017-11-01 at 16:44 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On 1 November 2017 at 15:04, Benjamin Mesing wrote:
> > Hi Lisandro,
> >
> > thanks for the quick help. I will try this. E
Hi Lisandro,
thanks for the quick help. I will try this. Everything looked fine to
me, because the qt5-moc was used. So, if I understand the fix
correctly, I have to tell the qt5-moc to actually expect qt5 code.
It is a little bit confusing, all my makefile are generated from .pro
files with "qma
Hi Folks (please CC, I am not subscribed),
I ported packagesearch to QT5 due to the removal of QT4. On my machine
everything compiled fine. But when I uploaded the package, almost all
buildds failed to build (except for the amd64 one).
https://buildd.debian.org/status/package.php?p=packagesearch&
Package: sddm
Version: 0.14.0-4
Severity: important
Hi,
for some time, sddm does not start on my system.
sddm.log is empty and daemon.log shows the following message:
Aug 31 18:02:10 xxx systemd[1]: sddm.service: Service hold-off time over,
scheduling restart.
Aug 31 18:02:10 xxx systemd[1]: Sto
Package: kde-workspace
Version: 4:4.11.22-3
Severity: important
Hi,
I dist-upgraded my system to unstable.
Now, when I start into KDE from KDM the "normal" KDE-startup dialog is
shown.
At one point the screen turns black and only the curser is visible.
I have kwin_x11 installed.
What I have t
IMO merely recommending cups-bsd is not a full fix: If one has lpr
installed, cups-bsd won't be installed alongside cups-bsd. As long as
okular _silently_ fails to print in some configurations I would not
consider this bug solved. A simple solution would be to check, if
cupsbsd is available upon pr
unblock 458884 by 458558
thanks
Ok, I will work around the problem in packagesearch then. I still
consider it a very bad decision by QT.
Feel free to close the bug, or tag it wontfix - whatever you like best.
Best regards
Benjamin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Hello,
this bug has cause packagesearch to be removed from testing, due to a
resulting FTBS.
Is anyone working on a fix?
I would hate to see packagesearch not making it into lenny due to this
bug.
Best regards
Benjamin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
Package: libqt4-dev
Version: 4.3.3-2
Severity: normal
When upgrading from 4.3.2 to 4.3.3 I suddenly got loads of linker errors.
Those were occuring because in my plugins .pro file I use the "LIB" template
which now adds the -Wl,--no-undefined option to the linking line.
E.g.:
g++ -Wl,--no-
I've found a bug report for this problem against IceWM.
I do not know if this is a QT or an IceWM bug.
http://sourceforge.net/tracker/index.php?func=detail&aid=1573405&group_id=31&atid=100031
Best regards
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
Package: libqt4-gui
Version: 4.2.1-1
Severity: grave
Justification: renders package unusable
Hello,
when closing a QT4-GUI applications this seems to crash my window manager IceWM.
E.g. all window decorations are lost.
This problem does not occur when running KDE.
I've encountered those crashes
Hello,
attached you find a bug report about a linker error that occured when
building packagesearch.
This build error surfaced only recently (and happens also on i386 and
probably all other architectures) and occurs only on systems with an up
to date set of packages. A diff of a successful and a
Hello
> Both of these bugs you reported were regressions in 4.1.1. Can you test
> the 4.1.2 packages and see if either of these bugs are fixed there?
I am still encountering both bugs.
~> dpkg -l "*qt4*"
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Co
Hello,
any information about wether this bug is reproducable? Any idea if/when
it will be fixed?
It is a showstopper for the upload of my package.
Best regards
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
Package: libqt4-dev
Version: 4.1.1-1
Severity: important
X-Debbugs-Cc: [EMAIL PROTECTED]
Hello,
no PNG-Icons are diplayed in my application (packagesearch).
For example the following code has no effect (used to work before):
QPixmap appIcon("packagesearch.png");
setIcon(appIcon)
Ok, I think I've found the reason for the crashes: packagesearch is
written using dynamic plugins, the dynamic plugins can be compiled with
different setting than the main application.
If I mix debug and release versions (e.g. the plugins in release and the
main application in debug mode) the crash
Forgot to mention, the latter crash happens only in debug mode. The one
reported first in both, debug and release.
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I hit another issue which is probably related. It is triggered by the
setupUi function for a .ui file.
This strongly indicates a QT bug, especially since it said something
about qvariant.cpp
Ben
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1231083840 (LWP 17026)]
0xb
Package: libqt4-dev
Version: 4.1.1-1
Severity: normal
X-Debbugs-Cc: [EMAIL PROTECTED]
Since the update to QT 4.1.1 my application (packagesearch) crashes when
calling qApp->processEvents() in some places, everything worked fine
with QT 4.1.0.
I was not able to reproduce the crash in a small exa
> > So probably libqt4-dev 4.1 should conflict with libqt4-debug <= 4.0.1?
>
> Conflicts with earlier versions are frowned upon in policy (7.3). I
> think the right thing to do would be to split all of the _debug.so
> symlinks into a separate libqt4-debug-dev package. The current scheme
> of lum
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> [...]
An update of libmysqlclient14(-dev) to version 4.1.15-1 solved the
issue.
So maybe libqt4-dev should depend on libmysqlclient14(-dev) >= 4.1.15-1?
Btw. I ha
> I've received a bug report [1] against packagesearch crashing on arch
> i386 (it was reported to work fine on amd64). The backtrace [2]
> indicates that the problem lies within the QT library, and the fact that
> with Qt 4.0.1 everything worked fine seem to support this thesis.
> Therefore I woul
Package: libqt4-dev
merge 346603 346605
thanks
merged due to a duplicated post
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
An update of libqt4-debug to 4.1 (which was still 4.0.1 before) fixed
this issue and brought it down to bug 346586.
So probably libqt4-dev 4.1 should conflict with libqt4-debug <= 4.0.1?
Best regards
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
> Surely this is due to an upgrade to qt4?
The package was successfully compiled against QT 4.0.1 before.
> Try installing/depending on libqt3-headers
I've tried and it wielded no change (it was a linker error in the first
place..).
But when I am at it: Is a dependency on libqt3-headers required?
X-Debbugs-Cc: [EMAIL PROTECTED]
Package: libqt4-dev
Version: 4.1.0-1
Severity: important
Hello,
After an update to the latest QT (from 4.0.1 to 4.1), my package
(packagesearch) fails to build with the following linker errors which I
get in debug mode:
g++ -Wl,-export-dynamic -o packagesearch .ob
Hello,
I've received a bug report [1] against packagesearch crashing on arch
i386 (it was reported to work fine on amd64). The backtrace [2]
indicates that the problem lies within the QT library, and the fact that
with Qt 4.0.1 everything worked fine seem to support this thesis.
Therefore I would
X-Debbugs-Cc: [EMAIL PROTECTED]
Package: libqt4-dev
Version: 4.1.0-1
Severity: important
Hello,
After an update to the latest QT (from 4.0.1 to 4.1), my package
(packagesearch) fails to build with the following linker errors which I
get in debug mode:
g++ -Wl,-export-dynamic -o packagesearch .ob
X-Debbugs-Cc: [EMAIL PROTECTED]
Package: libqt4-dev
Version: 4.1.0-1
Severity: important
Hello,
After an update to the latest QT (from 4.0.1 to 4.1), my package fails to build
with the
following linker errors:
g++ -Wl,-export-dynamic -o packagesearch .obj/main.o .obj/packagesearchimpl.o
.obj/h
> Any idea of how to fix it?
No, sorry. I was only informed by Steve that it seems, that a bug report
should be appropriate.
See http://lists.debian.org/debian-devel/2005/12/msg00447.html for the
thread.
Best regards Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
Package: libqt4-dev
Version: 4.0.1-2
Severity: minor
Hello,
to reduce dependencies between packages, it is suggested to add only
neccessary libraries as linker arguments. Steve Langasek explained the
problems in [1]. Now qmake pulls in loads of unneeded dependencies,
including e.g. libfreetype (-
Package: libqt4-dev
Version: 4.0.0-2
Severity: normal
File: /usr/bin/qmake-qt4
My project contains this:
USE_KDE_LIBS = false
contains(USE_KDE_LIBS, true)
{
message("using USE_KDE_LIBS")
INCLUDEPATH += /usr/include/kde
LIBS += -lkdecore
DEFINES += __USE_KDE_LIBS
}
Package: kdm
Version: 4:3.3.2-1
Followup-For: Bug #263449
Just wanted to note, that for me the problem persists.
I have worked around this issue by removing
-nolisten tcp option.
Greetings Ben (who would love to have the bug voting
feature already :-)
-- System Information:
Debian Release: 3
Package: kate
Version: 4:3.3.2-1
Severity: minor
When using kate or kwrite they flood stdout with lots of
ASSERT: "!m_doc->wrapCursor()" in ../../../kate/part/katerenderer.cpp (626)
messages thereby affecting the performance of the application.
-- System Information:
Debian Release: 3.1
APT pre
Package: kate
Version: 4:3.2.1-1
Severity: wishlist
File: /usr/bin/kwrite
If I have the following situation:
{
int a=0;
// a+=5;
cerr << a <
Package: kate
Version: 4:3.2.1-1
Severity: wishlist
File: /usr/bin/kwrite
If I have the following situation:
{
int a=0;
// a+=5;
cerr << a <
> > Package: konqueror Version: 4:3.2.1-1 Severity: important Tags: sid
>
> > After the upgrade to KDE 3.2 (from 3.1.4) starting konqueror fails
> > with the following output
>
> Have you upgraded kde while a kde session was running ? This is not a
> good idea. Do you still get the crash after
Package: konqueror
Version: 4:3.2.1-1
Severity: important
Tags: sid
After the upgrade to KDE 3.2 (from 3.1.4) starting konqueror fails with
the following output
kdeinit: Shutting down running client.
-
It looks like dcopserver is already running. If you are sure
th
Package: konqueror
Version: 4:3.2.1-1
Severity: important
Tags: sid
After the upgrade to KDE 3.2 (from 3.1.4) starting konqueror fails with the
following output
kdeinit: Shutting down running client.
-
It looks like dcopserver is already running. If you are sure
t
42 matches
Mail list logo
