Fixed: chroot-installation_sid_install_qt5/267
See https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/267//console or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/267/ for more information.
Re: Updated Akonadi 1.13 packages
Hi Martin, On Friday 31 July 2015 22:01:03 Martin Steigerwald wrote: Any chance for updated Akonadi 1.13 packages? I'm not sure what exactly you are suggesting. Lately I've been working on Akonadi [1] and I'm happy to report that I believe I've managed to stabilise it. I strongly recommend to refrain from any further uploads of 1.13 unless some serious bugs are discovered. With my huge mail archive I'm in the same boat with you so I've tried latest head of 1.13 branch but found it unreliable and half-baked with multiple regressions in various backends. I selectively applied all changes that work reliably and I even had to rollback some that did not pass my tests. Testing Akonadi is a hell of an effort as it requires many hours of stressing with all three backends. Some changes in 1.13 cause unrecoverable database errors when even `akonadictl fsck` does not help. Some changes break initialisation of new database. I feel very uncomfortable about the idea of uploading any further changes to 1.13. I strongly recommend to wait till new upstream release. Meanwhile you can upgrade to akonadi/1.13.0-7 which accumulated the best improvements from 1.13 without known regressions. [1]: http://metadata.ftp-master.debian.org/changelogs/main/a/akonadi/unstable_changelog -- Best wishes, Dmitry Smirnov --- There is no such thing as public opinion. There is only published opinion. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#793778: kscreen: Big issues with three monitors
On Friday 31 July 2015 11:58:46 Martin Steigerwald wrote: Am Freitag, 31. Juli 2015, 11:45:51 schrieb Dominik George: Anyway, it may be wise to just retest with Qt 5.5. Maybe the issue is fixed already. Ok. I got the impression that somehow this is related to attaching *two* new screens at the same time, which is the case when ounting the notebook into the docking station. Maybe this leads to some kidn of race condition. Well, feel free to report the bug upstream if you think it you have an unusual setup. I just read by upstream and Lisandro that Qt 5.5 and even more so 5.5.1 fixed quite some mutiple screens related issues. I am not sure whether it fixes yours. I'm also not sure, but upstream will definetely ask you to test with Qt 5.5.0 so.. I'm afraid the best solution might be to wait here. Tip: what happens if you dock the notebook before turning it on? or at least while being on sddm (ie, not logged in plasma). -- 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#793778: kscreen: Big issues with three monitors
Hi, Tip: what happens if you dock the notebook before turning it on? or at least while being on sddm (ie, not logged in plasma). this scenario works better. It does not crash anything, however, it messes up the KDE panel. This might be another bug, though. -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Mobil: +49-151-61623918 Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Contributor LPIC-3 Linux Enterprise Professional (Security) signature.asc Description: This is a digitally signed message part.
Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade
It should, that's the default path embedded in the libs. The en variable might be used to override it. As I said, doing unset QT_PLUGIN_PATH and then running anything qt4 does not work either. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ signature.asc Description: This is a digitally signed message part.
Re: Updated Akonadi 1.13 packages
Am Samstag, 1. August 2015, 21:16:31 schrieb Dmitry Smirnov: Hi Martin, Hi Dmitry, On Friday 31 July 2015 22:01:03 Martin Steigerwald wrote: Any chance for updated Akonadi 1.13 packages? I'm not sure what exactly you are suggesting. Lately I've been working on Akonadi [1] and I'm happy to report that I believe I've managed to stabilise it. I strongly recommend to refrain from any further uploads of 1.13 unless some serious bugs are discovered. Ok, I was not aware that you cherry-picked some optimization patches. Then I wonder why it still feels slower than the self-compiled one. I may have a closer look at which patches you merged. With my huge mail archive I'm in the same boat with you so I've tried latest head of 1.13 branch but found it unreliable and half-baked with multiple regressions in various backends. I selectively applied all changes that work reliably and I even had to rollback some that did not pass my tests. Testing Akonadi is a hell of an effort as it requires many hours of stressing with all three backends. Some changes in 1.13 cause unrecoverable database errors when even `akonadictl fsck` does not help. Some changes break initialisation of new database. Yikes. Is / did you make upstream aware of that? I feel very uncomfortable about the idea of uploading any further changes to 1.13. I strongly recommend to wait till new upstream release. I accept this, Dmitry. I didn´t see any regressions with the MySQL backend myself, so I wasn´t aware of any. And I was using this git versions for weeks at least. Meanwhile you can upgrade to akonadi/1.13.0-7 which accumulated the best improvements from 1.13 without known regressions. [1]: http://metadata.ftp-master.debian.org/changelogs/main/a/akonadi/unstable_ch angelog Thank you for your detailed explaination, -- Martin signature.asc Description: This is a digitally signed message part.
Re: Updated Akonadi 1.13 packages
Am Samstag, 1. August 2015, 21:16:31 schrieb Dmitry Smirnov: Hi Martin, On Friday 31 July 2015 22:01:03 Martin Steigerwald wrote: Any chance for updated Akonadi 1.13 packages? I'm not sure what exactly you are suggesting. Lately I've been working on Akonadi [1] and I'm happy to report that I believe I've managed to stabilise it. I strongly recommend to refrain from any further uploads of 1.13 unless some serious bugs are discovered. Ok, in concrete, I am willing to help report and follow-up on: akonadi (1.13.0-7) unstable; urgency=medium […] * Removed some patches introduced in previous upload due to regressions causing invalid SQL commands. -- Dmitry Smirnov only...@debian.org Mon, 20 Jul 2015 12:30:32 +1000 akonadi (1.13.0-6) unstable; urgency=medium […] * Bunch of optimisation patches from upstream 1.13 branch. […] -- Dmitry Smirnov only...@debian.org Mon, 20 Jul 2015 03:26:42 +1000 Do you want to take the time to share what regressions you got, so I can report them upstream? If you already reported them, disregard my mail. Meanwhile you can upgrade to akonadi/1.13.0-7 which accumulated the best improvements from 1.13 without known regressions. I forgot to mention, I have this one installed already, using sid with some packages from experimental on this machine. Thank you for your work on the package and your testing with all backends. [1]: http://metadata.ftp-master.debian.org/changelogs/main/a/akonadi/unstable_ch angelog Thanks, -- Martin signature.asc Description: This is a digitally signed message part.
Bug#794341: kwin-x11: Window manager often frezes when some of window is resized
Package: kwin-x11 Version: 4:5.3.2-3 Severity: important Dear Maintainer, Window manager kwin_x11 frezes quite often when I try to resize some window. I observed that it happens mostly when I drag bottom right corner of window for very short time. If I hold mouse button longer it mostly doesn't happen. When it happen all programs continues working and screen continues to be refreshed, but there is not possible to move, close, resize of any window. It doesn't react on mouse commands and keyboard. There is only possible to swith to TTY (ctrl+alt+F1) and restart sddm Unfortunatelly I haven't found any trace of this error in journalcrl. I have no idea where to find any log files for kwin_x11. I have tried to run kwin_x11 from console to see if it produce any strerr output, but it doesn't when freeze happens. Only what I can provide is dump of my kwin configuration (output from qdbus org.kde.KWin /KWin supportInformation) It's pasted here: https://paste.kde.org/pywlqjyzt -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kwin-x11 depends on: ii kwin-common 4:5.3.2-3 ii libc62.19-19 ii libkf5i18n5 5.12.0-1 ii libkf5windowsystem5 5.12.0-1 ii libqt5core5a 5.4.2+dfsg-5 ii libqt5gui5 5.4.2+dfsg-5 ii libqt5widgets5 5.4.2+dfsg-5 ii libqt5x11extras5 5.4.2-2 ii libstdc++6 5.1.1-14 ii libxcb1 1.10-3+b1 kwin-x11 recommends no packages. kwin-x11 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150801171542.5810.78152.report...@krzysztof.dom.net
Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade
On Saturday 01 August 2015 09:22:30 Salvo Tomaselli wrote: [snip] The Debian qt4-x11 build looks for plugins in /usr/lib/arch/qt4/plugins. That's why it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) It should, that's the default path embedded in the libs. The en variable might be used to override it. -- 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.
qt-kde team meeting at Debconf?
Hi. will you meet at Debconf in Heidelberg? I will be there and would like to meet some of you in person. Maybe I can help with some bug triaging or so. I also will be at Randa Meetings in September, also for bug triaging, maybe more. So if you have anything that really things needs more attention to look at, I may be able to spend some time on it or discuss things upstream. Thank you, -- Martin -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4745307.KOYliuKapq@merkaba
Bug#794292: Removed package(s) from experimental
We believe that the bug you reported is now fixed; the following package(s) have been removed from experimental: libkf5modemmanagerqt-dev | 4:5.2.2-1 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libkf5modemmanagerqt5 | 4:5.2.2-1 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libkf5modemmanagerqt5-dbg | 4:5.2.2-1 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libmm-qt | 4:5.2.2-1 | source --- Reason --- ROM; obsolete, replaced by modemmanager-qt -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/794292 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1zlgyk-0001zi...@franck.debian.org
Bug#794292: Removed package(s) from experimental
Version: 4:5.2.2-1+rm Dear submitter, as the package libmm-qt has just been removed from the Debian archive experimental we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/794292 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1zlgyp-0001zo...@franck.debian.org
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates a disfonctionnement of any window kde
Package: kde-window-manager Version: 4:5.3.2-3 Followup-For: Bug #793026 Dear Maintainer, The bug is still present but it can be reclassified since it's not important anymore: the symlink /usr/bin/kwin allowed kwin to start but, at least for me, window title bar was black and not usable; I had to install kwin-decoration-oxygen to have usable windows (at least one theme), but I still see some weird things: 1) In systemsettings - windows decorations working themes are black (I'll attach a screenshot to show), the one visible is the non working one (black title bar) 2) Downloaded decorations don't work; I assume they're vastly for kde4, maybe not compatible for kde5, one should consider a way for filtering. Don't work mean the black title as above. 3) There is only one decoration theme, but maybe it's just a matter of time. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-window-manager depends on: ii kwin-x11 4:5.3.2-3 kde-window-manager recommends no packages. kde-window-manager suggests no packages. -- no debconf information
Bug#794292: Removed package(s) from unstable
Version: 1.0.1-2+rm Dear submitter, as the package libmm-qt has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/794292 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1zlgxe-0001vo...@franck.debian.org
Bug#793052: Disconnected IMAP stops getting mail
On Tuesday, July 21, 2015 02:49:22 PM you wrote: Hi Charles, First of all please always report bugs using reportbug utility as described in https://www.debian.org/Bugs/Reporting because we need all the additional information about installed packages on your system. Ok. This problem might be related to Akonadi. Typically that kind of problems may happen due to problems in storage backend when akonadi can't save downloaded emails. What version of akonadi you have installed? Please try latest akonadi* 1.13.0-7 packages from unstable since 1.13.0-7 fixes deadlock that may be affecting kmail. ii akonadi-server 1.13.0-2 amd64 I will try the unstable version so as long as it doesn't pull in a million new libraries and therefor risk breaking my system. It seems to get better if I enable interval mail check (and thus reportedly turn off IMAP IDLE) What Akonadi backend are you using? (See value of Driver variable in ~/.config/akonadi/akonadiserverrc). mysql Please try running akonadictl fsck. If your akonadi uses MYSQL backend then it may be worth checking for errors in No effect, and no errors. Charles -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3411669.xxHlpij8iH@phalaris
Re: Updated Akonadi 1.13 packages
On Saturday 01 August 2015 18:56:09 Martin Steigerwald wrote: Do you want to take the time to share what regressions you got, so I can report them upstream? If you already reported them, disregard my mail. I did not have time to chase those problems with upstream, unfortunately... On MySQL backend I've seen Error code: 1452 DB error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`PartTable`, CONSTRAINT `PartTable_ibfk_2` FOREIGN KEY (`partTypeId`) REFERENCES `PartTypeTable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) Error text: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`PartTable`, CONSTRAINT `PartTable_ibfk_2` FOREIGN KEY (`partTypeId`) REFERENCES `PartTypeTable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement Query: INSERT INTO PartTable (pimItemId, data, datasize, version, external) VALUES (:0, :1, :2, :3, :4) Error during insertion into table PartTable Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`PartTable`, CONSTRAINT `PartTable_ibfk_2` FOREIGN KEY (`partTypeId`) REFERENCES `PartTypeTable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement and other errors like invalid SQL sentences etc. I don't remember what caused this particular error but the whole process felt so fragile I almost lost confidence in Akonadi. :( Cherry-picking optimisations in Akonadi is not too easy as they cascade on top of each other. It turned out that it is extremely time consuming to apply even those that look safe and testing often proves that impression wrong... I forgot to mention, I have this one installed already, using sid with some packages from experimental on this machine. Nice. I hope updated Akonadi will work well for you. :) Thank you for your work on the package and your testing with all backends. Thanks for your help and sorry for not chasing problems in Akonady any further. In order to report bugs upstream it might be better to test Akonadi's matser but I can't risk breaking my email by doing that. Fiddling with Akonadi already took a whole week of my time and I simply can't afford to continue working on. Luckily my email is working again... -- All the best, Dmitry Smirnov --- The foundation of morality should not be made dependent on myth nor tied to any authority lest doubt about the myth or about the legitimacy of the authority imperil the foundation of sound judgment and action. -- Albert Einstein signature.asc Description: This is a digitally signed message part.
Re: Updated Akonadi 1.13 packages
On Saturday 01 August 2015 18:48:11 Martin Steigerwald wrote: Ok, I was not aware that you cherry-picked some optimization patches. Then I wonder why it still feels slower than the self-compiled one. I may have a closer look at which patches you merged. I could not include all patches due to regressions... Some changes in 1.13 cause unrecoverable database errors when even `akonadictl fsck` does not help. Some changes break initialisation of new database. Yikes. Is / did you make upstream aware of that? Unfortunately I had no time to properly document and report this. My priority was to fix deadlock and number of other problems in Akonadi. Testing upstream optimisations was not part of the agenda... I presume upstream should pick up such issues in their own testing. There is a possibility that some of those problems could be detected by unit tests that we do not run... I accept this, Dmitry. I didn´t see any regressions with the MySQL backend myself, so I wasn´t aware of any. And I was using this git versions for weeks at least. When I cherry-picked some optimisations I found that one or two of them broke initialisation of new database... I think borrowing any more fixes may cause more harm than good. My hopes are with new upstream release -- at least testing it may be feasible... -- Regards, Dmitry Smirnov --- For every complex problem there is an answer that is clear, simple, and wrong. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#777957: marked as done (libmm-qt: ftbfs with GCC-5)
Your message dated Sun, 02 Aug 2015 00:18:19 + with message-id e1zlgyp-0001zo...@franck.debian.org and subject line Bug#794292: Removed package(s) from experimental has caused the Debian Bug report #777957, regarding libmm-qt: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libmm-qt Version: 1.0.1-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/libmm-qt_1.0.1-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] (optional=templinst)_ZN5QListI7QStringE6appendERKS0_@Base 1.0.1 - (optional=templinst)_ZN5QListI7QStringED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListI7QStringED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI7QStringED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI7QStringED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListI8QVariantE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListI8QVariantE6appendERKS0_@Base 1.0.1 - (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE13detach_helperEi@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE6appendERKS2_@Base 1.0.1 - (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListIjE13detach_helperEi@Base 1.0.1 (optional=templinst)_ZN5QListIjE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListIjE5clearEv@Base 1.0.1 - (optional=templinst)_ZN5QListIjE6appendERKj@Base 1.0.1 - (optional=templinst)_ZN5QListIjED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListIjED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjE6appendERKj@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjED2Ev@Base 1.0.1 _ZN6QDebugD1Ev@Base 1.0.1 _ZN6QDebugD2Ev@Base 1.0.1 - _ZN7QStringD1Ev@Base 1.0.1 - _ZN7QStringD2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# _ZN7QStringD1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# _ZN7QStringD2Ev@Base 1.0.1 _ZNK12ModemManager11ModemDevice10interfacesEv@Base 1.0.1 _ZNK12ModemManager11ModemDevice10isGsmModemEv@Base 1.0.1 _ZNK12ModemManager11ModemDevice10metaObjectEv@Base 1.0.1 @@ -844,7 +847,8 @@ _ZlsR13QDBusArgumentRK16CurrentModesType@Base 1.0.1 _ZlsR13QDBusArgumentRK17SignalQualityPair@Base 1.0.1 _ZlsR13QDBusArgumentRK5QListI4QMapI7QString8QVariantEE@Base 1.0.1 - (optional=templinst)_ZrsI15QDBusObjectPath4QMapI7QStringS1_IS2_8QVariantEEERK13QDBusArgumentS8_RS1_IT_T0_E@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZrsI15QDBusObjectPath4QMapI7QStringS1_IS2_8QVariantEEERK13QDBusArgumentS8_RS1_IT_T0_E@Base 1.0.1 +
Bug#777957: marked as done (libmm-qt: ftbfs with GCC-5)
Your message dated Sun, 02 Aug 2015 00:16:40 + with message-id e1zlgxe-0001vo...@franck.debian.org and subject line Bug#794292: Removed package(s) from unstable has caused the Debian Bug report #777957, regarding libmm-qt: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libmm-qt Version: 1.0.1-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/libmm-qt_1.0.1-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] (optional=templinst)_ZN5QListI7QStringE6appendERKS0_@Base 1.0.1 - (optional=templinst)_ZN5QListI7QStringED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListI7QStringED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI7QStringED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI7QStringED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListI8QVariantE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListI8QVariantE6appendERKS0_@Base 1.0.1 - (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE13detach_helperEi@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEE6appendERKS2_@Base 1.0.1 - (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIN12ModemManager11ModemDevice13InterfaceTypeEED2Ev@Base 1.0.1 (optional=templinst)_ZN5QListIjE13detach_helperEi@Base 1.0.1 (optional=templinst)_ZN5QListIjE18detach_helper_growEii@Base 1.0.1 (optional=templinst)_ZN5QListIjE5clearEv@Base 1.0.1 - (optional=templinst)_ZN5QListIjE6appendERKj@Base 1.0.1 - (optional=templinst)_ZN5QListIjED1Ev@Base 1.0.1 - (optional=templinst)_ZN5QListIjED2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjE6appendERKj@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjED1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZN5QListIjED2Ev@Base 1.0.1 _ZN6QDebugD1Ev@Base 1.0.1 _ZN6QDebugD2Ev@Base 1.0.1 - _ZN7QStringD1Ev@Base 1.0.1 - _ZN7QStringD2Ev@Base 1.0.1 +#MISSING: 1.0.1-2# _ZN7QStringD1Ev@Base 1.0.1 +#MISSING: 1.0.1-2# _ZN7QStringD2Ev@Base 1.0.1 _ZNK12ModemManager11ModemDevice10interfacesEv@Base 1.0.1 _ZNK12ModemManager11ModemDevice10isGsmModemEv@Base 1.0.1 _ZNK12ModemManager11ModemDevice10metaObjectEv@Base 1.0.1 @@ -844,7 +847,8 @@ _ZlsR13QDBusArgumentRK16CurrentModesType@Base 1.0.1 _ZlsR13QDBusArgumentRK17SignalQualityPair@Base 1.0.1 _ZlsR13QDBusArgumentRK5QListI4QMapI7QString8QVariantEE@Base 1.0.1 - (optional=templinst)_ZrsI15QDBusObjectPath4QMapI7QStringS1_IS2_8QVariantEEERK13QDBusArgumentS8_RS1_IT_T0_E@Base 1.0.1 +#MISSING: 1.0.1-2# (optional=templinst)_ZrsI15QDBusObjectPath4QMapI7QStringS1_IS2_8QVariantEEERK13QDBusArgumentS8_RS1_IT_T0_E@Base 1.0.1 +
Bug#794292: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libmm-qt |1.0.1-2 | source libmodemmanagerqt-dbg |1.0.1-2 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libmodemmanagerqt-dev |1.0.1-2 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libmodemmanagerqt1 |1.0.1-2 | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x --- Reason --- ROM; obsolete, replaced by modemmanager-qt -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/794292 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1zlgx8-0001vw...@franck.debian.org
Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade
Hello, Could you check with ldd /usr/bin/qweborf. That'll shows which Qt library is used. It's python. It uses pyqt4. I am attaching the ldd output for subsurface, which is a C++ thing that uses Qt4. The Debian qt4-x11 build looks for plugins in /usr/lib/arch/qt4/plugins. That's why it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ linux-vdso.so.1 (0x7ffd5374e000) libdivecomputer.so.0 = /usr/lib/x86_64-linux-gnu/libdivecomputer.so.0 (0x7f8c9544f000) libxslt.so.1 = /usr/lib/x86_64-linux-gnu/libxslt.so.1 (0x7f8c9521) libxml2.so.2 = /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x7f8c94e45000) libmarblewidget.so.19 = /usr/lib/libmarblewidget.so.19 (0x7f8c9469c000) libzip.so.2 = /usr/lib/x86_64-linux-gnu/libzip.so.2 (0x7f8c9448b000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f8c9426f000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f8c93fa2000) libgit2.so.22 = /usr/lib/x86_64-linux-gnu/libgit2.so.22 (0x7f8c93cd6000) libQtWebKit.so.4 = /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 (0x7f8c917f5000) libQtSvg.so.4 = /usr/lib/x86_64-linux-gnu/libQtSvg.so.4 (0x7f8c9159d000) libQtGui.so.4 = /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f8c908a7000) libQtNetwork.so.4 = /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x7f8c90555000) libQtCore.so.4 = /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x7f8c90065000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8c8fe48000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f8c8fb3b000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f8c8f83a000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f8c8f624000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f8c8f27a000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8c8f076000) libicui18n.so.52 = /usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x7f8c8ec64000) libicuuc.so.52 = /usr/lib/x86_64-linux-gnu/libicuuc.so.52 (0x7f8c8e8e6000) libicudata.so.52 = /usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x7f8c8d079000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8c8ce56000) libastro.so.1 = /usr/lib/libastro.so.1 (0x7f8c8cc16000) libQtDBus.so.4 = /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x7f8c8c999000) libQtXml.so.4 = /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x7f8c8c752000) libQtScript.so.4 = /usr/lib/x86_64-linux-gnu/libQtScript.so.4 (0x7f8c8c298000) libQtDeclarative.so.4 = /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 (0x7f8c8bce) libphonon.so.4 = /usr/lib/x86_64-linux-gnu/libphonon.so.4 (0x7f8c8ba62000) libhttp_parser.so.2.1 = /usr/lib/x86_64-linux-gnu/libhttp_parser.so.2.1 (0x7f8c8b85a000) libssl.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x7f8c8b5f) libcrypto.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f8c8b18f000) libssh2.so.1 = /usr/lib/x86_64-linux-gnu/libssh2.so.1 (0x7f8c8af65000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f8c8ad5d000) libXrender.so.1 = /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x7f8c8ab53000) libjpeg.so.62 = /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x7f8c8a8f8000) libpng12.so.0 = /lib/x86_64-linux-gnu/libpng12.so.0 (0x7f8c8a6d1000) libgstapp-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstapp-1.0.so.0 (0x7f8c8a4c4000) libgstpbutils-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0 (0x7f8c8a29b000) libgstvideo-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 (0x7f8c8a04e000) libgstaudio-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 (0x7f8c89dff000) libgstbase-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 (0x7f8c89b9f000) libgstreamer-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 (0x7f8c8988e000) libgobject-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7f8c8963c000) libglib-2.0.so.0 = /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f8c8932c000) libfontconfig.so.1 = /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7f8c890ef000) libQtXmlPatterns.so.4 = /usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so.4 (0x7f8c88a98000) libQtOpenGL.so.4 = /usr/lib/x86_64-linux-gnu/libQtOpenGL.so.4 (0x7f8c88795000)
