Processed: Re: Bug#801096: qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu
Processing control commands: > tags -1 - moreinfo Bug #801096 [qt5-qmake] qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu Removed tag(s) moreinfo. -- 801096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801096: qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu
Control: tags -1 - moreinfo On 09.10.2015 03:05, Lisandro Damián Nicanor Pérez Meyer wrote: tag 801096 moreinfo thanks Hi Matthias! On Tuesday 06 October 2015 11:56:31 Matthias Klose wrote: Package: qmake-qt5 Version: 5.4.2+dfsg-2 Severity: important this is seen when building openjfx on arm64: https://launchpadlibrarian.net/220388096/buildlog_ubuntu-wily-arm64.openjfx_ 8u60-b27-0ubuntu1_BUILDING.txt.gz Well, the first thing to note here is that you are filing a bug against the Debian package using an Ubuntu build. Maybe you fired reportbug on the wrong machine? at this time there was no Debian build. So please don't speculate. You can now reproduce this by disabling the 12-generic-qmake-spec.patch. build.gradle chooses to set the linux-g++-m64 spec, That's wrong, it should be using linux-g++ on aarch64. Moreover I don't understand why it's chossing a specific mkspec, that's selected at Qt5 build time and should be respected. why shipping a spec which is wrong in the first place? and then fails on the unknown -m64 option. Trying to use the linux-g++ option fails, because the qplatformdefs.h of this spec is basically empty. This file is identical for the -m32 and -m64 specs, so why not include it there? It's identical, and sourced from mkspecs/linux-g++-64/qmake.conf [diff]. Look at the final lines, full diff included for verbosity. fine, but why then ship a file which can't be used by design? Marking this bug as moreinfo until we sort out the Ubuntu stuff :) done.
Processed: Re: qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu
Processing commands for cont...@bugs.debian.org: > tag 801096 moreinfo Bug #801096 [qt5-qmake] qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 801096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801096: qtmake's linux-g++-m64 spec sets -m64 on aarch64-linux-gnu
tag 801096 moreinfo thanks Hi Matthias! On Tuesday 06 October 2015 11:56:31 Matthias Klose wrote: > Package: qmake-qt5 > Version: 5.4.2+dfsg-2 > Severity: important > > this is seen when building openjfx on arm64: > https://launchpadlibrarian.net/220388096/buildlog_ubuntu-wily-arm64.openjfx_ > 8u60-b27-0ubuntu1_BUILDING.txt.gz Well, the first thing to note here is that you are filing a bug against the Debian package using an Ubuntu build. Maybe you fired reportbug on the wrong machine? > build.gradle chooses to set the linux-g++-m64 spec, That's wrong, it should be using linux-g++ on aarch64. Moreover I don't understand why it's chossing a specific mkspec, that's selected at Qt5 build time and should be respected. > and then fails on the > unknown -m64 option. Trying to use the linux-g++ option fails, because the > qplatformdefs.h of this spec is basically empty. This file is identical for > the -m32 and -m64 specs, so why not include it there? It's identical, and sourced from mkspecs/linux-g++-64/qmake.conf [diff]. Look at the final lines, full diff included for verbosity. Marking this bug as moreinfo until we sort out the Ubuntu stuff :) [diff] --8<-- [diff] --8<-- [diff] --8<-- [diff] --8<-- [diff] --8<-- (qtbase src's root dir)$ diff -Naur mkspecs/linux-g++/ mkspecs/linux-g++-64/ diff -Naur mkspecs/linux-g++/qmake.conf mkspecs/linux-g++-64/qmake.conf --- mkspecs/linux-g++/qmake.conf2014-03-17 23:24:06.270583408 -0300 +++ mkspecs/linux-g++-64/qmake.conf 2014-03-17 23:24:06.270583408 -0300 @@ -1,12 +1,23 @@ # # qmake configuration for linux-g++ # +# Written for GNU/Linux platforms that have both lib and lib64 directories, +# like the AMD Opteron. +# MAKEFILE_GENERATOR = UNIX CONFIG += incremental QMAKE_INCREMENTAL_STYLE = sublib +QMAKE_CFLAGS= -m64 +QMAKE_LFLAGS= -m64 + include(../common/linux.conf) include(../common/gcc-base-unix.conf) include(../common/g++-unix.conf) + + +QMAKE_LIBDIR_X11= /usr/X11R6/lib64 +QMAKE_LIBDIR_OPENGL = /usr/X11R6/lib64 + load(qt_config) diff -Naur mkspecs/linux-g++/qplatformdefs.h mkspecs/linux- g++-64/qplatformdefs.h --- mkspecs/linux-g++/qplatformdefs.h 2015-08-08 00:19:31.266895204 -0300 +++ mkspecs/linux-g++-64/qplatformdefs.h2015-08-08 00:19:31.262895331 -0300 @@ -31,62 +31,4 @@ ** / -#ifndef QPLATFORMDEFS_H -#define QPLATFORMDEFS_H - -// Get Qt defines/settings - -#include "qglobal.h" - -// Set any POSIX/XOPEN defines at the top of this file to turn on specific APIs - -// 1) need to reset default environment if _BSD_SOURCE is defined -// 2) need to specify POSIX thread interfaces explicitly in glibc 2.0 -// 3) it seems older glibc need this to include the X/Open stuff -#ifndef _GNU_SOURCE -# define _GNU_SOURCE -#endif - -#include - - -// We are hot - unistd.h should have turned on the specific APIs we requested - -#include -#include -#include -#include -#include -#include -#include - -#include -#include -#include -#include -#include -#include -#include -#include -#include -#ifndef QT_NO_IPV6IFNAME -#include -#endif - -#define QT_USE_XOPEN_LFS_EXTENSIONS -#include "../common/posix/qplatformdefs.h" - -#undef QT_SOCKLEN_T - -#if defined(__GLIBC__) && (__GLIBC__ >= 2) -#define QT_SOCKLEN_Tsocklen_t -#else -#define QT_SOCKLEN_Tint -#endif - -#if defined(_XOPEN_SOURCE) && (_XOPEN_SOURCE >= 500) -#define QT_SNPRINTF ::snprintf -#define QT_VSNPRINTF::vsnprintf -#endif - -#endif // QPLATFORMDEFS_H +#include "../linux-g++/qplatformdefs.h" -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: [bts-link] source package kate
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kate > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #448490 (http://bugs.debian.org/448490) > # Bug title: kate: Kate has no crash recovery > # * http://bugs.kde.org/show_bug.cgi?id=107710 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> WONTFIX > # * upstream said bug is wontfix > tags 448490 + upstream wontfix Bug #448490 [kate] kate: Kate has no crash recovery Added tag(s) upstream and wontfix. > usertags 448490 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 448490 + status-RESOLVED resolution-WONTFIX There were no usertags set. Usertags are now: status-RESOLVED resolution-WONTFIX. > # remote status report for #535832 (http://bugs.debian.org/535832) > # Bug title: kate request: background color in export as HTML > # * http://bugs.kde.org/show_bug.cgi?id=207533 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> WONTFIX > # * upstream said bug is wontfix > tags 535832 + upstream wontfix Bug #535832 [kate] kate request: background color in export as HTML Added tag(s) wontfix. > usertags 535832 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 535832 + status-RESOLVED resolution-WONTFIX There were no usertags set. Usertags are now: status-RESOLVED resolution-WONTFIX. > thanks Stopping processing here. Please contact me if you need assistance. -- 448490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448490 535832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package kwin
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kwin > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #794501 (http://bugs.debian.org/794501) > # Bug title: [kwin] Can't go to previous virtual desktop with > (Meta|Alt|Ctrl)+Shift+Tab > # * http://bugs.kde.org/show_bug.cgi?id=341959 > # * remote status changed: CONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 794501 + fixed-upstream Bug #794501 [kwin] [kwin] Can't go to previous virtual desktop with (Meta|Alt|Ctrl)+Shift+Tab Added tag(s) fixed-upstream. > usertags 794501 - status-CONFIRMED Usertags were: status-CONFIRMED. Usertags are now: . > usertags 794501 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 794501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Exhausts X11 shared memory
Processing commands for cont...@bugs.debian.org: > reassign 800698 openjdk-7-jre Bug #800698 [libqtgui4] libqtgui4: GUI applications become unusable when shared memory is exhausted Bug reassigned from package 'libqtgui4' to 'openjdk-7-jre'. No longer marked as found in versions qt4-x11/4:4.8.7+dfsg-3. Ignoring request to alter fixed versions of bug #800698 to the same values previously set > retitle 800698 Exhausts X11 shared memory Bug #800698 [openjdk-7-jre] libqtgui4: GUI applications become unusable when shared memory is exhausted Changed Bug title to 'Exhausts X11 shared memory' from 'libqtgui4: GUI applications become unusable when shared memory is exhausted' > thanks Stopping processing here. Please contact me if you need assistance. -- 800698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Exhausts X11 shared memory
reassign 800698 openjdk-7-jre retitle 800698 Exhausts X11 shared memory thanks openjdk maintainers: I'm reassigning this bug to you because we ruled out Qt4 for now, and the workaround is switching from openjdk-7 to openjdk-8. Please take a look at the full bug log for more information. On Thursday 08 October 2015 17:24:04 Boris Pek wrote: [snip] > I do not have any experience in Java and I do not have enough time and > interest for investigating the bug in openjdk-7 dipper. Also we can do > nothing from Qt4 side. And there is a known workaround. So this bug report > might be closed now. Let's better reassign it to openjdk-7-jre. If changing to openjdk-8 fixes the problem then the issue might be there. -- Una sola bomba nuclear puede arruinar el resto de tu día. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems
Hi, >> control: retitle 800698 libqtgui4: GUI applications become unusable when >> shared memory is exhausted > > With this title I'm even more convinced that this is not a bug ;) Please read > below. This is only an assumption which is based on found bug reports in other projects. >> >> but hey, why Qt5 based and Gtk+ >> >> based programs were working without any issues in the same conditions? >> > >> > I do have an idea. Where those java applications creating an icon in the >> > taskbar? >> > >> > The only change that *might* be causing the problem here is the addition >> > of a patch that allows the systray to use sni-qt. >> >> At first look I do not see anything related to shared memory usage in patch >> [1]. >> >> [1] >> >> http://anonscm.debian.org/cgit/pkg-kde/qt/qt4-x11.git/tree/debian/patches/plugin_system_for_systemtray.patch?h=debian/4.8.7%2bdfsg-3 >> > Did any of the Java created a taskbar icon? >> >> If you had in mind a notification area, then yes, the most complex of these >> Java based programs creates an icon in system tray. And this icon is >> blinking when some events inside program trigger it. > > The only source change between the versions you mentioned in the original bug > report is that patch. And I know Qt4 is using (X-11-related?) shared memory to > draw things because I remember having to fix some permissions issues in past > releases (for Wheezy IIRC). > > I don't know why GTK doesn't fails, and I *guess* that Qt5 might be using some > OpenGL-related stuff that might make things go without problems. Yes, it looks that Qt4 uses X11 rendering by default. I have checked [1] and [2]. In the first case GUI rendering is broken and unusable and there are a lot of repeated X11 error messages in console [3]. But in the second case program looks more or less fine (only font in the main menu and in context menus looks ugly because of font hinting does not work here). [1] okular --graphicssystem raster [2] okular --graphicssystem opengl [3] The beginning of log from stderr: QNativeImage: Unable to attach to shared memory segment. X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 56 (X_ChangeGC) Resource id: 0x0 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 ... > Are you running sni-qt? If so maybe the bug is there, or at least related. I have removed sni-qt package and after reboot bug is still present. >> The main question is what to do with Qt4 libraries? >> >> Other Debian users may face to this bug because package default-jdk depends >> from openjdk-7-jdk in Debian Stretch. > > Well, if the memory gets exhausted is no wonder that Qt4 fails. Now I hardly > doubt that this is a bug in Qt4 due to the amount of testing the current > version has, after all it's just bug fixes from stable, and not many linux- > related precisely. And the behavior started with just a patch for sni-qt. > > If you have sni-qt installed I would definitely take a look there first. sni-qt does not cause to this bug. The problem is somewhere else. Unfortunately, I do not have cowbuilder environment for amd64 now thus I cannot rebuild qt4-x11 package without discussed patch for testing, but I have force installed libqtgui4/4:4.8.7+dfsg-1 from Debian snapshots archive [4] (yes, only this one package and nothing more) and after reboot I can reproduce the bug. So the problem is definitely not in the plugin_system_for_systemtray.patch. Probably an update in completely anoter package have lead to this bug. [4] http://snapshot.debian.org/archive/debian/20150526T221958Z/pool/main/q/qt4-x11/libqtgui4_4.8.7%2Bdfsg-1_amd64.deb > I'll leave the bug open tagged as moreinfo in case you want to reassign it, > else I'll close it in a couple of weeks, as nothing shows this is really a Qt4 > bug. I do not have any experience in Java and I do not have enough time and interest for investigating the bug in openjdk-7 dipper. Also we can do nothing from Qt4 side. And there is a known workaround. So this bug report might be closed now. Best regards, Boris
Bug#797765: (no subject)
On Monday 05 October 2015 10:45:14 Johannes Zarl-Zierl wrote: [snip] > Thanks for the explanation. My pleasure. > In this case it would be nice if the package would at least show up in a > search for qtquick. Is it possible to change the package description of > > qtdeclarative5-dev to something like this: > >> This package contains the header development files for building some > >> Qt 5 applications using Qt 5 declarative (aka QtQuick2) headers. > > Another way to make the situation more transparent to users would be to add > > something like this to the package description of qtquick1-5-dev: > >> In order to build Qt Quick 2 applications on Qt5, you need to install the > >> package qtdeclarative5-dev, instead. The suggestions are indeed fine, but we will be retiring qtquick1 with the next Qt5 upload. We will consider adding more info the the declarative long description, of course. Kinds regards, Lisandro. -- "A computer is like an air conditioner. It stops working when you open windows." Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#800821: some tests
Downgrading dolphin (to 4:15.4.3) but keeping konqueror at 4:15.08.1-1 allows to use dolphinpart again. During the update from 4:15.4.3 (working) to 4:15.08 (broken), dolphin was split to a separate src package and its libs were moved to a different folder (from /usr/lib/kde4 to /usr/lib/[ARCH]/qt5/plugins). Maybe it's looking for the dolphinpart.so in the wrong folder? However, just symlinking dolphinpart.so to the old path does not work for me
Bug#801308: umbrello: Can't save to file - "UMLDoc::saveDocument moving with error"
Package: umbrello Version: 4:15.08.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? After starting the application umbrello, even if there's or not some content in the diagram, saving file shows up a dialog box saying: "There was a problem saving file: /path/to/the/file/to/be/saved * What exactly did you do (or not do) that was effective (or ineffective)? Starting umbrello in CLI to see log messages and see the error as: klauncher not running... launching kdeinit klauncher not running... launching kdeinit klauncher not running... launching kdeinit couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files" umbrello: UMLDoc::saveDocument moving with error = "/tmp/umbrello.X20558" to QUrl( "file:///home/groolot/file.xmi" ) But fortunatly, the temporary file "/tmp/umbrello.X20558" exists and contain the appropriate content as created inside umbrello. I then suspect a problem in the 'moving' action inside the program, from temporary file to saved file. * What was the outcome of this action? Not saving the file. * What outcome did you expect instead? The file to be saved in the right place. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages umbrello depends on: ii libc6 2.19-22 ii libkf5archive55.14.0-1 ii libkf5completion5 5.14.0-1 ii libkf5configcore5 5.14.0-1 ii libkf5configgui5 5.14.0-1 ii libkf5configwidgets5 5.14.0-1 ii libkf5coreaddons5 5.14.0-1 ii libkf5i18n5 5.14.0-1 ii libkf5iconthemes5 5.14.0-1 ii libkf5jobwidgets5 5.14.0-1 ii libkf5kiocore55.14.0-1 ii libkf5kiowidgets5 5.14.0-1 ii libkf5texteditor5 5.14.0-1 ii libkf5textwidgets55.14.0-1 ii libkf5widgetsaddons5 5.14.0-1 ii libkf5xmlgui5 5.14.0-1 ii libqt5core5a 5.4.2+dfsg-9 ii libqt5gui55.4.2+dfsg-9 ii libqt5printsupport5 5.4.2+dfsg-9 ii libqt5svg55.4.2-3 ii libqt5widgets55.4.2+dfsg-9 ii libqt5xml55.4.2+dfsg-9 ii libstdc++65.2.1-17 ii libxml2 2.9.2+zdfsg1-4 ii libxslt1.11.1.28-2+b2 umbrello recommends no packages. Versions of packages umbrello suggests: ii khelpcenter 4:5.4.1-1 -- no debconf information
Bug#800698: Kmail2 display garbled (after a while)
Hi Boris, I didn't have that issue any more since a few days. Kmail is pretty much in use each day and when I had this issue, I had it several times a day (reboot, kdm stop/start, kmail stop/start didn't help much). As soon as the problem pops up again, I'll come back here. Thanks for having a look ! Tim On Thursday 08 October 2015 11:42:25 Boris Pek wrote: > Hi Tim, > > > since I installed kde5 I have a kmail2 issue. > > > > After a while the kmail2 display window becomes drawn unreadable. > > See this screenshot: > > https://drive.google.com/open?id=0B_loju3MX2rTZlNOdDRxblVTWDg > > > > Stopping and starting kmail does not help. > > Stopping and starting kdm helps for a while (until it suddenly happens > > again). > > > > I can't see anything obvious in 'dmesg' or .xsession-errors. Well I see > > lot's of 'BadDrawable' messages, but these are not limited to kmail. > > > > I am on Debian SID with latest dist-upgrade, have the problem with kernel > > 4.1 and 4.2 (didn't test any older kernels). Grafix is internal Intel i3 > > (Sandy Bridge). > > > > Any ideas how to work around that or how to pin the problem ? > > $ ldd /usr/bin/kmail | grep QtGui > libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 > (0x7f984cbb) > > kmail is currently built with old Qt4 based KDE libs. It looks that you have > faced with issue from #800698. Please try to launch kmail from terminal and > show the output. > > Best regards, > Boris
Bug#800698: Kmail2 display garbled (after a while)
Hi Tim, > since I installed kde5 I have a kmail2 issue. > > After a while the kmail2 display window becomes drawn unreadable. > See this screenshot: > https://drive.google.com/open?id=0B_loju3MX2rTZlNOdDRxblVTWDg > > Stopping and starting kmail does not help. > Stopping and starting kdm helps for a while (until it suddenly happens again). > > I can't see anything obvious in 'dmesg' or .xsession-errors. Well I see lot's > of 'BadDrawable' messages, but these are not limited to kmail. > > I am on Debian SID with latest dist-upgrade, have the problem with kernel 4.1 > and 4.2 (didn't test any older kernels). Grafix is internal Intel i3 (Sandy > Bridge). > > Any ideas how to work around that or how to pin the problem ? $ ldd /usr/bin/kmail | grep QtGui libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f984cbb) kmail is currently built with old Qt4 based KDE libs. It looks that you have faced with issue from #800698. Please try to launch kmail from terminal and show the output. Best regards, Boris
