Nieuws - goud is een onmisbare bescherming voor schuldenberg van 250 miljard
Beste lezer, We leven in een gepolariseerde wereld vol onzekerheden en die onzekerheden werpen een steeds grotere schaduw af over de economie en over de financiële markten. Eigenlijk is onze wereld een surrealistisch plaatje geworden: iedereen blijft maar schulden maken, we leven er op los alsof er geen morgen bestaat. Zowel overheden, particulieren als bedrijven steken zichzelf steeds dieper in de schulden. Over het juiste bedrag van de uitstaande schulden verschillen de meningen, maar inmiddels zou het al gaan om een bedrag van meer dan 250.000 miljard dollar. Daarbij is rekening gehouden met alle openstaande verplichtingen van de overheden, inclusief sociale zekerheid, pensioenen enzovoort. Zelfs een klein kind zal beseffen dat de huidige situatie niet kan blijven duren, vroeg of laat zal er ergens een radertje vast lopen. En dan zal de (schulden)wagen aan het rollen gaan. GoldCore merkt op dat de globale debt-to-GDP ratio, zeg maar de verhouding schulden ten opzichte van het BBP, is opgelopen tot bijna 320%. Het hoeft geen betoog dat dergelijke verhouding astronomisch hoog is. Mathematisch gezien is het simpelweg onmogelijk geworden om de uitstaande schulden nog ooit terug te betalen. Het vervelende aan schulden is echter dat ze steeds op een bepaald moment in de toekomst terugbetaald moeten worden. De boodschap van GoldCore is dan ook duidelijk: de beleggers krijgen het advies om beschutting op de goudmarkt te zoeken tegen het uit de hand lopen van de schuldensituatie. Goud, zilver en in mindere mate de andere edelmetalen zullen hun waarde behouden wanneer de schuldenzeepbel implodeert, obligaties, aandelen, vastgoed, valuta’s enzovoort zullen dat in veel mindere mate doen. Een explosie van de goudprijs ligt dan ook in de lijn van de verwachtingen, zonder dat GoldCore zich waagt aan een voorspelling omtrent het toekomstig niveau van de goudprijs. Maar dat dit fors boven het huidige prijsniveau ligt, staat als een paal boven water [https://cdn.flxml.eu/lt-2161182922-a58ad5d94de2d7f97a44cf798e395f5b7dec5ef454e14522][1] ![2] [1]: https://cdn.flxml.eu/lt-2161182922-a58ad5d94de2d7f97a44cf798e395f5b7dec5ef454e14522 "https://cdn.flxml.eu/lt-2161182922-a58ad5d94de2d7f97a44cf798e395f5b7dec5ef454e14522"; [2]: https://cdn.flxml.eu//dyn/images/smartbuilder/transparent.png
Processed: [bts-link] source package x11-xkb-utils
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package x11-xkb-utils > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #913359 (http://bugs.debian.org/913359) > # Bug title: xkbcomp.pc requires libxkbfile-dev as dependency > # * https://gitlab.freedesktop.org/xorg/app/xkbcomp/merge_requests/3 > # * remote status changed: (?) -> merged > # * closed upstream > tags 913359 + fixed-upstream Bug #913359 [x11-xkb-utils] xkbcomp.pc requires libxkbfile-dev as dependency Added tag(s) fixed-upstream. > usertags 913359 + status-merged There were no usertags set. Usertags are now: status-merged. > thanks Stopping processing here. Please contact me if you need assistance. -- 913359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][xorg-team/app/xterm] Pushed new tag xterm-344-1
Sven Joachim pushed new tag xterm-344-1 at X Strike Force / app / xterm -- View it on GitLab: https://salsa.debian.org/xorg-team/app/xterm/tree/xterm-344-1 You're receiving this email because of your account on salsa.debian.org.
[bts-link] source package x11-xkb-utils
# # bts-link upstream status pull for source package x11-xkb-utils # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #913359 (http://bugs.debian.org/913359) # Bug title: xkbcomp.pc requires libxkbfile-dev as dependency # * https://gitlab.freedesktop.org/xorg/app/xkbcomp/merge_requests/3 # * remote status changed: (?) -> merged # * closed upstream tags 913359 + fixed-upstream usertags 913359 + status-merged thanks
Bug#919475: marked as done (xterm: No resize larger than display size?)
Your message dated Thu, 14 Feb 2019 17:36:16 + with message-id and subject line Bug#919475: fixed in xterm 344-1 has caused the Debian Bug report #919475, regarding xterm: No resize larger than display size? 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.) -- 919475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xterm Version: 342-1 Hi! I was used to resize the uxterm window quite larger than the actual root window size (and move the window to see parts of it), which may be useful for stuff presenting quite long lines. This used to work at least in version 327-2, and didn't work in 338-1 nor current 342-1. Bisecting it down, it seems this bug was introduced with the import of 334. Though I didn't find an obvious entry in XTerm's changelog. It would be nice to restore the old behavior to allow window sizes larger than the monitor size. Thanks a lot, Jan-Benedict -- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: xterm Source-Version: 344-1 We believe that the bug you reported is fixed in the latest version of xterm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Joachim (supplier of updated xterm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 18:04:18 +0100 Source: xterm Architecture: source Version: 344-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Sven Joachim Closes: 919475 Changes: xterm (344-1) unstable; urgency=medium . * New upstream release. - A check of zIconBeep resource was removed in double-buffer fix in xterm 334. That is used to decide whether to handle struct-notify events. When xterm does handle the events, it may negotiate a new window-size with the window manager. In that case, the limitResize resource setting limited the new window-size to the screen-size. Amended that by eliminating the limit for this special case when double-buffer is configured, and restoring the check for zIconBeep when double-buffer is not configured (Closes: #919475). * Refresh Debian patches. * Update copy of XTerm FAQ to revision 1.378 (dated 2019/01/27). Checksums-Sha1: 7fb582bdc5b3078e2c09f121a41d14224be4d1f9 2406 xterm_344-1.dsc 5333bd575dd8393b159660dcca24a8c8c68f7b2a 1355326 xterm_344.orig.tar.gz 7cca14877116c8076def25c4dc6de211f30f6b9b 251 xterm_344.orig.tar.gz.asc 6b14a4bd36280e2bd75071138f31c32300acd3c9 108868 xterm_344-1.debian.tar.xz 5f4307ec5e37df68b04801cf1ffba5e026b5d70f 8082 xterm_344-1_source.buildinfo Checksums-Sha256: 4a42c1d652ec9f51672c3d7adac8006dd4c54324a3731bc92e7db9b91222595d 2406 xterm_344-1.dsc ccceb8f6119ae24ab422d7ce7c5713114d304c856daf0d922efc198b56accdf5 1355326 xterm_344.orig.tar.gz 75091e7671769ac53d766a642d4d689af3081a258072e05e852898149ad3250b 251 xterm_344.orig.tar.gz.asc fb4d035927e7fe88a6f9d195391b25750265d078332be767a23c89f7bfcba17b 108868 xterm_344-1.debian.tar.xz e18bda204465963f0d35a30fc27b0e9fb76478408171c842846971a1622174fe 8082 xterm_344-1_source.buildinfo Files: 129e274af2473e9de943485b85f777b5 2406 x11 optional xterm_344-1.dsc dc3c0f7033fe4d605db21e239925d3e4 1355326 x11 optional xterm_344.orig.tar.gz c6e3768d968532788d609a581c73f54f 251 x11 optional xterm_344.orig.tar.gz.asc 7a46627d12cd893efee349e0d977db17 108868 x11 optional xterm_344-1.debian.tar.xz f9ca2301f2e44dabd877ae312fd3a9eb 8082 x11 optional xterm_344-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEKF8heKgv5Jai5p4QOxBucY1rMawFAlxln+YACgkQOxBucY1r MaxHXQ//c4FwsTjc5pXfGybWBu7uFVNgWrM9o9SFJymhFDP2HW5OmXMxXFQikCcj qJLTe4dYKCfYpqo6NakzGc/WIEaZHSXAiwY3ZG4+6nBJwpLjvDPu0ScM/Jw6x946 DTwCo1Sd6n/vpRYh19zmCvTYJmnifwUnWxvuZ8ULev98tXJcmGt1S/iaVGn9sFOz csg9OWgbubWt4IguGJhogTvOTWg7s0ZPpnBUyoUQ4fhkSZffSyki29AySlvVomBU QbZW6zJV/SfOVzv5Zdk0ej9fU19FYredUOYortS+F9ha3D6RIFGYErjCqdx+J6tK VtM5oiiiRPFNm1W10zt4p6fHhVBX3P3/j9nsyi+rEtvWl/iFcg53thfPFGbJSWoI dIOPjBUHNrWPqN
Processing of xterm_344-1_source.changes
xterm_344-1_source.changes uploaded successfully to localhost along with the files: xterm_344-1.dsc xterm_344.orig.tar.gz xterm_344.orig.tar.gz.asc xterm_344-1.debian.tar.xz xterm_344-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
xterm_344-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 18:04:18 +0100 Source: xterm Architecture: source Version: 344-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Sven Joachim Closes: 919475 Changes: xterm (344-1) unstable; urgency=medium . * New upstream release. - A check of zIconBeep resource was removed in double-buffer fix in xterm 334. That is used to decide whether to handle struct-notify events. When xterm does handle the events, it may negotiate a new window-size with the window manager. In that case, the limitResize resource setting limited the new window-size to the screen-size. Amended that by eliminating the limit for this special case when double-buffer is configured, and restoring the check for zIconBeep when double-buffer is not configured (Closes: #919475). * Refresh Debian patches. * Update copy of XTerm FAQ to revision 1.378 (dated 2019/01/27). Checksums-Sha1: 7fb582bdc5b3078e2c09f121a41d14224be4d1f9 2406 xterm_344-1.dsc 5333bd575dd8393b159660dcca24a8c8c68f7b2a 1355326 xterm_344.orig.tar.gz 7cca14877116c8076def25c4dc6de211f30f6b9b 251 xterm_344.orig.tar.gz.asc 6b14a4bd36280e2bd75071138f31c32300acd3c9 108868 xterm_344-1.debian.tar.xz 5f4307ec5e37df68b04801cf1ffba5e026b5d70f 8082 xterm_344-1_source.buildinfo Checksums-Sha256: 4a42c1d652ec9f51672c3d7adac8006dd4c54324a3731bc92e7db9b91222595d 2406 xterm_344-1.dsc ccceb8f6119ae24ab422d7ce7c5713114d304c856daf0d922efc198b56accdf5 1355326 xterm_344.orig.tar.gz 75091e7671769ac53d766a642d4d689af3081a258072e05e852898149ad3250b 251 xterm_344.orig.tar.gz.asc fb4d035927e7fe88a6f9d195391b25750265d078332be767a23c89f7bfcba17b 108868 xterm_344-1.debian.tar.xz e18bda204465963f0d35a30fc27b0e9fb76478408171c842846971a1622174fe 8082 xterm_344-1_source.buildinfo Files: 129e274af2473e9de943485b85f777b5 2406 x11 optional xterm_344-1.dsc dc3c0f7033fe4d605db21e239925d3e4 1355326 x11 optional xterm_344.orig.tar.gz c6e3768d968532788d609a581c73f54f 251 x11 optional xterm_344.orig.tar.gz.asc 7a46627d12cd893efee349e0d977db17 108868 x11 optional xterm_344-1.debian.tar.xz f9ca2301f2e44dabd877ae312fd3a9eb 8082 x11 optional xterm_344-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEKF8heKgv5Jai5p4QOxBucY1rMawFAlxln+YACgkQOxBucY1r MaxHXQ//c4FwsTjc5pXfGybWBu7uFVNgWrM9o9SFJymhFDP2HW5OmXMxXFQikCcj qJLTe4dYKCfYpqo6NakzGc/WIEaZHSXAiwY3ZG4+6nBJwpLjvDPu0ScM/Jw6x946 DTwCo1Sd6n/vpRYh19zmCvTYJmnifwUnWxvuZ8ULev98tXJcmGt1S/iaVGn9sFOz csg9OWgbubWt4IguGJhogTvOTWg7s0ZPpnBUyoUQ4fhkSZffSyki29AySlvVomBU QbZW6zJV/SfOVzv5Zdk0ej9fU19FYredUOYortS+F9ha3D6RIFGYErjCqdx+J6tK VtM5oiiiRPFNm1W10zt4p6fHhVBX3P3/j9nsyi+rEtvWl/iFcg53thfPFGbJSWoI dIOPjBUHNrWPqNKkMOLZ0+ruqlSkWuXdQcuB3ZBAGZZRsGna4vB86vCmjbRcxgti iZhK16DOlC3QxIzFmgKE48WV8qPW5PYf8e9obI2svpKbt7BFC2e11Hq3HUzETd4/ /8sYwdZ5gAmsUTSK2AbuXAPUPZ3pimVadaPflPAy4y4xwOOu/4gHqsEoChSqpr3D pYQUj7zHSVvY35sBoPnazKw7XI7upDF5WUzU5XZMEPwEDQd4/BVWgGMjXvyAHkmX VIMr9cSDIWsZOHxbFca96DagQalZKAKVIufRvtNB8NVu2CPh7u0= =TtY2 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Re: Bug#922346: eog: Opened an image and my display server crashed
Control: reassign -1 libgl1-mesa-dri Control: tags -1 + moreinfo On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote: > I opened a png file in eog and my display server crashed. eog shouldn't be able to cause this, even if it wanted to, so this is a bug in the display server or some library it uses. >From the backtrace you provided, I think this is most likely to be an assertion failure in /usr/lib/x86_64-linux-gnu/dri/i965_dri.so, so I'm reassigning this. The Mesa maintainers will want to know more details of your system. The output of `reportbug --template libgl1-mesa-dri` would presumably be useful information. Was the file that you opened in eog particularly large, or otherwise unusual? Thanks, smcv > Here is the relevant part of my syslog: > > Feb 14 20:44:45 debian org.gnome.Shell.desktop[1414]: Window manager warning: > Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for > 0x187 (Visionneur) > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Xwayland: > src/intel/genxml/gen7_pack.h:72: __gen_uint: Assertion `v <= max' failed. > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Backtrace: > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 0: > /usr/bin/Xwayland > (OsLookupColor+0x139) [0x55b8e2f27e09] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 1: > /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fba70a3372f] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 2: > /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x10b) [0x7fba708978bb] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 3: > /lib/x86_64-linux-gnu/libc.so.6 (abort+0x121) [0x7fba70882535] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) unw_get_proc_name > failed: no unwind info found [-10] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 4: > /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fba70882400] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 5: > /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) [0x7fba708900f2] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 6: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_nouveau_vieux+0x416573) [0x7fba6fb6c503] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 7: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_nouveau_vieux+0x416dd5) [0x7fba6fb6cd95] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 8: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_i915+0x136b7b) [0x7fba6f402d8b] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 9: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_i915+0x1370e7) [0x7fba6f403ab7] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 10: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_i915+0x12f041) [0x7fba6f3f3711] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 11: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_i915+0x11a2dc) [0x7fba6f3c952c] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 12: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_nouveau_vieux+0x1ccc7a) [0x7fba6f6d929a] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 13: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > (__driDriverGetExtensions_nouveau_vieux+0x1ccfea) [0x7fba6f6d999a] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 14: > /usr/bin/Xwayland (glamor_create_gc+0xd535) [0x55b8e2df1a05] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 15: > /usr/bin/Xwayland (DamageRegionAppend+0x19f8) [0x55b8e2e98eb8] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 16: > /usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x7b7) [0x55b8e2deef57] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 17: > /usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x67e) [0x55b8e2dee9be] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 18: > /usr/bin/Xwayland (AddTraps+0x3551) [0x55b8e2e8aad1] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 19: > /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55b8e2ef1e6e] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 20: > /usr/bin/Xwayland (InitFonts+0x3b6) [0x55b8e2ef5df6] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 21: > /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fba7088409b] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 22: > /usr/bin/Xwayland (_start+0x2a) [0x55b8e2dc71ea] > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Fatal server error: > Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Caught signal 6 > (Aborted). Server aborting > Feb 14 20:44:46
Processed: Re: Bug#922346: eog: Opened an image and my display server crashed
Processing control commands: > reassign -1 libgl1-mesa-dri Bug #922346 [eog] eog: Opened an image and my display server crashed Bug reassigned from package 'eog' to 'libgl1-mesa-dri'. No longer marked as found in versions eog/3.28.4-2. Ignoring request to alter fixed versions of bug #922346 to the same values previously set > tags -1 + moreinfo Bug #922346 [libgl1-mesa-dri] eog: Opened an image and my display server crashed Added tag(s) moreinfo. -- 922346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922346: eog: Opened an image and my display server crashed
Le jeudi 14 février 2019 à 20:31 +, Simon McVittie a écrit : > Control: reassign -1 libgl1-mesa-dri > Control: tags -1 + moreinfo > > On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote: > > I opened a png file in eog and my display server crashed. > > eog shouldn't be able to cause this, even if it wanted to, so this is > a bug in the display server or some library it uses. > > From the backtrace you provided, I think this is most likely to be an > assertion failure in /usr/lib/x86_64-linux-gnu/dri/i965_dri.so, so > I'm > reassigning this. > > The Mesa maintainers will want to know more details of your system. > The output of `reportbug --template libgl1-mesa-dri` would presumably > be useful information. > > Was the file that you opened in eog particularly large, or otherwise > unusual? No. It was only 1,5MB. It didn't appear to be unusual in any way, but I don't know if it was a fully valid PNG file. Michel Le Bihan
