Bug#735488: Qt4 in arm64: wrap up of the current situation
Mark: as per [0] Thiago (upstream for qtcore) says: +#ifndef Q_DATA_MEMORY_BARRIER +# define Q_DATA_MEMORY_BARRIER asm volatile(dmb sy\n:::memory) +#endif +#ifndef Q_COMPILER_MEMORY_BARRIER +# define Q_COMPILER_MEMORY_BARRIER asm volatile(:::memory) This shouldn't be necessary anymore if we're using the compilr intrinsics with the right __ATOMIC_xxx macros. The compiler will inser the proper barriers. Would it be possible to fix it? [0] https://codereview.qt-project.org/#patch,all_unified,81011,3 For everyone but specially Wookey who wants the patchs in Debian, quoting upstream WRT -fpermissive: That error needs to be fixed in the right place. Adding -fpermissive to make the error disappear without fixing the problem is not the right solution. So as I said before, this needs to get fixed before merging the patches. As a wrap-up of the push-to-upstream actions, the mostly objected part if the -fpermissive flag. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- 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/1666784.Zuv8zkeyqR@tonks
Processing of qtcreator_3.0.1+dfsg+exp-2_amd64.changes
qtcreator_3.0.1+dfsg+exp-2_amd64.changes uploaded successfully to localhost along with the files: qtcreator_3.0.1+dfsg+exp-2.dsc qtcreator_3.0.1+dfsg+exp-2.debian.tar.xz qtcreator_3.0.1+dfsg+exp-2_amd64.deb qtcreator-data_3.0.1+dfsg+exp-2_all.deb qtcreator-dbg_3.0.1+dfsg+exp-2_amd64.deb qtcreator-doc_3.0.1+dfsg+exp-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1wpxw4-0004v9...@franck.debian.org
qtcreator_3.0.1+dfsg+exp-2_amd64.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Mar 2014 12:32:01 -0300 Source: qtcreator Binary: qtcreator qtcreator-data qtcreator-dbg qtcreator-doc Architecture: source amd64 all Version: 3.0.1+dfsg+exp-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org Changed-By: Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org Description: qtcreator - lightweight integrated development environment (IDE) for Qt qtcreator-data - application data for Qt Creator IDE qtcreator-dbg - debugging symbols for Qt Creator IDE qtcreator-doc - documentation for Qt Creator IDE Changes: qtcreator (3.0.1+dfsg+exp-2) experimental; urgency=medium . * Remove unnecesary build dependencies added because of a bug in Qt Webkit. - Build depend upon libqt5webkit5-dev = 5.2.1+dfsg-4~ to be sure we don't hit the bug. Checksums-Sha1: 328890831dcd5a8c9687b6b5e0583c0d40d1deed 2842 qtcreator_3.0.1+dfsg+exp-2.dsc 8fb2ef24d61317786e81a5ac85a832b6117dab69 13932 qtcreator_3.0.1+dfsg+exp-2.debian.tar.xz 9b29b2e29c0af35bcb53f371a31e95ad21b76f90 11098616 qtcreator_3.0.1+dfsg+exp-2_amd64.deb b7b7d0df37f9fda165192d7de562f2ff78521662 1995152 qtcreator-data_3.0.1+dfsg+exp-2_all.deb 9e1e96073ea8a5f7a92e30147b77027b1bb9cd8f 294295752 qtcreator-dbg_3.0.1+dfsg+exp-2_amd64.deb d4ea29319b05c999b1ca986ea37703820c5af072 8561018 qtcreator-doc_3.0.1+dfsg+exp-2_all.deb Checksums-Sha256: 28afeebceb7cdd44198279189548fc76052509efef572ed65782ed59878b9ead 2842 qtcreator_3.0.1+dfsg+exp-2.dsc 1070b04645dc1514666373e1b67221035fb2f521925ea133b42595e9fd09bc8a 13932 qtcreator_3.0.1+dfsg+exp-2.debian.tar.xz 9aacf83bbd28acaa28601ba70d81b1cd32eadd51813c2af010d99427d2dee158 11098616 qtcreator_3.0.1+dfsg+exp-2_amd64.deb 74ba65991c38069874b4af87d9ec8adede8ebf06bc1cf77ab37a28412aa8f775 1995152 qtcreator-data_3.0.1+dfsg+exp-2_all.deb cc61ad3c9b4fece6e974b19a2583ee34b4cf15303483363a5990dd34107c993c 294295752 qtcreator-dbg_3.0.1+dfsg+exp-2_amd64.deb 6fa35226fdeb639c4a72a7e979f860193379a1e9a9b262cc94843fb7835e14c9 8561018 qtcreator-doc_3.0.1+dfsg+exp-2_all.deb Files: d3cb77895feb207172e4f9196616eebe 2842 devel optional qtcreator_3.0.1+dfsg+exp-2.dsc ad88f314964840ec19669922968d2785 13932 devel optional qtcreator_3.0.1+dfsg+exp-2.debian.tar.xz c7bf36ff73cc024f663c3bbfa214ca92 11098616 devel optional qtcreator_3.0.1+dfsg+exp-2_amd64.deb e80d35963345ceab52cf212033d2c6f0 1995152 devel optional qtcreator-data_3.0.1+dfsg+exp-2_all.deb b321038bef96f7949279d1a23087ead1 294295752 debug extra qtcreator-dbg_3.0.1+dfsg+exp-2_amd64.deb b9758678a1e0af609e0d58ce3c3e3a34 8561018 doc optional qtcreator-doc_3.0.1+dfsg+exp-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTKHuyAAoJEKtkX0BihqfQtvkQAKM7OED2iE1Gi51KRDMyoqpc J54B1tC+I2zDzioRTIGS4c3rcGLiF2/ksCsuzbcQPSBX0vg3aVCpe678r9kJk5Dt haqW7Svb/acrjYrEChiuGdWWPvIxAJL49IYeQGz00xs8C0KkBvJ/v92IyZTZR/0w YpSCbEZ4xFZOcTluLLk4iksGPSw3GBfMHhl4Jp1G2A1OVtzOlck5WarcBhYmCWC9 44/9t4ZPJhfXj2ZauaiqPXg/7vvl6dtpSqkux30zeZ5tpEktFyabt82xMFMTjiTA hoxVuJ5mwMcCFdhb2NFHHgbtsjhMygFCGltQSsA0k7KqJ+R5iMPKjoDaAYdRDr5U largPRxhN6zYBVJ8XguCHJhGS8s75JepdoOrC73ay5CjO4dZswRiZmFqpISbatkA gpvZYIDAqSdVV60b6qfrOmJolq2SKI2CPBrmC808R5hylaHM6QWlugLTqBzuzp6g Gz5rJZOgGs+DNGmFfhVY31agsMinR7YleGXPrL1XYqYnFzt0ouw0+KtvvII6fVVY LeDu0Zvedy13Esa6pBMa4YNwdp7dB8rYUwiwbwhpy82sdy+I9viiAUCF56sGRaK1 23ggnSWm/s4QjwLLdoDX7HEnZ6f/zTXr8OCou0DD4YJgMD4ZPOtP9EetKI7UZ5Pi LudF7L8MvN1R+527f3v3 =THQd -END PGP SIGNATURE- Thank you for your contribution to Debian. -- 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/e1wpxfq-0005ch...@franck.debian.org
Re: making-friends-with-kontact-again
On Monday 17 March 2014 17:43:43 David Bate wrote: Just to prevent you wasting your time - I recently reinstalled (with clean configs, and even using the 4.13 alpha) but it did not fix the filtering problem :(. ...oh - thanks for the hint, saves me a lot of time. Somehow surprising that such a small feature like inbound mail filtering is causing trouble for so long :( Thanks for all the replies... Andy
Re: Automounted NFS shares never timeout
On Tuesday 18 March 2014 02:36:36 Michael Schuerig wrote: Anyway, there are no discernable accesses by any KDE component. The fault is probably elsewhere. Then what happens if you test this with - plain console - a very simple session (fvwm + xterm)? Cheers Carsten signature.asc Description: This is a digitally signed message part.
Re: Automounted NFS shares never timeout
On Tuesday 18 March 2014 10:02:43 Carsten Pfeiffer wrote:
On Tuesday 18 March 2014 02:36:36 Michael Schuerig wrote:
Anyway, there are no discernable accesses by any KDE component. The
fault is probably elsewhere.
Then what happens if you test this with
- plain console
- a very simple session (fvwm + xterm)?
On the console and in a KDE session for a freshly created user, the NFS
is automatically unmounted when the timeout expires. In my usual KDE
session, if I kill plasma-desktop, the timeout works, too. Restarting
plasma-desktop causes the share to be automounted again, ie, without any
explicit access to it.
Here's what the pstree output for plasma-desktop looks like:
plasma-desktop
├─ksysguardd
├─{KCupsConnection}
├─{QInotifyFileSys}
├─{QProcessManager}
└─{plasma-desktop}
I've also tried strace'ing plasma-desktop (with -e trace=open and with
grepping for relevant paths), but didn't see any accesses to the share
there.
As I wrote in another reply, I was hoping to get some insight from
autofs. Presumably it needs to know about which accesses and processes
keep a mounted share from timing out. Unfortunately, even at debug
level, no such information is in the log.
Michael
--
Michael Schuerig
mailto:mich...@schuerig.de
http://www.schuerig.de/michael/
signature.asc
Description: This is a digitally signed message part.
Re: Automounted NFS shares never timeout
Hello, i have simillar problem, but with autofs+cifs. I run commands umount -l /mnt/smb4/*/* /etc/init.d/autofs stop before leaving home and suspending my notebook. When i forget to run those commands, plasma-desktop and krunner get stuck after resume. lsof is also stuck. Ussually, killing desktop and krunner helps. I was investigating this several times, without success. One time, i thought, it was caused by ksysguardd. Libor On Monday 17 March 2014 14:46:54 Michael Schuerig wrote: I have a single NFS share automounted by autofs. Once it is mounted, it is never (auto-)unmounted, even though I don't explicityl access it. Lsof does not show any open files below the mount point. My hypothesis is that some process periodically accesses the share, unfortunately, I can't find any such process. I'd have to catch it red- handed exactly when it accesses the share. I was suspecting the Removable Device Automounter (kded_device_automounter) and disabled it, but that didn't change anything. Any suggestion what (if any!) part of KDE might be causing this? Any general suggestion for finding the culprit? Michael
Re: Automounted NFS shares never timeout
On Tuesday 18 March 2014 13:18:20 Libor Klepáč wrote: Hello, i have simillar problem, but with autofs+cifs. I run commands umount -l /mnt/smb4/*/* /etc/init.d/autofs stop before leaving home and suspending my notebook. Somewhere in the autofs docs I read a warning against manually unmounting (or mounting) automounted shares. I don't remember the details. When i forget to run those commands, plasma-desktop and krunner get stuck after resume. lsof is also stuck. Have a look at this bug report https://bugs.kde.org/show_bug.cgi?id=184062 Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1576154.pYFETzoV60@fuchsia
Re: Automounted NFS shares never timeout
On Tuesday 18 March 2014 01:40:53 Michael Schuerig wrote: A notable difference between NFS and sshfs is that in Dolphin the NFS share is shown in the places panel under Devices, whereas the sshfs share is not. That doesn't have to mean anything. I've got four NFS shares on the same server, with all of them having identical entries in fstab (except for the path). 3 of them show up in dolphin, the fourth does not. God knows how the one share is different from the others to dolphin. So I guess that this little bug in dolphin is probably unrelated... My next advice would have been to try inotify, but I saw you already did that… Cheers, Johannes -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1697694.rkcjiJvamT@mani
