Bug#767559: geoip-database-extra, geoip-database-contrib: error when trying to install together
reassign #767559 geoip-database-contrib thanks Hi, this has to be fixed in the -contrib packaging. Am 01.11.2014 um 04:05 schrieb Andreas Beckmann: > Package: geoip-database-extra,geoip-database-contrib > Version: 1.17 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > Control: found -1 20141027-1 > > Architecture: amd64 > Distribution: sid > > Hi, > > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > Selecting previously unselected package geoip-database-extra. > (Reading database ... 8794 files and directories currently installed.) > Preparing to unpack .../geoip-database-extra_20141027-1_all.deb ... > Unpacking geoip-database-extra (20141027-1) ... > dpkg: error processing archive > /var/cache/apt/archives/geoip-database-extra_20141027-1_all.deb (--unpack): >trying to overwrite '/usr/share/GeoIP/GeoIPASNum.dat', which is also in > package geoip-database-contrib 1.17 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Errors were encountered while processing: >/var/cache/apt/archives/geoip-database-extra_20141027-1_all.deb > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality. > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > usr/share/GeoIP/GeoIPASNum.dat > > This bug is assigned to both packages. If you, the maintainers of > the two packages in question, have agreed on which of the packages will > resolve the problem please reassign the bug to that package. You may > also register in the BTS that the other package is affected by the bug. > > Cheers, > > Andreas > > PS: for more information about the detection of file overwrite errors > of this kind see http://edos.debian.net/file-overwrites/. > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#758716: tgt: init script not LSB compliant
Am 16.09.2014 um 11:55 schrieb Apollon Oikonomopoulos: >> a) stop vs. forcedstop >> stop does not work if there are still open sessions: >> # /etc/init.d/tgt stop ; echo $? >> [FAIL] Stopping target framework daemon: tgtd failed! >> Some initiators are still connected - could not stop tgtd >> 2 >> I had to change the use of stop() to forcedstop(), so that tgt works with >> HeartBeat. > > This is intentional and I am a bit reluctant to change the behavior at > this point (although under systemd we default to forcedstop, having no > ability to define custom actions). I'll think a bit more about > defaulting to a hard behavior before the next release. Note that failing > in this case does not seem to be an LSB violation. Think about stopping a SQL or Webservice, where are still (and any time) users. Not stopping on stop is buggy :( -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#762132: [Pkg-fglrx-devel] Bug#762132: fglrx-driver: Update to 1:14.6~ga14.201-1 amd64: Mouse cursor gone
Am 18.09.2014 um 21:33 schrieb Harald: Package: fglrx-driver Version: 1:14.6~ga14.201-1 Severity: important Dear Maintainer, Installing 1:14.6~ga14.201-1 worked flawlessly, but the mouse cursor is not displayed even if I can use the mouse. Updating xserver and depending packages from testing to 2:1.16.0.901-1 showed no effect. I used aticonfig --initial and used my old xorg.conf --> no difference Option "HWCursor" "off" in xorg.conf showed no effect. Thanks for helping to give the cursor back ;) Nobody asked for a cursor, just for new Xserver support ;-) Which desktop environment are you using? On KDE I couldn't reproduce this issue. Could you try out another one? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760773: [Mlt-devel] Fwd: Processed: no audio since binNMU to link against newer libav*
Am 23.09.2014 um 06:30 schrieb Dan Dennedy: > On Mon, Sep 22, 2014 at 6:33 AM, Patrick Matthäi <mailto:pmatth...@debian.org>> wrote: > > Hi Dan, > > it seems as mlt is unable to render audio since we have updated > libav to version 11-1. > Are you aware of such an issue? > > Here are all information: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761593 > > > Hi Patrick, > I just fixed this issue in MLT git commit 3ac0201. You might be able to > cherry-pick this as-is and apply it to 0.9.2, but if not, it should be > easy to recreate manually. I tried to keep it as minimal as possible to > facilitate that. As such, it does not address the other problem you > reported recently about using stream.codec.time_base instead of > stream.time_base. The fix for that problem and other API deprecations > requires more regression testing and time. I feel fairly confident that > the change in commit for this bug is backwards compatible. > Much thanks for your quick fix! Jonas already reported, that your patch is working for him. I will upload tomorrow a fixed package :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#762725: ITP: apt-dater-host -- host helper application for apt-dater
Package: wnpp Severity: wishlist Owner: "Patrick Matthäi" * Package name: apt-dater-host Version : 1.0.0~ Upstream Author : Thomas Liske * URL : https://github.com/DE-IBH/apt-dater-host * License : GPL2+ Programming Lang: Perl Description : host helper application for apt-dater -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739054: [Pkg-fglrx-devel] Bug#739054: fglrx-driver: fglrx segfault
Am 21.07.2014 um 16:34 schrieb Andrey Gursky: > Hi, > > on Jessie amd64 with > fglrx 14.4.2-1 > xserver-xorg 1.15.1-1 > > chromium 36.0.1985.36-1 is the last one that crashes, 36.0.1985.84-1 > is the next one available on amd64 that doesn't crash anymore, such as > newer beta releases. > > A drawback: WebGL support is disabled. Turning it on with > chrome://flags didn't help. > > Regards, > Andrey > > ___ > Pkg-fglrx-devel mailing list > pkg-fglrx-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fglrx-devel > Could you please retest it with the current release in jessie/sid? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#757329: apt-dater: Multi-Arch updates are not detected
Package: apt-dater-host Version: 0.9.0-3+wheezy1 Severity: important File: apt-dater Tags: upstream If you are e.g. on amd64 and also have installed i386 multiarch libs, apt-dater does not detect and install updates for it. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-dater-host depends on: ii debconf [debconf-2.0] 1.5.49 ii libapt-pkg-perl0.1.26+b1 ii libimvirt-perl 0.9.4-4 ii lsb-release4.1+Debian8+deb7u1 ii openssh-server 1:6.0p1-4+deb7u2 ii perl 5.14.2-21+deb7u1 Versions of packages apt-dater-host recommends: ii imvirt 0.9.4-4 ii sudo1.8.5p2-1+nmu1 apt-dater-host suggests no packages. -- Configuration Files: /etc/sudoers.d/apt-dater-host [Errno 13] Keine Berechtigung: u'/etc/sudoers.d/apt-dater-host' -- debconf information: apt-dater-host/assume_yes: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757723: geoip-database: Would be nice to have GeoLite2 databases packaged
Hello, the problem is not that they do not provide the data sources (.csv), but there is no way to build those .csv data to the binary format required by GeoIP itself. If you are skilled in C++ you may extend the geoip-generator from the Debian geoip sources itself. If there is a way to build those data I would be happy to provide them. Am 10.08.2014 um 22:02 schrieb Andrew Moise: Package: geoip-database Version: 20140710-1 Severity: wishlist Hello. It would be nice to have packaged up the free city data that maxmind now makes available: http://dev.maxmind.com/geoip/geoip2/geolite2/ Thanks for your time, take care. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.11 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash geoip-database depends on no packages. Versions of packages geoip-database recommends: ii libgeoip1 1.6.2-1 geoip-database suggests no packages. -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757723: geoip-database: Would be nice to have GeoLite2 databases packaged
Am 11.08.2014 um 16:25 schrieb Andrew Moise: Hm, I'm not too familiar with geoip or its situation in Debian. My thought for how to handle this would be to package the GeoLite2 databases (not .csv but .mmdb) and the APIs for them that Maxmind provides, both as packages that are separate from the existing geoip packages. But, I would mostly defer to your judgement -- I am capable with C++ and could also extend the geoip-generator. That would be nice! :) What's the reason for not just packaging the GeoLite2 .mmdb files and the new API as Maxmind provides them? I'm still not 100% sure about what the existing situation is. Mostly my motivation is simply It is non-free if it is not buildable from source. that I'm working with a tool for which it would be useful if Debian could, out of the box, resolve IP addresses to city names for me. Then you also could get happy with geoip-database-contrib. Thanks. -Andrew On Mon, Aug 11, 2014 at 9:57 AM, Patrick Matthäi wrote: Hello, the problem is not that they do not provide the data sources (.csv), but there is no way to build those .csv data to the binary format required by GeoIP itself. If you are skilled in C++ you may extend the geoip-generator from the Debian geoip sources itself. If there is a way to build those data I would be happy to provide them. Am 10.08.2014 um 22:02 schrieb Andrew Moise: Package: geoip-database Version: 20140710-1 Severity: wishlist Hello. It would be nice to have packaged up the free city data that maxmind now makes available: http://dev.maxmind.com/geoip/geoip2/geolite2/ Thanks for your time, take care. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.11 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash geoip-database depends on no packages. Versions of packages geoip-database recommends: ii libgeoip1 1.6.2-1 geoip-database suggests no packages. -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757723: geoip-database: Would be nice to have GeoLite2 databases packaged
Am 12.08.2014 um 05:06 schrieb Gregory Oschwald: > Although MaxMind does not provide a writer for the legacy database > format, it does provide a writer for the format used by GeoLite2 / GeoIP2: > > https://github.com/maxmind/MaxMind-DB-Writer-perl > > There is also a specification at: > > https://github.com/maxmind/MaxMind-DB/blob/master/MaxMind-DB-spec.md > > Greg From my last information GeoIP2 is a complete rewrite and not finished for productive environments, yet. Maybe it also would be better to provide geoip and "geoip2" as seperate source packages.. Anyway the MaxMind DB Writer is not useful for the current format and where I last have got a chat with one from MaxMind: it is also not working, but things could have been changed.. So what should we do now with this bugreport? I would personaly prefer a volunter who is able to extend the geoip-generator to support the city database as input and output. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#765974: kdenlive: KDE help fails to load gzipped documentation files
tag #765974 + pending thanks Thanks, this will be fixed with the next upload! Am 19.10.2014 um 21:05 schrieb Vincent Pinon: > Package: kdenlive > Version: 0.9.10-1 > Severity: normal > > Reported Upstream: > http://www.kdenlive.org/mantis/view.php?id=3156 > > Reported on Ubuntu: > https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1219476 > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages kdenlive depends on: > ii kde-runtime 4:4.14.1-1 > ii kdenlive-data 0.9.10-1 > ii libav-tools 6:11-1 > ii libc6 2.19-11 > ii libgcc1 1:4.9.1-16 > ii libgl1-mesa-glx [libgl1] 10.2.8-1 > ii libglu1-mesa [libglu1]9.0.0-2 > ii libkdecore5 4:4.14.1-1 > ii libkdeui5 4:4.14.1-1 > ii libkio5 4:4.14.1-1 > ii libknewstuff3-4 4:4.14.1-1 > ii libknotifyconfig4 4:4.14.1-1 > ii libkrossui4 4:4.14.1-1 > ii libmlt++3 0.9.2-2 > ii libmlt6 0.9.2-2 > ii libnepomuk4 4:4.14.1-1 > ii libqjson0 0.8.1-3 > ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 > ii libsolid4 4:4.14.1-1 > ii libsoprano4 2.9.4+dfsg-1.1 > ii libstdc++64.9.1-16 > ii libx11-6 2:1.6.2-3 > ii libxau6 1:1.0.8-1 > ii libxdmcp6 1:1.1.1-1 > ii libxext6 2:1.3.3-1 > ii melt 0.9.2-2 > > Versions of packages kdenlive recommends: > ii dvdauthor0.7.0-1.2+b1 > pn dvgrab > ii frei0r-plugins 1.4-3 > ii genisoimage 9:1.1.11-3 > pn recordmydesktop > pn swh-plugins > > Versions of packages kdenlive suggests: > ii khelpcenter4 4:4.14.1-1 > > -- no debconf information > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#766676: [Pkg-fglrx-devel] Bug#766676: /usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/linux/libglx.so: undefined symbol: LoadExtension
rwx 1 root root 30 Oct 24 14:54 /etc/alternatives/glx--linux-libglx.so > -> /usr/lib/fglrx/fglrx-libglx.so > > File System: > lrwxrwxrwx 1 root root 21 Oct 24 14:54 /usr/lib/glx -> > /etc/alternatives/glx > lrwxrwxrwx 1 root root 50 Oct 24 14:54 > /usr/lib/x86_64-linux-gnu/libGL.so.1 -> > /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu > -rw-r--r-- 1 root root 286120 Sep 22 17:49 > /usr/lib/xorg/modules/extensions/libglx.so > > > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (900, 'testing'), (600, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages fglrx-driver depends on: > ii debconf [debconf-2.0] 1.5.53 > ii glx-alternative-fglrx 0.4.2 > ii libc6 2.19-11 > ii libfglrx 1:14.9+ga14.201-2 > ii libgl1-mesa-glx [libgl1] 10.2.8-1 > ii libx11-6 2:1.6.2-3 > ii libxext6 2:1.3.3-1 > ii libxrandr2 2:1.4.2-1 > ii libxrender11:0.9.8-1 > ii xserver-xorg-core [xorg-video-abi-18] 2:1.16.1-1 > > Versions of packages fglrx-driver recommends: > ii fglrx-atieventsd 1:14.9+ga14.201-1 > ii fglrx-modules-dkms [fglrx-kernel-14.9+ga14.201] 1:14.9+ga14.201-1 > ii libgl1-fglrx-glx 1:14.9+ga14.201-2 > pn libgl1-fglrx-glx-i386 > > Versions of packages fglrx-driver suggests: > pn amd-opencl-icd > ii fglrx-control 1:14.9+ga14.201-2 > pn xvba-va-driver > > Versions of packages xserver-xorg-video-intel depends on: > ii libc6 2.19-11 > ii libdrm-intel1 2.4.58-2 > ii libdrm2 2.4.58-2 > ii libpciaccess0 0.13.2-3 > ii libpixman-1-0 0.32.6-3 > ii libudev1 215-5+b1 > ii libx11-6 2:1.6.2-3 > ii libx11-xcb12:1.6.2-3 > ii libxcb-dri2-0 1.10-3 > ii libxcb-util0 0.3.8-3 > ii libxcb11.10-3 > ii libxv1 2:1.0.10-1 > ii libxvmc1 2:1.0.8-2 > ii xserver-xorg-core [xorg-video-abi-18] 2:1.16.1-1 > > Versions of packages fglrx-driver is related to: > pn ia32-libs > ii libdrm-radeon1 2.4.58-2 > pn linux-headers > ii xserver-xorg 1:7.7+7 > ii xserver-xorg-core 2:1.16.1-1 > ii xserver-xorg-video-ati 1:7.5.0-1 > ii xserver-xorg-video-radeon 1:7.5.0-1 > > -- debconf information: > * fglrx-driver/needs-xorg-conf-to-enable: > fglrx-driver/check-xorg-conf-on-removal: true > fglrx-driver/removed-but-enabled-in-xorg-conf: > > ___ > Pkg-fglrx-devel mailing list > pkg-fglrx-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fglrx-devel > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#735047: [Pkg-fglrx-devel] Bug#735047: Possible solution
reassign #735047 glx-alternative-fglrx thanks Am 25.09.2014 um 21:31 schrieb Alexander Kudrevatykh: I retested this patch with latest jessie updates and it helps -- Alexander Kudrevatykh В Срд, 24/09/2014 в 22:02 +0200, Patrick Matthäi пишет: >Am 04.05.2014 um 13:19 schrieb Drill Main: > >I suffered from the same bug too, but I think the solution is such that: > >when we switch to igpu mode, original libglx.so must be restored too. At > >least I understood it this way after inspecting "switchlibglx" script > >from original amd driver installator. > > > >Thus the bug occured only in dpkg alternatives file > >"/var/lib/dpkg/alternatives/glx".Thus i propose such patch: > > > >diff -ruPN a/var/lib/dpkg/alternatives/glx b/var/lib/dpkg/alternatives/glx > >--- a/var/lib/dpkg/alternatives/glx 2014-05-04 12:26:36.0 +0400 > >+++ b/var/lib/dpkg/alternatives/glx 2014-05-04 15:15:00.258850761 +0400 > >@@ -24,7 +24,7 @@ > > /usr/lib/fglrx/fglrx_drv.so > > /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 > > /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 > > -/usr/lib/fglrx/fglrx-libglx.so > > + > > /usr/lib/mesa-diverted > > 5 > > > >After that igpu mode seems to be working properly (at least as far as I > >can say). > >Could you please retest it with the current release in jessie/sid? > > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#769335: otrs2: fails to upgrade from 'wheezy': /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with non-zero status
Where is your Database.pm or which permissions does it have? Von meinem iPad gesendet > Am 12.11.2014 um 22:51 schrieb Andreas Beckmann : > > Package: otrs2 > Version: 3.3.9-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'wheezy'. > It installed fine in 'wheezy', then the upgrade to 'jessie' fails. > >> From the attached log (scroll to the bottom...): > > Setting up otrs2 (3.3.9-1) ... > dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf > Replacing config file /etc/otrs/database.pm with new version > creating database backup in > /var/cache/dbconfig-common/backups/otrs2_3.1.7+dfsg1-8+deb7u4.pgsql. > applying upgrade script for 3.1.7+dfsg1-8+deb7u4 -> 3.2.1. > Can't locate /etc/otrs/database.pm: Permission denied at > /usr/share/otrs/Kernel/Config.pm line 27. > BEGIN failed--compilation aborted at /usr/share/otrs/Kernel/Config.pm line > 37. > Compilation failed in require at ./scripts/DBUpdate-to-3.2.pl line 32. > BEGIN failed--compilation aborted at ./scripts/DBUpdate-to-3.2.pl line 32. > error encountered processing > /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1: > /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with > non-zero status > dbconfig-common: otrs2 configure: aborted. > dbconfig-common: flushing administrative password > dpkg: error processing package otrs2 (--configure): > subprocess installed post-installation script returned error exit status 1 > Setting up libsoap-lite-perl (1.11-1) ... > Processing triggers for libc-bin (2.19-12) ... > Processing triggers for ca-certificates (20141019) ... > Updating certificates in /etc/ssl/certs... 10 added, 8 removed; done. > Running hooks in /etc/ca-certificates/update.ddone. > Errors were encountered while processing: > otrs2 > > > cheers, > > Andreas > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769335: otrs2: fails to upgrade from 'wheezy': /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with non-zero status
tag #769335 + moreinfo thanks Am 12.11.2014 um 22:51 schrieb Andreas Beckmann: > Setting up otrs2 (3.3.9-1) ... > dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf > Replacing config file /etc/otrs/database.pm with new version > creating database backup in > /var/cache/dbconfig-common/backups/otrs2_3.1.7+dfsg1-8+deb7u4.pgsql. > applying upgrade script for 3.1.7+dfsg1-8+deb7u4 -> 3.2.1. > Can't locate /etc/otrs/database.pm: Permission denied at > /usr/share/otrs/Kernel/Config.pm line 27. > BEGIN failed--compilation aborted at /usr/share/otrs/Kernel/Config.pm line > 37. > Compilation failed in require at ./scripts/DBUpdate-to-3.2.pl line 32. > BEGIN failed--compilation aborted at ./scripts/DBUpdate-to-3.2.pl line 32. > error encountered processing > /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1: > /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with > non-zero status > dbconfig-common: otrs2 configure: aborted. > dbconfig-common: flushing administrative password > dpkg: error processing package otrs2 (--configure): >subprocess installed post-installation script returned error exit status 1 > Setting up libsoap-lite-perl (1.11-1) ... > Processing triggers for libc-bin (2.19-12) ... > Processing triggers for ca-certificates (20141019) ... > Updating certificates in /etc/ssl/certs... 10 added, 8 removed; done. > Running hooks in /etc/ca-certificates/update.ddone. > Errors were encountered while processing: >otrs2 I have checked it up in a virtual machine and can not reproduce this issue, maybe another "in-piuparts-world-only-error" issue. From what I see here: => dbconfig creates and handle database.pm and it is generated with the following values: dbc_generate_include_owner="otrs:www-data" dbc_generate_include_perms="0640" => Can't locate /etc/otrs/database.pm: Permission denied at /usr/share/otrs/Kernel/Config.pm line 27. => line 26 checks for the existance of database.pm. if it exists (-f) then a require is executed in line 27, which is the case here, but you have got wrong permissions? which ones? => this whole issue is not triggered in my manual wheezy->jessie upgrade process => and again, dbconfig-common handles this file, but I think the bug is in your testing suite/piuparts -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#767370: does not start debconf, displays debconf commands and waits for input
Am 14.11.2014 um 10:57 schrieb Thijs Kinkhorst: > On Thu, November 13, 2014 22:49, Thomas Liske wrote: >> tag 767370 upstream,fixed-upstream >> thanks >> >> >> Hi Thijs, >> >> needrestart did not find any kernel images which triggers this special >> bug. There was a divison by zero triggered by calculating the >> progressbar length. >> >> needrestart did not die since the linux specific stuff was running in an >> eval block. needrestart was not started in verbose mode so it does not >> report the error message (divsion by zero) of the eval call. >> >> While dieing in the eval block the stdout/stdin fd's were left screwed >> up... resulting in the debconf commands on the tty. >> >> In verbose mode the bug was not triggered since verbose mode disables >> the progressbar stuff. > > Thanks. Good that it was found. This is a Xen domU which indeed does not > have any linux-* packages installed since it runs the host kernel. > > Can we have a targeted fix for this in unstable that fits the jessie > unfreeze policy? Targeted! But first I would like to see 1.2-4 in testing, after it has been aged. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#769544: needrestart: prompts user without following Debian Configuration Management Specification - accesses /dev/tty
Am 14.11.2014 um 13:07 schrieb Andreas Beckmann: > Well, there shouldn't any output get on that console ..., so let's look > at the running processes: > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > needresta 20673 root cwdDIR 0,19 60 532392089 > /tmp/piupartss/tmpubCt88/tmp > needresta 20673 root rtdDIR 0,19 460 532372904 > /tmp/piupartss/tmpubCt88 > needresta 20673 root txtREG 0,1910416 532382504 > /tmp/piupartss/tmpubCt88/usr/bin/perl > needresta 20673 root memREG 0,1918728 532387760 > /tmp/piupartss/tmpubCt88/usr/lib/x86_64-linux-gnu/perl/5.20.1/auto/IO/IO.so > > needresta 20673 root memREG 0,19 1827768 532387323 > /tmp/piupartss/tmpubCt88/usr/lib/x86_64-linux-gnu/libperl.so.5.20.1 > needresta 20673 root memREG 0,19 140928 532442638 > /tmp/piupartss/tmpubCt88/lib/x86_64-linux-gnu/ld-2.19.so > needresta 20673 root0r CHR5,0 0t0 532392052 > /tmp/piupartss/tmpubCt88/dev/tty > needresta 20673 root1w CHR5,0 0t0 532392052 > /tmp/piupartss/tmpubCt88/dev/tty > needresta 20673 root2w FIFO0,8 0t0 532480261 pipe > needresta 20673 root3r REG 0,19 3485 532493945 > /tmp/piupartss/tmpubCt88/usr/share/perl5/NeedRestart/UI/Debconf.pm > needresta 20673 root4r FIFO0,8 0t0 532499621 pipe > needresta 20673 root5w FIFO0,8 0t0 532499622 pipe > needresta 20673 root6r FIFO0,8 0t0 532579111 pipe > > You may not access /dev/tty for prompting (or whatever) ... > use debconf *properly*. Hi, I think this is a duplicate of bug #767370 Could you add a linux-image to your piuparts packages and test, if the issue is gone away (not that there is another one)? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#769335: otrs2: fails to upgrade from 'wheezy': /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with non-zero status
Am 14.11.2014 um 10:54 schrieb Paul Gevers: >> => dbconfig creates and handle database.pm and it is generated with the >> following values: >> dbc_generate_include_owner="otrs:www-data" >> dbc_generate_include_perms="0640" >> >> => Can't locate /etc/otrs/database.pm: Permission denied at >> /usr/share/otrs/Kernel/Config.pm line 27. >> >> => line 26 checks for the existance of database.pm. if it exists (-f) >> then a require is executed in line 27, which is the case here, but you >> have got wrong permissions? which ones? >> >> => this whole issue is not triggered in my manual wheezy->jessie upgrade >> process >> >> => and again, dbconfig-common handles this file, but I think the bug is >> in your testing suite/piuparts > > We had a bug in dbconfig-common exactly in this area. It might be that > this bug is a duplicate of bug 767248 that was fixed recently. Much thanks for pointing to this Paul! @Andreas: Could you please retest with an up-to-date dbconfig-common? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#769582: amarok gets silent on manual song changes
Package: amarok Version: 2.8.0-2.1+b1 Severity: grave Hello, first: I were not realy sure if severity grave is realy correct, since most amarok functions are working. But after some hours I have decided that this is a grave error, since it is not usable as media player anymore. Problem description: - If I start amarok and then start a song on the right side (eg doubleclick) it starts playing. If I manualy change the song again on the right side audio output is not working anymore until I restart amarok - if I start amarok and only using the back- and forward button to change songs, everything is working. but if I start again a song manualy, no audio output - automatic song changes also work fine So amarok is here not able to produce any audio output, after I have changed (not initialy started) a song in my playlist. I have started amarok with "--nofork --debug" and attached the full log. It contains the following: - starting of amarok with --nofork and --debug - starting to play a song - manualy switching the song again (no audio output anymore). _BEFORE_ I switched the song, I have marked the location with ">>> now changing manual" at line 955 Hope this will help you to identify the issue. You can also contact me on IRC (the-me). -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ amarok.debug.log.gz Description: application/gzip signature.asc Description: OpenPGP digital signature
Bug#769544: needrestart: prompts user without following Debian Configuration Management Specification - accesses /dev/tty
Am 15.11.2014 um 18:32 schrieb Thomas Liske: > But that's just academic - the bug is silly and needs to be fixed > for jessie without any doubt. ACK. > Paravirtualized using libvirt AFAIK - there are many other > virtualization environments requiring a kernel image inside the > container. But the bug should keep a severity of serious[1] if it > violates the debian policy. The severity is OK for me, since this bug affects some well known container based virtualization platforms and also chroots, if /boot is missing with kernel images. Common scenarios. >> The current upload you want to get into jessie was only uploaded with >> priority=low. If the upstream fix for this bug here gets backported >> and uploaded with priority=medium it would be eligible for migration >> at the same time. I think you should do that, especially since I do >> not see an unblock request for the current version in sid. > > The patch for #767370 and #769544 has not been uploaded by Patrick, yet. I have just uploaded needrestart=1.2+git20141115-1 to experimental (for additional testing). The next jessie/unstable upload *will* fix this issue, but first I want to see 1.2-4 in jessie (since it has got some more changes). -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#769723: unblock: kid3/3.1.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kid3 It adds the missing manpages (where kid3.1 itself links to). diff -Naur '--exclude=.svn' 3.1.1-1/debian/changelog 3.1.1-2/debian/changelog --- 3.1.1-1/debian/changelog2014-11-11 22:43:22.053641657 +0100 +++ 3.1.1-2/debian/changelog2014-11-13 21:55:16.879633742 +0100 @@ -1,3 +1,9 @@ +kid3 (3.1.1-2) unstable; urgency=low + + * Add missing kid3-core manpages. Thanks to Achim Bohnet. + + -- Patrick Matthäi Thu, 13 Nov 2014 21:44:24 +0100 + kid3 (3.1.1-1) unstable; urgency=medium * New upstream release. diff -Naur '--exclude=.svn' 3.1.1-1/debian/kid3-core.manpages 3.1.1-2/debian/kid3-core.manpages --- 3.1.1-1/debian/kid3-core.manpages 1970-01-01 01:00:00.0 +0100 +++ 3.1.1-2/debian/kid3-core.manpages 2014-11-13 21:55:16.879633742 +0100 @@ -0,0 +1,2 @@ +kid3-build/doc/en/kid3-core.1 +kid3-build/doc/de/kid3-core.de.1 unblock kid3/3.1.1-2 -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#814009: glusterfs-server: Does not work after upgrade (e. g. mount not possible anymore)
fu** now it is migrated to testing :/ Am 07.02.2016 um 15:14 schrieb Thomas Renard: Package: glusterfs-server Version: 3.7.7 Severity: important Dear Maintainer, after upgrading to 3.7.7 mounting is not possible anymore. glusterfs volume somevolume heal info returns a failed to get the 'volume file' from server This seems to be an upstream problem - I tried to find something which fits. see: http://www.spinics.net/lists/gluster-users/msg25434.html here the fix seems to in version 3.7.8 according to developer Joe Julian. The main problem seems to be a wrong scripting for upgrade (second post in thread). Downgrading to 3.7.6-1+b1 from snapshots rescued my system. Because of the complexity I do not have any more hints (sorry about that). I hope Severity: important is good - my systems do not work after upgrade because they use glusterfs via https://github.com/calvera/docker-volume-glusterfs which does not startup either. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages glusterfs-server depends on: ii glusterfs-client 3.7.7 ii glusterfs-common 3.7.7 ii libacl1 2.2.52-2 ii libc6 2.21-7 ii libncurses5 6.0+20151024-2 ii libreadline6 6.3-8+b4 ii libssl1.0.2 1.0.2f-2 ii libtinfo5 6.0+20151024-2 ii libuuid1 2.27.1-3 ii libxml2 2.9.3+dfsg1-1 ii lsb-base 9.20160110 ii python2.7.11-1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages glusterfs-server recommends: ii nfs-common 1:1.2.8-9 glusterfs-server suggests no packages. -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations
Am 13.02.2016 um 09:53 schrieb Dmitry Smirnov: Source: otrs2 Version: 5.0.6-1 Severity: serious I'm quite shocked to find how badly otrs2 packaging violates DFSG. There are many non-distributrable pre-built (minified) source-less files in orig tarball under "var/httpd/htdocs/js/thirdparty". No attemps to fix this situation has been and some inconvenient lintian warnings (such as "source- contains-prebuilt-javascript-object" and "source-contains-prebuilt-flash- object") are hidden through use of lintian-overrides. Moreover many bundled third party components are not even documented in "debian/copyright". :( :( Fixing those problems is neigher optional nor hard. To comply with policy sources of minified files can be shipped in "debian/missing-sources". Minified files can be replaced on build time with their uncompressed original files or even with files minified by build srcipts (if you believe in minification). Where appropriate you can certainly use system libjs-* packages and there is already bug for that: #695664. At your convenience you can use "dh_linktree" or "dh_link" helpers to facilitate replacement. New `uscan` functionality allows to do DFSG-repackaging by utilising "copyright/Files-Excluded" field -- you can read more about that in https://wiki.debian.org/UscanEnhancements (Also it might be helpful to add "repacksuffix=+dfsg" to "debian/watch"). Finally you don't have to document copyrights and licenses for files that were dropped from orig.tar. You are not the only maintainer who have to deal with pesky bundled non-DFSG third party components. Just recently yours truly had to fix package "ckeditor" because one of my packages bundles it. Therefore I'm confident that you can replace "ckeditor" bundled to "otrs2" with "ckeditor (>= 4.5.6~)" right now and that it is safe to do so. Please address all those problems ASAP. I do not comply with your report. I am aware of those issues, that is also why the embedded-code-copies bug is marked as "need help". OTRS packaging is a hard job and mostly it is not possible to replace the libjs thirdparty foo with the packages from Debian, mostly because of version missmatches. Nobody is willed (or in my case able) to fix those JS issues, which appear here and then with different versions in different places (ugly JS sh..). If everything is simple for you and just replacements have to be done (which is not the case) then I would be happy to welcome you on the otrs-packaging board. Just a short example: With 5.0.1-2 I had to drop (and inform the security team) about removing again the use of the libjs-jquery* packages from Debian, because of #802938 -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#813805: Package: otrs Version: 5.0.6-1~bpo8+1;3.3.9-3
Am 05.02.2016 um 12:53 schrieb alex bachmer: Package: otrs Source: otrs2 Version: 5.0.6-1~bpo8+1 Installed-Size: 227 Maintainer: Patrick Matthäi Architecture: all Depends: otrs2 Description-en: Open Ticket Request System (OTRS 5) OTRS is an Open source Ticket Request System (also well known as trouble ticket system) with many features to manage customer telephone calls and e-mails. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. . This package depends on the otrs2 5.x series package. Description-md5: 8e0a7b6c0c591bed07ede62404238eb1 Homepage: http://www.otrs.org Section: web Priority: optional Filename: pool/main/o/otrs2/otrs_5.0.6-1~bpo8+1_all.deb Size: 198484 MD5sum: 91db5a75a732c02c7cfbbcff2527b628 SHA1: 9aed0cf1cc6e393195129377b003d003af0d576c SHA256: b648c6bb61fbec3f0487ef2ef6df18c8405aad3287933e7586a2d1662caa991f Package: otrs Source: otrs2 Version: 3.3.9-3 Installed-Size: 232 Maintainer: Patrick Matthäi Architecture: all Depends: otrs2 Description-en: Open Ticket Request System (OTRS 3) OTRS is an Open source Ticket Request System (also well known as trouble ticket system) with many features to manage customer telephone calls and e-mails. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. For a detailed documentation see package otrs-doc-en or otrs-doc-de. . This package depends on the otrs2 3.x series package. Description-md5: 82b96b585b49727738ceb801d1535372 Homepage: http://www.otrs.org Tag: devel::lang:sql, interface::web, network::server, role::program, web::application, works-with::bugs, works-with::db, works-with::mail Section: web Priority: optional Filename: pool/main/o/otrs2/otrs_3.3.9-3_all.deb Size: 183970 MD5sum: 6fd18cc0935ab59814c5dc48b5dc5095 SHA1: d61a30900a2332c5ed81d75d4bd3c5b7bd2224cf SHA256: 21c89d52f77446aecd2b54695eb07104196998101bb08c1c7fba25311cae86e0 Hi After installing otrs, if i want to work on a ticket, i get the following error: (a messagebox apears with this message) "An error occurred! Do you want to see the complete error message?" after pressing ok button, it shows me: "CKEDITOR.instances[EditorID] is undefined" I use version:5.0.6-1~bpo8+1, but both version shows me the same error. thank you for your help alex I can not reproduce your issue. I am also using the bpo package here in a bigger company.. Can you reproduce this issue on a _fresh_ system with a _fresh_ browser? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#815112: Also add v6 databases
Am 19.02.2016 um 00:04 schrieb Vincent Bernat: Package: geoip-database-extra Version: 20160210-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! It would be pretty useful if you could also add the v6 versions for GeoIPASNum and GeoIPCity. They are also available from the same sources. ACK, but the build programs need support (patches) for it. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#815501: mlt: FTBFS on kfreebsd: error: variable 'req' has initializer but incomplete type
Am 22.02.2016 um 03:09 schrieb Steven Chamberlain:
> tags 815501 + patch
> user debian-...@lists.debian.org
> usertags 815501 + kfreebsd
> thanks
>
> Hi,
>
> Andreas Beckmann wrote:
>> starting with version 6 mlt FTBFS on kfreebsd-i386 and kfreebsd-amd64:
>> https://buildd.debian.org/status/fetch.php?pkg=mlt&arch=kfreebsd-amd64&ver=6.0.0-2&stamp=1455825880
>>
>> [...]
>> cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
>> -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre
>> -ffast-math-g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread
>> -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre
>> -ffast-math-g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread
>> -I../.. -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts
>> -fno-tree-pre -ffast-math-g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
>> -fPIC -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -c -o consumer_cbrts.o
>> consumer_cbrts.c
>> consumer_cbrts.c: In function 'create_socket':
>> consumer_cbrts.c:583:12: error: variable 'req' has initializer but
>> incomplete type
>> struct ip_mreqn req = {{0}};
>> ^
>
> Unfortunately GNU/kFreeBSD uses a netinet/ip.h provided by GNU libc,
> not the FreeBSD one, so it doesn't have struct ip_mreqn.
>
> Until we have that, this feature can be easily disabled with the
> attached patch, allowing the rest of mlt to build successfully.
>
Thanks for your explaination. So we know now, that it is not easy
fixable within the mlt source code.
@Dan:
Would you merge his patch?
--- a/src/modules/plusgpl/consumer_cbrts.c
+++ b/src/modules/plusgpl/consumer_cbrts.c
@@ -37,7 +37,7 @@
#endif
#include
// includes for socket IO
-#if (_POSIX_C_SOURCE >= 1 || _XOPEN_SOURCE || _POSIX_SOURCE) &&
(_POSIX_TIMERS > 0)
+#if (_POSIX_C_SOURCE >= 1 || _XOPEN_SOURCE || _POSIX_SOURCE) &&
(_POSIX_TIMERS > 0) && !defined(__FreeBSD_kernel__)
#define CBRTS_BSD_SOCKETS 1
#include
#include
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
signature.asc
Description: OpenPGP digital signature
Bug#815800: Activate support for WLAN USB N53 device
Package: src:linux Version: 4.4.2-3 Hello, in jessie and sid the ASUS USB-N53 B1 (aka N600) adapter is not working => no wlan device is detected. On [0] I have found, that "rt2800usb - Include support for unknown (USB) devices (RT2800USB_UNKNOWN)" has to be activated, but the Debian configuration says: # CONFIG_RT2800USB_UNKNOWN is not set [0]: https://wikidevi.com/wiki/ASUS_USB-N53 -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#810789: RM: sshm -- ROM; not developed anymore
Package: ftp.debian.org Severity: normal Please remove the package completly from our archive. It is not developed anymore, thanks
Bug#807424: kdenlive: Buttons missing
Am 08.12.2015 um 18:13 schrieb Massimo Barbieri: Package: kdenlive Version: 15.08.3-1 Severity: normal Dear Maintainer, I'm using Kdenlive with Debian Stretch 64bit with Gnome 3 and buttons of the gui of kdenlive are missing (ex. Open and save buttons under the menu). Please notice that kde-runtime and kde-runtime-data are installed. Hi, could you please check if they appear if you install oxygen-icon-theme or plasma-theme-oxygen? - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#818480: libmlt memory corruption crashes openshot
Am 17.03.2016 um 14:59 schrieb Chris Bainbridge: Package: libmlt6 Version: 0.9.2-2 Severity: important Trying to use openshot to put together a simple sequence of videos but it crashes or hangs after a few minutes. It seems to be when changes are made and the timeline cursor is reposioned. This pretty much makes openshot unusable. Valgrind shows repeated memory corruption during this period resulting from free in mlt_frame_close: ==25301== Invalid write of size 4 ==25301==at 0x241E76F2: av_frame_unref (in /usr/lib/x86_64-linux-gnu/libavutil.so.54.3.0) ==25301==by 0x23341907: avcodec_decode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0) ==25301==by 0x28F6624D: producer_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1C3E7DD4: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltxine.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EC105: get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EADAD: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135F03F0: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301== Address 0x2a585ea0 is 576 bytes inside a block of size 584 free'd ==25301==at 0x4C29E90: free (vg_replace_malloc.c:473) ==25301==by 0x28F61CD3: producer_avformat_close (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x10177B4D: cache_object_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x10177BF7: mlt_cache_item_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1796A41E: video_thread (in /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so) ==25301==by 0x4E3D0A3: start_thread (pthread_create.c:309) ==25301== ==25301== Invalid write of size 8 ==25301==at 0x241E76C6: av_frame_unref (in /usr/lib/x86_64-linux-gnu/libavutil.so.54.3.0) ==25301==by 0x23341907: avcodec_decode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0) ==25301==by 0x28F6624D: producer_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1C3E7DD4: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltxine.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EC105: get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EADAD: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135F03F0: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301== Address 0x2a585cc0 is 96 bytes inside a block of size 584 free'd ==25301==at 0x4C29E90: free (vg_replace_malloc.c:473) ==25301==by 0x28F61CD3: producer_avformat_close (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x10177B4D: cache_object_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x10177BF7: mlt_cache_item_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x179
Bug#818670: RM: fotowall -- ROM; Not active developed anymore
Package: ftp.debian.org Severity: normal Hello, I - as the maintainer of the package - request the removal of fotowall from the archive, because it is not developed anymore since years and will not work with the up to date Qt versions.
Bug#818446: roarplaylistd: FTBFS: error: 'SLP_OK' undeclared
config.h says, it has got LIB_SLP, which is not true and a fault. But I can fix it for Debian with the --no-slp switch. Am 18.03.2016 um 11:36 schrieb Philipp Schafft: Good morning, can you please provide the config.h from your build? (it's created by configure). I don't see why exactly this fails as it builds without OpenSLP fine for me. Thank you for your additional information.
Bug#818804: RM: webissues-server -- ROM; not compatible and maintained
Package: ftp.debian.org Severity: normal Hello, as the old maintainer of webissues-server I request the removal of this package from the archive, because of the following reasons: a) no new maintainer has been found after years b) low popcon c) not compatible with the up to date webissues client d) (not tested) but I do not believe the currrent version in Debian works with our up to date PHP versions
Bug#818961: heartbeat: v1 config style not compatible with systemd
Package: heartbeat Version: 1:3.0.5+hg12629-1.2 Severity: grave Tags: upstream Justification: causes non-serious data loss Hello, as previous reported on IRC the v1 config style does not work with systemd as init system. Failovers are broken, because of the event based systemd, instead of LSB ordering for services. I also tried out the 1:3.0.6-2 version, without any luck. Upstream also states (have not got the link now) that it is unsupported, since v1 style does not get new features. IMO the package should warn (debconf dialog prio high?) the user if he upgrades heartbeat and systemd+v1 config is in use. Why severity grave? On setting up some test VMs I noticed that it looks like the cluster is working, but on intensive testing (just some failovers or using /usr/share/heartbeat/ scripts) everything broke again and again. For productive setups this will fail in a bigger downtime and the user could not identify the real problem (missing support) from the logs, except of some coredumps and never taking over clients. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#819162: pacemaker: Missing dependency on dbus
Package: pacemaker Version: 1.1.14-2 Severity: serious Hello, pacemaker is missing a dependency on "dbus", without it installation and start will fail: resource-agents (1:3.9.7-1~bpo8+1) wird eingerichtet ... pacemaker-resource-agents (1.1.14-2~bpo8+1) wird eingerichtet ... pacemaker (1.1.14-2~bpo8+1) wird eingerichtet ... Failed to start pacemaker.service: Unit dbus.service failed to load: No such file or directory. invoke-rc.d: initscript pacemaker, action "start" failed. dpkg: Fehler beim Bearbeiten des Paketes pacemaker (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations
Am 15.02.2016 um 14:14 schrieb Dmitry Smirnov: I am aware of those issues, that is also why the embedded-code-copies bug is marked as "need help". And this is why I provided some hints how you can address those problems in my bug report. This is why I wrote to you after when I stabilised "ckeditor" so you could use it. I can use it, until ckeditor OR otrs upstreams broke it again, like with jquery. Also it would prevent backports of otrs to jessie. and mostly it is not possible to replace the libjs thirdparty foo with the packages from Debian, mostly because of version missmatches. Hold on, you are answering the least important concern. There are cases when replacing bundled library with system one could be fragile or not suitable. But you can't ship and use untrusted pre-minified upstream files with who- knows-what... You reported a very general bug about the whole javascript mess. Replacing ckeditor will not solve the other problems or all those minified files and so on. Nobody is willed (or in my case able) to fix those JS issues, which appear here and then with different versions in different places (ugly JS sh..). At least I gave you "ckeditor" didn't I? That's one less problem to deal with... See above. If everything is simple for you and just replacements have to be done (which is not the case) then I would be happy to welcome you on the otrs-packaging board. It is simple enough. Although some system libraries should be safe to use you do not have to use only system libraries. But you have to get rid of non-DFSG precompiled binaries. I appreciate your invitation but unfortunately I have no time for otrs. IMO minified files are not as evil as the embedded libs, which should be addressed first. Just a short example: With 5.0.1-2 I had to drop (and inform the security team) about removing again the use of the libjs-jquery* packages from Debian, because of #802938 I agree that using "libjs-jquery-ui" package of different version than bundled one is fragile. Though with "libjs-jquery" you'd probably be safe as long as you do not cross 1.9.0 boundary. However you must not use pre-minified "jquery-ui.js" as it is shipped in orig.tar. As very minimum you have to replace it with original uncompressed version that you have to ship in "debian/missing-sources" and ideally report pre-built binaries as bug to upstream. If you believe in minification then you can minify on build time. You can not trust source- less, unreadable, unmodifiable pre-built binaries. I suppose lintian already warned you long before I did. I wrote the following wiki page that I use when I make upstream bug reports about minified binaries -- I hope you might find it useful: https://wiki.debian.org/onlyjob/no-minification Investing work in removing those files will not realy help and just burden the whole packaging and eat time to fix realy serious issues - like embedded libs. @Debian release team: I would like to request a strech ignore for this bug. I am aware of these problems, but I am not able to fix them nor did anyone ever offered me help with this JS foo. If it would not be possible I had to resign otrs packaging in Debian. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#816340: lack of rtaudio blocks Movit support in Kdenlive
Am 01.03.2016 um 01:04 schrieb Steinar H. Gunderson: Source: mlt Version: 6.0.0-2 Severity: normal Hi, rtaudio was removed from the Debian MLT package in #668893 (in 2012) due to concerns over the embedded copy. However, it seems Kdenlive now requires rtaudio support in MLT before it's willing to enable GPU filters via Movit. (I don't know exactly why; the comments indicate Movit and SDL audio together crashes, but when I developed this support back in the day, I saw no such issues.) Could you please consider reenabling it? The bug seems to indicate that work on building against a non-bundled rtaudio was in progress at the time. Hey, as long as mlt just uses the librtaudio and libebur from the embedded code copies I am not able to enable those features (also Ubuntu and other distros). -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations
Am 03.03.2016 um 14:31 schrieb Julien Cristau: On Wed, Mar 2, 2016 at 12:36:46 +0100, Patrick Matthäi wrote: @Debian release team: I would like to request a strech ignore for this bug. I am aware of these problems, but I am not able to fix them nor did anyone ever offered me help with this JS foo. If it would not be possible I had to resign otrs packaging in Debian. There's two issues as I understand it: - embedded copies of third-party code - lack of source for some of them The former is not necessarily RC, and I'm not thrilled about ignoring the latter. Not to mention we're months away from freeze, so this isn't the time to consider stretch-ignore tags, there's plenty of time to fix bugs still. Thanks for your answer. I will try to fix the serious bugs in the next time. Just get a new notebook after my workstation crashed...
Bug#803408: kdenlive clip playback stuck and switch to project monitor produces a crash
Am 29.10.2015 um 20:22 schrieb Mikko Rapeli: Package: kdenlive Version: 15.08.2+git20151026-1 Severity: normal Hi, I'm slowly trying to edit my project with a few clips. If I leave kdenlive idling with the project open for a while, it somehow gets stuck to a few frames of a single clip in clip preview. When I try to switch and preview other clips, their audio track is played but video is stuck on that previous clip. If I then switch to project monitor, kdenlive crashes: Hello, could you please retest this issue with kdenlive 15.12.0-1 and give me some feedback? Please also attach a new gdb bt, if it is still crashing. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#800623: kdenlive: egmentation fault on use of "corners" effect
Am 05.10.2015 um 16:07 schrieb Patrick Matthäi: Am 05.10.2015 um 15:58 schrieb Asumu Takikawa: On 2015-10-05 11:38:16 +0200, Patrick Matthäi wrote: Thanks for your investigation. Does this also resolves your bug #800623 => "Segmentation fault on use of "corners" effect" ? No, that appears to be a different issue that I haven't been able to pinpoint yet. Cheers, Asumu Thanks. Could you please install the libqt -dbg packages and kdenlive-dbg + libmlt-dbg and run it with gdb (using bt full)? Hi, and please retest it with kdenlive 15.12.0-1 and give me some feedback? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#809231: Fwd: Bug#809231: kdenlive: Wrong number at transcode profile
Am 28.12.2015 um 18:21 schrieb jb: > On Monday, December 28, 2015 06:05:24 PM you wrote: >> Hey, >> could you check this? :) > > Hi, > > Thanks for the report. > This is now fixed in git. Thanks for your quick fix! -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#734442: patch
Am 01.01.2016 um 04:09 schrieb Eric Dorland: To repeat myself: If you guys (packagers) all agree on how this file should look like, I'm fine with it too. If you want to maintain a separate unit file for Debian which is different from other distros, I'm not in a position to stop you from doing this. I don't have strong feelings about this, and I'm not the maintainer. I would just like this to work out of the box on Debian :) Patrick what do you think? For the Debian packaging itself it looks good for me (except of the username e.g.). Maybe we should use something like "znc-system" or "znc-daemon", since most znc users just have called their znc user "znc" and "_znc" is invalid. I would be happy to have got a solution with upstream and other distributions, so that there are no bigger differences (or bugs) between different distributions and upstream. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#766957: Patch / update for znc to disable weak ciphers and SSLv2/SSLv3 protocols
Am 22.11.2014 um 17:47 schrieb Thijs Kinkhorst: > Hi, > >> sid/jessie will be fixed, soon. But I can not take the responsibility >> for backporting this patch to znc=0.206. > > I've not seen movement in sid yet on this issue. Is it still on your > radar? Anything I can help with? > > > Cheers, > Thijs > Whops. I already pinged Uli about the debian security list but did not get an answer, yet. @Uli: *ping ping*? :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#773700: unblock: otrs2/3.3.9-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package otrs2. -security also ACKed this upload.
diff -Naur '--exclude=.svn' 3.3.9-2/debian/changelog 3.3.9-3/debian/changelog
--- 3.3.9-2/debian/changelog2014-10-29 09:32:47.224286362 +0100
+++ 3.3.9-3/debian/changelog2014-12-18 19:57:30.862192259 +0100
@@ -1,3 +1,13 @@
+otrs2 (3.3.9-3) unstable; urgency=medium
+
+ * Add patch 16-CVE-2014-9324.diff which fixes CVE-2014-9324, also known as
+OSA-2014-06:
+An attacker with valid OTRS credentials could access and manipulate ticket
+data of other users via the GenericInterface, if a ticket webservice is
+configured and not additionally secured.
+
+ -- Patrick Matthäi Thu, 18 Dec 2014 19:02:56 +0100
+
otrs2 (3.3.9-2) unstable; urgency=low
* Drop libjs-jquery dependency and use the emebedded version again to avoid
diff -Naur '--exclude=.svn' 3.3.9-2/debian/patches/16-CVE-2014-9324.diff
3.3.9-3/debian/patches/16-CVE-2014-9324.diff
--- 3.3.9-2/debian/patches/16-CVE-2014-9324.diff1970-01-01
01:00:00.0 +0100
+++ 3.3.9-3/debian/patches/16-CVE-2014-9324.diff2014-12-18
19:57:30.874192201 +0100
@@ -0,0 +1,1528 @@
+# Upstream patch to fix CVE-2014-9324, also known as OSA-2014-06:
+# An attacker with valid OTRS credentials could access and manipulate ticket
+# data of other users via the GenericInterface, if a ticket webservice is
+# configured and not additionally secured.
+# URL:
+# https://www.otrs.com/security-advisory-2014-06-incomplete-access-control/
+
+diff -Naur otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/Common.pm
otrs2-3.3.9/Kernel/GenericInterface/Operation/Ticket/Common.pm
+--- otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/Common.pm
2014-09-03 15:15:41.0 +0200
otrs2-3.3.9/Kernel/GenericInterface/Operation/Ticket/Common.pm
2014-12-18 18:54:26.386869907 +0100
+@@ -1369,6 +1369,17 @@
+
+ =item CheckCreatePermissions ()
+
++Tests if the user have the permissions to create a ticket on a determined
queue
++
++my $Result = $CommonObject->CheckCreatePermissions(
++Ticket => $TicketHashReference,
++UserID => 123, # or 'CustomerLogin'
++UserType => 'Agent', # or 'Customer'
++);
++
++returns:
++$Success = 1# if everything is OK
++
+ =cut
+
+ sub CheckCreatePermissions {
+@@ -1413,6 +1424,45 @@
+ return 1;
+ }
+
++=item CheckAccessPermissions()
++
++Tests if the user have access permissions over a ticket
++
++my $Result = $CommonObject->CheckAccessPermissions(
++TicketID => 123,
++UserID => 123, # or 'CustomerLogin'
++UserType => 'Agent', # or 'Customer'
++);
++
++returns:
++$Success = 1# if everything is OK
++
++=cut
++
++sub CheckAccessPermissions {
++my ( $Self, %Param ) = @_;
++
++# check needed stuff
++for my $Needed (qw(TicketID UserID UserType)) {
++if ( !$Param{$Needed} ) {
++return;
++}
++}
++
++my $TicketPermissionFunction = 'TicketPermission';
++if ( $Param{UserType} eq 'Customer' ) {
++$TicketPermissionFunction = 'TicketCustomerPermission';
++}
++
++my $Access = $Self->{TicketObject}->$TicketPermissionFunction(
++Type => 'ro',
++TicketID => $Param{TicketID},
++UserID => $Param{UserID},
++);
++
++return $Access;
++}
++
+ =begin Internal:
+
+ =item _ValidateUser()
+diff -Naur
otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/TicketCreate.pm
otrs2-3.3.9/Kernel/GenericInterface/Operation/Ticket/TicketCreate.pm
+--- otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/TicketCreate.pm
2014-09-03 15:15:41.0 +0200
otrs2-3.3.9/Kernel/GenericInterface/Operation/Ticket/TicketCreate.pm
2014-12-18 18:54:26.390869876 +0100
+@@ -238,6 +238,7 @@
+ );
+ }
+
++my $PermissionUserID = $UserID;
+ if ( $UserType eq 'Customer' ) {
+ $UserID = $Self->{ConfigObject}->Get('CustomerPanelUserID')
+ }
+@@ -304,7 +305,7 @@
+ # check create permissions
+ my $Permission = $Self->{TicketCommonObject}->CheckCreatePermissions(
+ Ticket => $Ticket,
+-UserID => $UserID,
++UserID => $PermissionUserID,
+ UserType => $UserType,
+ );
+
+diff -Naur
otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/TicketGet.pm
otrs2-3.3.9/Kernel/GenericInterface/Operation/Ticket/TicketGet.pm
+--- otrs2-3.3.9.orig/Kernel/GenericInterface/Operation/Ticket/TicketGet.pm
2014-09-03 15:15:41.0 +0200
otr
Bug#863443: unblock: needrestart/2.11-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package needrestart It fixes a RC bug by blacklisting for oneshot services, while it is closing one important and one serious bug. It also adds a patch (already in jessie-bpo) to fix a Perl warning, which only affects Perl 5.20.x, it makes backports easier. diff -Naur '--exclude=.svn' 2.11-2/debian/changelog 2.11-3/debian/changelog --- 2.11-2/debian/changelog 2017-01-24 10:56:05.028489330 +0100 +++ 2.11-3/debian/changelog 2017-05-26 15:59:51.615213743 +0200 @@ -1,3 +1,23 @@ +needrestart (2.11-3) unstable; urgency=high + + * Add patch 03-perl-warning to fix a warning from Perl triggered in version +5.20. + * Merge 2.11-2~bpo8+1 changelog. + * Add patch 04-ignore-systemd-services to ignore apt-daily.service, +apt-daily-upgrade.service, unattended-upgrades.service and +rc-local.service. +Closes: #862840, #852864 + + -- Patrick Matthäi Fri, 26 May 2017 15:45:04 +0200 + +needrestart (2.11-2~bpo8+1) jessie-backports; urgency=medium + + * Rebuild for jessie-backports. + * Add patch 03-perl-warning to fix a warning from Perl triggered in version +5.20. + + -- Patrick Matthäi Mon, 06 Feb 2017 10:42:32 +0100 + needrestart (2.11-2) unstable; urgency=high * Add patch 02-install-restart-d to fix installation of restart.d/ script diff -Naur '--exclude=.svn' 2.11-2/debian/patches/03-perl-warning.diff 2.11-3/debian/patches/03-perl-warning.diff --- 2.11-2/debian/patches/03-perl-warning.diff 1970-01-01 01:00:00.0 +0100 +++ 2.11-3/debian/patches/03-perl-warning.diff 2017-05-26 15:59:51.615213743 +0200 @@ -0,0 +1,14 @@ +# Fix warning in Perl 5.20.x. Not triggered in 5.24.x. + +diff -Naur needrestart-2.11.orig/ex/needrestart.conf needrestart-2.11/ex/needrestart.conf +--- needrestart-2.11.orig/ex/needrestart.conf 2017-01-17 16:00:20.0 +0100 needrestart-2.11/ex/needrestart.conf 2017-02-06 10:40:29.008100902 +0100 +@@ -150,7 +150,7 @@ + qr(^/\[aio\]), + + # Oil Runtime Compiler's JIT files +-qr(/orcexec\.[\w\d]+( \(deleted\))?$), ++qr#/orcexec\.[\w\d]+( \(deleted\))?$#, + ]; + + # Verify mapped files in fileystem: diff -Naur '--exclude=.svn' 2.11-2/debian/patches/04-ignore-systemd-services.diff 2.11-3/debian/patches/04-ignore-systemd-services.diff --- 2.11-2/debian/patches/04-ignore-systemd-services.diff 1970-01-01 01:00:00.0 +0100 +++ 2.11-3/debian/patches/04-ignore-systemd-services.diff 2017-05-26 15:59:51.607213783 +0200 @@ -0,0 +1,24 @@ +# Ignore / Blacklist apt-daily.service, apt-daily-upgrade.service, +# unattended-upgrades.service and rc-local.service. +# Closes: #852864 +# Closes: #862840 + +diff -Naur needrestart-2.11.orig/ex/needrestart.conf needrestart-2.11/ex/needrestart.conf +--- needrestart-2.11.orig/ex/needrestart.conf 2017-05-26 15:46:38.987005457 +0200 needrestart-2.11/ex/needrestart.conf 2017-05-26 15:49:06.062305440 +0200 +@@ -121,6 +121,15 @@ + qr(^emergency\.service$) => 0, + qr(^rescue\.service$) => 0, + ++ # Do not restart oneshot service apt-daily, unattended-upgrades.service ++ # and apt-daily-upgrade.service,see #862840 ++ qr(^apt-daily\.service$) => 0, ++ qr(^apt-daily-upgrade\.service$) => 0, ++ qr(^unattended-upgrades\.service$) => 0, ++ ++ # Ignore rc-local.service, see #852864 ++ qr(^rc-local\.service$) => 0, ++ + # don't restart systemd-logind, see #798097 + qr(^systemd-logind) => 0, + }; diff -Naur '--exclude=.svn' 2.11-2/debian/patches/series 2.11-3/debian/patches/series --- 2.11-2/debian/patches/series2017-01-24 10:56:05.020489378 +0100 +++ 2.11-3/debian/patches/series2017-05-26 15:59:51.607213783 +0200 @@ -1,2 +1,4 @@ 01-use-invoke-rc-d.diff 02-install-restart-d.diff +03-perl-warning.diff +04-ignore-systemd-services.diff unblock needrestart/2.11-3 -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#863444: unblock: apt-dater/1.0.3-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package apt-dater
This update adds one upstream patch to fix the broken Tcl filters in the UI.
They are failing because of incorrect return values.
diff -Naur '--exclude=.svn' 1.0.3-3/debian/changelog 1.0.3-4/debian/changelog
--- 1.0.3-3/debian/changelog2016-11-22 11:33:34.715749952 +0100
+++ 1.0.3-4/debian/changelog2017-05-26 16:00:16.415094385 +0200
@@ -1,3 +1,9 @@
+apt-dater (1.0.3-4) unstable; urgency=medium
+
+ * Add upstream patch 03-broken-tcl-filters to fix broken Tcl filters.
+
+ -- Patrick Matthäi Fri, 26 May 2017 15:54:42 +0200
+
apt-dater (1.0.3-3) unstable; urgency=medium
* Replace patch 01-grep-syntax-error with 02-fix-default-err-pattern from
diff -Naur '--exclude=.svn' 1.0.3-3/debian/patches/03-broken-tcl-filters.diff
1.0.3-4/debian/patches/03-broken-tcl-filters.diff
--- 1.0.3-3/debian/patches/03-broken-tcl-filters.diff 1970-01-01
01:00:00.0 +0100
+++ 1.0.3-4/debian/patches/03-broken-tcl-filters.diff 2017-05-26
16:00:16.411094403 +0200
@@ -0,0 +1,21 @@
+# Upstream fix for Tcl filters never matching due to broken return code
+# handling.
+# URL:
https://github.com/DE-IBH/apt-dater/commit/c6c41e8fe32b6c80ed6629f0b88e3a429a85a779
+
+diff --git a/src/ui.c b/src/ui.c
+index edf92e2..037340c 100644
+--- a/src/ui.c
b/src/ui.c
+@@ -2813,10 +2813,10 @@ void applyFilter(GList *hosts) {
+ case TCL_OK:
+ case TCL_RETURN:
+ filtered = atoi(Tcl_GetStringResult(tcl_interp)) > 0;
+- ;;
++ break;
+ default:
+ filtered = FALSE;
+- ;;
++ break;
+ }
+
+ if(filtered != n->filtered) {
diff -Naur '--exclude=.svn' 1.0.3-3/debian/patches/series
1.0.3-4/debian/patches/series
--- 1.0.3-3/debian/patches/series 2016-11-22 11:33:34.715749952 +0100
+++ 1.0.3-4/debian/patches/series 2017-05-26 16:00:16.411094403 +0200
@@ -1 +1,2 @@
02-fix-default-err-pattern.diff
+03-broken-tcl-filters.diff
unblock apt-dater/1.0.3-4
-- System Information:
Debian Release: 8.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#863889: libroad-dev bogus provides libsndio-dev.
Am 01.06.2017 um 17:56 schrieb peter green: > Package: libroar-dev > Version: 1.0~beta11-9 > Severity: important > > libroar-dev "provides" libsndio-dev. > > This made sense in jessie since libroar-dev contained > /usr/include/sndio.h and /usr/lib/arm-linux-gnueabihf/libsndio.so but > the stretch version of the package no longer contains those files. So > IMO this provides is bogus. > > I ran into this while trying to build vlc. If libroar-dev is installed > but libsndio-dev is not then the build-depends are satisfied thanks to > the provides but vlc fails to build because it can't find sndio. Hi, you are right, thanks for your hint. It will be removed with the next upload. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#864319: CVE-2017-9324
Am 06.06.2017 um 22:37 schrieb Moritz Muehlenhoff: > Package: otrs > Severity: grave > Tags: security > > Hi, > details are sparse on this one, could you get in touch with upstream to > isolate this to the change in question? > https://www.otrs.com/security-advisory-2017-03-security-update-otrs-versions/ > > Cheers, > Moritz I will try. On which way should I fix Stretch? stretch-security updates or direct upload to Stretch? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
found #864642 4.9.30-2+deb9u1 thanks Am 12.06.2017 um 10:02 schrieb Patrick Matthäi: > Package: src:linux > Version: 4.9.30-1 > Severity: important > File: linux > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where > appropriate *** > > Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to > linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the > "primary" interface this: > > TCP: ens192: Driver has suspect GRO implementation, TCP performance may > be compromised. > > I can't see any performance impact. This happens on all our vSphere 6.0 > and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML > 350 G9 and so on). > > Why is this bug important? Because on one VM this also produces a kernel > panic after some time (minutes or hours). I just could get the panic > attached as screenshot. The only "big" difference between the crashing > host and the others may be, that it is also running PM2, NPM, NodeJS and > a NFS kernel server. > > If I boot the VM with 4.9.30-1 and deactivate gro and lro with: > ethtool -K ens192 gro off > ethtool -K ens192 lro off > .. it does not crash. > > Booting 4.9.18-1 and everything is completly fine ;) > The VM keeps on crashing after a few hours -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#873878: [gluster-packaging] Fwd: Bug#873878: glusterfs-client: mount.glusterfs needs bash as /bin/sh
Am 01.09.2017 um 11:40 schrieb Niels de Vos:
> On Fri, Sep 01, 2017 at 09:36:16AM +0200, Patrick Matthäi wrote:
>> Hi,
>>
>> how should it be fixed for glusterfs now? Better shell code without
>> bashishm or do you want /bin/bash as shebang?
> Do you have a preference? I do not know how much work is it is to
> rewrite the mount.glusterfs script to remove all the Bashisms. At least
> in the Debian builds you may want to patch it to /bin/bash for the time
> being.
I would prefer a patch, so that it works without bash. Luckily the bug
reporter just wrote a patch :)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873878#10
If you would merge it, I also would add it to the repository. I have
attached two other patches for 3.12.x, too.
>
> Opinions welcome :) Thanks,
> Niels
>
>>
>>
>> Weitergeleitete Nachricht
>> Betreff: Bug#873878: glusterfs-client: mount.glusterfs needs bash as
>> /bin/sh
>> Weitersenden-Datum: Thu, 31 Aug 2017 20:21:01 +
>> Weitersenden-Von:Michael Lundkvist
>> Weitersenden-An: debian-bugs-dist@lists.debian.org
>> Weitersenden-CC: Patrick Matthäi
>> Datum: Thu, 31 Aug 2017 21:46:18 +0200
>> Von: Michael Lundkvist
>> Antwort an: Michael Lundkvist ,
>> 873...@bugs.debian.org
>> An: Debian Bug Tracking System
>>
>>
>>
>> Package: glusterfs-client
>> Version: 3.12.0-1
>> Severity: serious
>> Tags: upstream
>> Justification: Policy 10.4
>>
>> Version 3.12 of Glusterfs adds code in /sbin/mount.glusterfs that depends on
>> bash.
>>
>> With dash as /bin/sh, I get the following error message when trying to mount
>> a glusterfs volume:
>>> /sbin/mount.glusterfs: 667: /sbin/mount.glusterfs: Bad substitution
>> Line 667 is:
>> 667 [ ${volume_str:0:1} = '/' ] && {
>>
>> Modifying mount.glusterfs to use /bin/bash makes it possible to mount again.
>>
>> /Micke
>>
>>
>> -- System Information:
>> Debian Release: buster/sid
>> APT prefers unstable
>> APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>> LANGUAGE=en_US:en (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages glusterfs-client depends on:
>> ii fuse 2.9.7-1
>> ii glusterfs-common 3.12.0-1
>> ii libc6 2.24-17
>> ii libssl1.1 1.1.0f-5
>> ii python2.7.13-2
>>
>> glusterfs-client recommends no packages.
>>
>> glusterfs-client suggests no packages.
>>
>> -- no debconf information
>>
>> ___
>> packaging mailing list
>> packag...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/packaging
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
# Fix syntax error in shell script.
diff -Naur
glusterfs-3.11.1.orig/extras/hook-scripts/create/post/S10selinux-label-brick.sh
glusterfs-3.11.1/extras/hook-scripts/create/post/S10selinux-label-brick.sh
---
glusterfs-3.11.1.orig/extras/hook-scripts/create/post/S10selinux-label-brick.sh
2017-06-27 17:25:12.237136825 +0200
+++ glusterfs-3.11.1/extras/hook-scripts/create/post/S10selinux-label-brick.sh
2017-07-03 16:21:05.113301642 +0200
@@ -43,7 +43,7 @@
do
# Add a file context for each brick path and associate with the
# glusterd_brick_t SELinux type.
-semanage fcontext --add -t glusterd_brick_t -r s0 $b(/.*)?
+semanage fcontext --add -t glusterd_brick_t -r s0 $b
# Set the labels on the new brick path.
restorecon -R $b
# Fix new spelling errors.
diff -Naur glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-geo-rep.c
glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-geo-rep.c
--- glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-geo-rep.c
2017-08-30 14:46:33.875359178 +0200
+++ glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-geo-rep.c
2017-08-31 10:43:14.228479030 +0200
@@ -3615,7 +3615,7 @@
"geo-replication start failed",
strerror (errno));
snprintf (errmsg, sizeof(errmsg),
- "fuse unvailable");
+
Bug#849752: lintian: dpkg-source failed with status 2 / no such file or directory
Am 19.04.2017 um 23:21 schrieb Niels Thykier: > Drew Parsons: >> On Fri, 30 Dec 2016 15:52:02 +0100 Patrick Matthäi wrote: >>> >>> with both versions of lintian on jessie/jessie-backports (I think >> since a stable update of >>> jessie itself) I get an error on checking most of my packages: >>> >>> # export LINTIAN_DEBUG=1; lintian -IE --pedantic >> /var/cache/pbuilder/result/ckport*.changes >>> warning: the authors of lintian do not recommend running it with root >> privileges! >>> N: Using dpkg-source to unpack ckport >>> cp: cannot stat '/tmp/temp-lintian-lab- >> ...: No such file or directory >> >> >> I'm now hitting this lintian bug. Not on all packages, but on the >> changes file (binary changes, not source) generated by pdebuild for >> instant 2016.2.0-2. >> >> Drew >> > Hi, > > Patrick, can you also "only" reproduce this on pdebuild produced binary > .changes files? > > Thanks, > ~Niels > Hi, sorry didn't tested, yet. But I can also reproduce it with Stretch and building packages with pbuilder and then checking them with lintian (also lintian v 2.5.51): $ lintian -IE --pedantic /var/cache/pbuilder/result/*.changes cp: cannot stat '/tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bing/bing_1.3.5-2_source/bing_1.3.5.orig.tar.gz': No such file or directory dpkg-source: error: cp /tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bing/bing_1.3.5-2_source/bing_1.3.5.orig.tar.gz to /tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bing/bing_1.3.5-2_source/bing_1.3.5.orig.tar.gz gave error exit status 1 internal error: dpkg-source -x failed with status 2 at /usr/share/lintian/collection/unpacked line 72. warning: collect info unpacked about package bing failed warning: skipping check of source package bing cp: cannot stat '/tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bmon/bmon_1_4.0-4_source/bmon_4.0.orig.tar.xz': No such file or directory dpkg-source: error: cp /tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bmon/bmon_1_4.0-4_source/bmon_4.0.orig.tar.xz to /tmp/temp-lintian-lab-NYxGw3LEkK/pool/b/bmon/bmon_1_4.0-4_source/bmon_4.0.orig.tar.xz gave error exit status 1 internal error: dpkg-source -x failed with status 2 at /usr/share/lintian/collection/unpacked line 72. warning: collect info unpacked about package bmon failed warning: skipping check of source package bmon I: bmon: desktop-entry-lacks-icon-entry usr/share/applications/bmon.desktop cp: cannot stat '/tmp/temp-lintian-lab-NYxGw3LEkK/pool/g/geoip/geoip_1.6.11-2_source/geoip_1.6.11.orig.tar.gz': No such file or directory dpkg-source: error: cp /tmp/temp-lintian-lab-NYxGw3LEkK/pool/g/geoip/geoip_1.6.11-2_source/geoip_1.6.11.orig.tar.gz to /tmp/temp-lintian-lab-NYxGw3LEkK/pool/g/geoip/geoip_1.6.11-2_source/geoip_1.6.11.orig.tar.gz gave error exit status 1 internal error: dpkg-source -x failed with status 2 at /usr/share/lintian/collection/unpacked line 72. warning: collect info unpacked about package geoip failed warning: skipping check of source package geoip cp: cannot stat '/tmp/temp-lintian-lab-NYxGw3LEkK/pool/m/mlt/mlt_6.4.1-5_source/mlt_6.4.1.orig.tar.gz': No such file or directory dpkg-source: error: cp /tmp/temp-lintian-lab-NYxGw3LEkK/pool/m/mlt/mlt_6.4.1-5_source/mlt_6.4.1.orig.tar.gz to /tmp/temp-lintian-lab-NYxGw3LEkK/pool/m/mlt/mlt_6.4.1-5_source/mlt_6.4.1.orig.tar.gz gave error exit status 1 internal error: dpkg-source -x failed with status 2 at /usr/share/lintian/collection/unpacked line 72. warning: collect info unpacked about package mlt failed warning: skipping check of source package mlt -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#866993: glusterfs-common: broken symlink: /usr/share/glusterfs/scripts/gsync-sync-gfid -> ../../../lib/glusterfs/gsync-sync-gfid
tag #866993 + pending severity #866993 normal thanks A broken symlink is not severity serious Am 03.07.2017 um 11:58 schrieb Andreas Beckmann: > Package: glusterfs-common > Version: 3.11.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. > > >From the attached log (scroll to the bottom...): > > 0m27.9s ERROR: FAIL: Broken symlinks: > /usr/share/glusterfs/scripts/gsync-sync-gfid -> > ../../../lib/glusterfs/gsync-sync-gfid > > > The target seems to have disappeared recently. > > > cheers, > > Andreas -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#875224: [videocut] Future Qt4 removal from Buster
Hi, Am 09.09.2017 um 23:12 schrieb Lisandro Damián Nicanor Pérez Meyer: > Source: videocut > Version: 0.2.0-17 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: > > [announced] > <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> > > Currently Qt4 has been dead upstream and we are starting to have problems > maintaining it, like for example in the [OpenSSL 1.1 support] case. > > [OpenSSL 1.1 support] > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> > > In order to make this move, all packages directly or indirectly depending on > the Qt4 libraries have to either get ported to Qt5 or eventually get > removed from the Debian repositories. > > Therefore, please take the time and: > - contact your upstream (if existing) and ask about the state of a Qt5 > port of your application > - if there are no activities regarding porting, investigate whether there are > suitable alternatives for your users > - if there is a Qt5 port that is not yet packaged, consider packaging it > - if both the Qt4 and the Qt5 versions already coexist in the Debian > archives, consider removing the Qt4 version > > = Porting = > > Some of us where involved in various Qt4 to Qt5 migrations [migration] and we > know for sure that porting stuff from Qt4 to Qt5 is much much easier and less > painful than it was from Qt3 to Qt4. > > We also understand that there is still a lot of software still using Qt4. > > Don't forget to take a look at the C++ API changes page [apichanges] whenever > you start porting your application. > > [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html > [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html > > For any questions and issues, do not hesitate to contact the Debian Qt/KDE > team at debian-qt-...@lists.debian.org > > The removal is being tracked in <https://wiki.debian.org/Qt4Removal> > > Lisandro, > on behalf of the Qt4 maintainers Videocut upstream is dead. So I will remove it when Qt4 is removed -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#875224: [videocut] Future Qt4 removal from Buster
I Just requested a ROM for it Am 12.09.2017 um 16:43 schrieb Lisandro Damián Nicanor Pérez Meyer: > On 12 September 2017 at 11:16, Patrick Matthäi wrote: >> Hi, > [snip] >> Videocut upstream is dead. So I will remove it when Qt4 is removed > ACK, thanks for the followup! > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#875734: RM: videocut -- ROM; dead upstream / Qt4 removal
Package: ftp.debian.org Severity: normal Please remove this package. Upstream is "dead" since years and with the removal of Qt4 it will not build / work anymore, see #875224
Bug#876344: glusterfs-server: glustereventsd hardcodes working-directory
forwarded #876344 https://bugzilla.redhat.com/show_bug.cgi?id=1494526 thanks Am 21.09.2017 um 10:32 schrieb Guillem Jover: > Package: glusterfs-server > Version: 3.12.1-1 > Severity: important > > Hi! > > The glustereventd daemon hardcodes several paths (in eventsapiconf.py), > among them the glusterd working-directory to /var/lib/gulsterd. This > breaks badly when you have configured glusterd to use a different > working directory with something like: > > ,--- > volume management > type mgmt/glusterd > option working-directory /some/other/path > … > end-volume > `--- > > Thanks, > Guillem -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#876359: glusterfs: FTBFS when building twice in a row
forwarded #876359 https://bugzilla.redhat.com/show_bug.cgi?id=1494527 thanks Hi Am 21.09.2017 um 11:54 schrieb Guillem Jover: > There are at least .pyc files left around: > > libglusterfs/src/generator.pyc > > generated XDR symlinks: > > rpc/xdr/gen/*.x > > and unexpected modifications to shipped files: > >tests/basic/fuse/Makefile >tests/basic/gfapi/Makefile > > After all those are removed, the build still fails due to the missing > Makefile.in files that have been removed somewhere. Running: > > $ autoreconf -f -i > > makes things worse as then we get tons of modified Makefile.in file > changes. :( I've not looked further after this. It never built twice in a row. I already sent many emails and issues (cant find them now, filled a new) about this behaviour -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#867884: classic UI does not work because of missign javascript
Package: icinga2-classicui Severity: serious Version: 2.6.0-2 Hi, icinga2 classic UI required jquery and jquery-ui. However you are not using the embedded version and the icinga version in Debian is not compatible(?) with the delivered versions from stable. This results in many 404 (see screenshot) requests and a not working UI (missing actions, dropdowns and so on). I checked some files and most of them do not exist (anymore) in the stable repository. Most of them are embedded in other packages. For example: root@ims:~# LC_ALL=C dpkg -S jquery.ui.menu.js dpkg-query: no path found matching pattern *jquery.ui.menu.js* root@ims:~# apt-file search jquery.ui.menu.js ganglia-webfrontend: /usr/share/ganglia-webfrontend/contrib/jquery-ui-1.10.2/ui/jquery.ui.menu.js mediawiki: /usr/share/mediawiki/resources/lib/jquery.ui/jquery.ui.menu.js root@ims:~# -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
found #864642 4.9.30-2+deb9u2 thanks And it still crashes.. Am 22.06.2017 um 14:58 schrieb Patrick Matthäi: > found #864642 4.9.30-2+deb9u1 > thanks > > > Am 12.06.2017 um 10:02 schrieb Patrick Matthäi: >> Package: src:linux >> Version: 4.9.30-1 >> Severity: important >> File: linux >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to >> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the >> "primary" interface this: >> >> TCP: ens192: Driver has suspect GRO implementation, TCP performance may >> be compromised. >> >> I can't see any performance impact. This happens on all our vSphere 6.0 >> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML >> 350 G9 and so on). >> >> Why is this bug important? Because on one VM this also produces a kernel >> panic after some time (minutes or hours). I just could get the panic >> attached as screenshot. The only "big" difference between the crashing >> host and the others may be, that it is also running PM2, NPM, NodeJS and >> a NFS kernel server. >> >> If I boot the VM with 4.9.30-1 and deactivate gro and lro with: >> ethtool -K ens192 gro off >> ethtool -K ens192 lro off >> .. it does not crash. >> >> Booting 4.9.18-1 and everything is completly fine ;) >> > The VM keeps on crashing after a few hours > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect
Am 12.07.2017 um 12:10 schrieb Bernhard Schmidt:
> On Wed, Jul 12, 2017 at 09:35:53AM +0200, Patrick Matthäi wrote:
>
> Hi,
>
>> we have got the same issue with all our VPNs upgraded to Stretch now.
>> Most VPNs are connected about a 1 GBit/s datacenter connection with each
>> other (also same LAN), the other ones are connected about a 100 MBit/s
>> connection.
>
>> route remote_host 255.255.255.255 net_gateway
> This suggests that the VPN server is inside the netblocks routed through
> the tunnel, right?
If I understood you correct: yes - all VPNs are "clients"
>
> When the problem happens, can you check whether the static /32 route
> towards the VPN server still exists and points outside the tunnel.
We will check if it occurs again and give you the output of "ip {a,r,l}"
Anything else needed?
>
> Please also check a couple of minutes before the ping timeout whether you
> see anything network related. Are you using ifupdown or NetworkManager
> on the client?
>
> Bernhard
>
That is mostly hard to check, because that are many endpoints and
clients. One client is located in the hosteurope network, which had got
a maintainance this night (with a short outage), but also many other
customer VPNs (sophos, self hosted VPNs and so on) were affected from
different locations and links. So I dont think that this is the whole
thing triggering this bug.
I also uploaded the current testing version to stretch-bpo and deployed
it on one host, to see if there is a difference later
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201 thanks Am 11.07.2017 um 10:24 schrieb Patrick Matthäi: > found #864642 4.9.30-2+deb9u2 > thanks > > And it still crashes.. > > > Am 22.06.2017 um 14:58 schrieb Patrick Matthäi: >> found #864642 4.9.30-2+deb9u1 >> thanks >> >> >> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi: >>> Package: src:linux >>> Version: 4.9.30-1 >>> Severity: important >>> File: linux >>> >>> Dear Maintainer, >>> >>> *** Reporter, please consider answering these questions, where >>> appropriate *** >>> >>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to >>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the >>> "primary" interface this: >>> >>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may >>> be compromised. >>> >>> I can't see any performance impact. This happens on all our vSphere 6.0 >>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML >>> 350 G9 and so on). >>> >>> Why is this bug important? Because on one VM this also produces a kernel >>> panic after some time (minutes or hours). I just could get the panic >>> attached as screenshot. The only "big" difference between the crashing >>> host and the others may be, that it is also running PM2, NPM, NodeJS and >>> a NFS kernel server. >>> >>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with: >>> ethtool -K ens192 gro off >>> ethtool -K ens192 lro off >>> .. it does not crash. >>> >>> Booting 4.9.18-1 and everything is completly fine ;) >>> >> The VM keeps on crashing after a few hours >> -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect
Am 12.07.2017 um 16:17 schrieb Bernhard Schmidt: > Am 12.07.2017 um 15:41 schrieb Patrick Matthäi: > > Hi, > >>>> we have got the same issue with all our VPNs upgraded to Stretch now. >>>> Most VPNs are connected about a 1 GBit/s datacenter connection with each >>>> other (also same LAN), the other ones are connected about a 100 MBit/s >>>> connection. >>> >> I also uploaded the current testing version to stretch-bpo and deployed >> it on one host, to see if there is a difference later > Ah, I was already wondering who did. > > Today I updated our Sophos UTM, which is one OpenVPN server, where are here multiple vpn clients are connected with. While updating the UTM, there are 2 reboots of the devices, so the client needs a reconnect. The client with version openvpn_2.4.3-4~bpo9+1 still works, all 2.4.0-6+deb9u1 are dead. Also the VPN endpoint is not reachable on the dead nodes. Please note, that I replaced many IPs and hostnames with other stuff. Working one (tun0 affected, tun1 is another VPN): Jul 18 09:32:25 login ovpn-utm[8335]: [address.of.utm.de] Inactivity timeout (--ping-restart), restarting Jul 18 09:32:25 login ovpn-utm[8335]: SIGUSR1[soft,ping-restart] received, process restarting Jul 18 09:32:25 login ovpn-utm[8335]: Restart pause, 5 second(s) Jul 18 09:32:30 login ovpn-utm[8335]: TCP/UDP: Preserving recently used remote address: [AF_INET]EXT.IP.FROM.VPN:1197 Jul 18 09:32:30 login ovpn-utm[8335]: Socket Buffers: R=[212992->212992] S=[212992->212992] Jul 18 09:32:30 login ovpn-utm[8335]: UDP link local: (not bound) Jul 18 09:32:30 login ovpn-utm[8335]: UDP link remote: [AF_INET]EXT.IP.FROM.VPN:1197 Jul 18 09:32:30 login ovpn-utm[8335]: TLS: Initial packet from [AF_INET]EXT.IP.FROM.VPN:1197, sid=4030f3bf 8b41b71f Jul 18 09:32:31 login ovpn-utm[8335]: VERIFY OK: depth=1, C=de, L=Paderborn, O=company Internet GmbH, CN=company Internet GmbH VPN CA, emailAddress=tech...@company.de Jul 18 09:32:31 login ovpn-utm[8335]: VERIFY X509NAME OK: C=de, ST=Nordrhein-Westfalen, L=Paderborn, O=company Internet GmbH, OU=Technik, CN=address.of.utm.de, emailAddress=tech...@company.de Jul 18 09:32:31 login ovpn-utm[8335]: VERIFY OK: depth=0, C=de, ST=Nordrhein-Westfalen, L=Paderborn, O=company Internet GmbH, OU=Technik, CN=address.of.utm.de, emailAddress=tech...@company.de Jul 18 09:32:33 login ovpn-utm[8335]: Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA Jul 18 09:32:33 login ovpn-utm[8335]: [address.of.utm.de] Peer Connection Initiated with [AF_INET]EXT.IP.FROM.VPN:1197 Jul 18 09:32:34 login ovpn-utm[8335]: SENT CONTROL [address.of.utm.de]: 'PUSH_REQUEST' (status=1) Jul 18 09:32:35 login ovpn-utm[8335]: PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.200.13.1,route-gateway 10.200.13.1,topology subnet,ping 10,ping-restart 120,route INT.BEHIND.VPN2.0 255.255.255.0,route INT.BEHIND.VPN1.0 255.255.255.0,dhcp-option DNS INT.BEHIND.VPN1.210,dhcp-option DNS INT.BEHIND.VPN2.250,dhcp-option DOMAIN domäne.intern,ifconfig 10.200.13.4 255.255.255.0' Jul 18 09:32:35 login ovpn-utm[8335]: OPTIONS IMPORT: timers and/or timeouts modified Jul 18 09:32:35 login ovpn-utm[8335]: OPTIONS IMPORT: --ifconfig/up options modified Jul 18 09:32:35 login ovpn-utm[8335]: OPTIONS IMPORT: route options modified Jul 18 09:32:35 login ovpn-utm[8335]: OPTIONS IMPORT: route-related options modified Jul 18 09:32:35 login ovpn-utm[8335]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Jul 18 09:32:35 login ovpn-utm[8335]: Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Jul 18 09:32:35 login ovpn-utm[8335]: Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication Jul 18 09:32:35 login ovpn-utm[8335]: Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Jul 18 09:32:35 login ovpn-utm[8335]: Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication Jul 18 09:32:35 login ovpn-utm[8335]: Preserving previous TUN/TAP instance: tun0 Jul 18 09:32:35 login ovpn-utm[8335]: NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device. Jul 18 09:32:35 login ovpn-utm[8335]: /sbin/ip route del EXT.IP.FROM.VPN/32 Jul 18 09:32:35 login ovpn-utm[8335]: /sbin/ip route del INT.BEHIND.VPN2.0/24 Jul 18 09:32:35 login ovpn-utm[8335]: /sbin/ip route del INT.BEHIND.VPN1.0/24 Jul 18 09:32:35 login ovpn-utm[8335]: Closing TUN/TAP interface Jul 18 09:32:35 login ovpn-utm[8335]: /sbin/ip addr del dev tun0 10.200.13.2/24 Jul 18 09:32:36 login ovpn-utm[8335]: ROUTE_GATEWAY TWO.NETWORK.2.1/255.255.255.0 IFACE=eth0 HWADDR=00:0c:29:cd:45:cc Jul 18 09:32:36 login ovpn-utm[8335]: TUN/TAP device tun0 opened Jul 18 09:32:36 login ovpn-utm[8335]: TUN/TAP TX queue length set to 100 Jul 18 09:32:36 login ovpn-utm[8335]: do_ifconfig, tt->did_ifco
Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect
Am 18.07.2017 um 12:58 schrieb Bernhard Schmidt: > The notworking version does nothing like this. This smells like a bug. > > What I don't understand is that you claim the VPN endpoint is not > reachable on the dead nodes (the outer IP I presume). Both nodes still > have a hostroute towards the VPN gateway in their routing table > I mean not the external VPN endpoint address, but the VPN internal server address (10.200.13.1 here). > > I've browsed through the git commits between 2.4.0 and 2.4.3, these > might be relevant here > > https://community.openvpn.net/openvpn/ticket/812 > https://community.openvpn.net/openvpn/ticket/887 > > Are you able to build a version with these patches applied yourself? I will build it for one of the notworking nodes and see what happens and give a feedback -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect
Am 18.07.2017 um 13:05 schrieb Patrick Matthäi: >> I've browsed through the git commits between 2.4.0 and 2.4.3, these >> might be relevant here >> >> https://community.openvpn.net/openvpn/ticket/812 >> https://community.openvpn.net/openvpn/ticket/887 >> >> Are you able to build a version with these patches applied yourself? > I will build it for one of the notworking nodes and see what happens and > give a feedback Yeah very nice! With both patches applied it is working :D Like the version 2.4.3-4 I get now a "NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device", all routes are removed and readded and the connection works again. Two hosts, which are not working after a restart of the server, do not have got this and refuse to work. Would love to see these patches in 9.1 :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect
Am 18.07.2017 um 13:29 schrieb Bernhard Schmidt: >>>> I've browsed through the git commits between 2.4.0 and 2.4.3, these >>>> might be relevant here >>>> >>>> https://community.openvpn.net/openvpn/ticket/812 >>>> https://community.openvpn.net/openvpn/ticket/887 >>>> >>>> Are you able to build a version with these patches applied yourself? >>> I will build it for one of the notworking nodes and see what happens and >>> give a feedback >> Yeah very nice! With both patches applied it is working :D Like the >> version 2.4.3-4 I get now a "NOTE: Pulled options changed on restart, >> will need to close and reopen TUN/TAP device", all routes are removed >> and readded and the connection works again. Two hosts, which are not >> working after a restart of the server, do not have got this and refuse >> to work. > Can you try to test which of those it is? I need a specific patch to get > into stable. I have tested it three times, it is definitly https://community.openvpn.net/openvpn/ticket/812 which fixes this issue > >> Would love to see these patches in 9.1 :) > 9.1 is already frozen, but I will submit it into 9.2 as soon as I know > which patch it is. Urgs right.. ;) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#849752: lintian: dpkg-source failed with status 2 / no such file or directory
Check script debian-readme for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: description on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script description for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: duplicate-files on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script duplicate-files for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: fields on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script fields for binary:libfizmo-dev/0.7.14-2/amd64 done (0.002s) N: Running check: filename-length on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script filename-length for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: files on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script files for binary:libfizmo-dev/0.7.14-2/amd64 done (0.028s) N: Running check: gir on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script gir for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: huge-usr-share on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script huge-usr-share for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: infofiles on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script infofiles for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: init.d on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script init.d for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: java on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script java for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: manpages on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script manpages for binary:libfizmo-dev/0.7.14-2/amd64 done (0.002s) N: Running check: md5sums on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script md5sums for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: menu-format on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script menu-format for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: menus on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script menus for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: ocaml on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script ocaml for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: scripts on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script scripts for binary:libfizmo-dev/0.7.14-2/amd64 done (0.001s) N: Running check: shared-libs on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script shared-libs for binary:libfizmo-dev/0.7.14-2/amd64 done (0.002s) N: Running check: symlinks on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script symlinks for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: systemd on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script systemd for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: triggers on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script triggers for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Running check: usrmerge on binary:libfizmo-dev/0.7.14-2/amd64 ... N: Check script usrmerge for binary:libfizmo-dev/0.7.14-2/amd64 done (0.000s) N: Checking all of group libfizmo/0.7.14-2 done (0.291s) N: Memory usage [libfizmo/0.7.14-2]: 171.81 kB N: Memory usage [changes:libfizmo/0.7.14-2/source_all_amd64]: 45.78 kB N: -- _shared_storage: 32.17 kB N: -- base_dir: 144.00 B N: -- field: 3.79 kB N: -- files: 9.08 kB N: -- name: 82.00 B N: -- type: 82.00 B N: Memory usage [binary:libfizmo-common/0.7.14-2/all]: 68.63 kB N: -- _shared_storage: 32.17 kB N: -- base_dir: 168.00 B N: -- changelog: 31.70 kB N: -- control: 192.00 B N: -- control_index: 68.75 kB N: -- field: 2.32 kB N: -- file_info: 1.53 kB N: -- index: 68.75 kB N: -- is_non_free: 72.00 B N: -- java_info: 176.00 B N: -- md5sums: 2.06 kB N: -- name: 89.00 B N: -- native: 82.00 B N: -- objdump_info: 176.00 B N: -- relation: 1427.00 B N: -- scripts: 176.00 B N: -- type: 82.00 B N: -- unpacked: 192.00 B N: Memory usage [binary:libfizmo-dev/0.7.14-2/amd64]: 124.75 kB N: -- _shared_storage: 32.17 kB N: -- base_dir: 160.00 B N: -- changelog: 31.72 kB N: -- control: 192.00 B N: -- control_index: 124.88 kB N: -- field: 2.25 kB N: -- file_info: 6.62 kB N: -- index: 124.88 kB N: -- is_non_free: 72.00 B N: -- java_info: 176.00 B N: -- md5sums: 10.30 kB N: -- name: 86.00 B N: -- native: 82.00 B N: -- objdump_info: 22.73 kB N: -- relation: 1.75 kB N: -- scripts: 176.00 B N: -- type: 82.00 B N: -- unpacked: 192.00 B -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#866751: wrong table structure for innodb_table_stats
Hi, I have got the same issue on all MariaDB 10.0 => 10.1 (jessie to stretch) upgraded servers. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#869838: kdenlive: closing all file descriptors for no reason whatsoever
Am 27.07.2017 um 00:37 schrieb Salvo Tomaselli: > Package: kdenlive > Version: 17.04.3-1 > Severity: minor > Tags: upstream > > Dear Maintainer, > while I was using strace on kdenlive, I noticed that when terminating, it > closes descriptors from 0 to 1023 for no reason. > > 1. the kernel does that > 2. I suppose they have massive file descriptor leaks, if they close files like >that? > > Per se it's not a big issue, but it's an indicator of bad practice. Hi, I think it is better if you report such issues directly to the kdenlive upstream bugtracker. Wasn't this issue present in < 17.04.3? > > Best > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages kdenlive depends on: > ii ffmpeg 7:3.2.6-1+b3 > ii kded55.28.0-1 > ii kdenlive-data17.04.3-1 > ii kinit5.28.0-1 > ii kio 5.28.0-2 > ii libc62.24-12 > ii libgcc1 1:7.1.0-10 > ii libgl1-mesa-glx [libgl1] 17.1.4-1 > ii libglu1-mesa [libglu1] 9.0.0-2.1 > ii libkf5archive5 5.28.0-2 > ii libkf5attica55.28.0-1 > ii libkf5auth5 5.28.0-2 > ii libkf5bookmarks5 5.28.0-1 > ii libkf5codecs55.28.0-1+b2 > ii libkf5completion55.28.0-1 > ii libkf5configcore55.28.0-2 > ii libkf5configgui5 5.28.0-2 > ii libkf5configwidgets5 5.28.0-2 > ii libkf5coreaddons55.28.0-2 > ii libkf5crash5 5.28.0-1 > ii libkf5dbusaddons55.28.0-1 > ii libkf5filemetadata3 5.28.0-1+b2 > ii libkf5guiaddons5 5.28.0-1 > ii libkf5i18n5 5.28.0-2 > ii libkf5iconthemes55.28.0-2 > ii libkf5itemviews5 5.28.0-1 > ii libkf5jobwidgets55.28.0-2 > ii libkf5kiocore5 5.28.0-2 > ii libkf5kiofilewidgets55.28.0-2 > ii libkf5kiowidgets55.28.0-2 > ii libkf5newstuff5 5.28.0-1 > ii libkf5notifications5 5.28.0-1 > ii libkf5notifyconfig5 5.28.0-1 > ii libkf5service-bin5.28.0-1 > ii libkf5service5 5.28.0-1 > ii libkf5solid5 5.28.0-4 > ii libkf5sonnetui5 5.28.0-2+b1 > ii libkf5textwidgets5 5.28.0-1 > ii libkf5widgetsaddons5 5.28.0-3 > ii libkf5xmlgui55.28.0-1 > ii libmlt++36.4.1-5+b1 > ii libmlt6 6.4.1-5+b1 > ii libqt5concurrent55.7.1+dfsg-4 > ii libqt5core5a 5.7.1+dfsg-4 > ii libqt5dbus5 5.7.1+dfsg-4 > ii libqt5gui5 5.7.1+dfsg-4 > ii libqt5network5 5.7.1+dfsg-4 > ii libqt5qml5 5.7.1-2+b2 > ii libqt5quick5 5.7.1-2+b2 > ii libqt5script55.7.1~20161021+dfsg-2 > ii libqt5svg5 5.7.1~20161021-2+b2 > ii libqt5widgets5 5.7.1+dfsg-4 > ii libqt5xml5 5.7.1+dfsg-4 > ii libstdc++6 7.1.0-10 > ii libv4l-0 1.12.5-1 > ii melt 6.4.1-5+b1 > ii oxygen-icon-theme5:5.28.0-1 > ii qml-module-qtquick-controls 5.7.1~20161021-2 > ii qml-module-qtquick2 5.7.1-2+b2 > > Versions of packages kdenlive recommends: > pn dvdauthor > pn dvgrab > pn frei0r-plugins > pn genisoimage > pn recordmydesktop > pn swh-plugins > > Versions of packages kdenlive suggests: > pn khelpcenter > > -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#869837: kdenlive: busy loop
.28.0-2 > ii libkf5bookmarks5 5.28.0-1 > ii libkf5codecs55.28.0-1+b2 > ii libkf5completion55.28.0-1 > ii libkf5configcore55.28.0-2 > ii libkf5configgui5 5.28.0-2 > ii libkf5configwidgets5 5.28.0-2 > ii libkf5coreaddons55.28.0-2 > ii libkf5crash5 5.28.0-1 > ii libkf5dbusaddons55.28.0-1 > ii libkf5filemetadata3 5.28.0-1+b2 > ii libkf5guiaddons5 5.28.0-1 > ii libkf5i18n5 5.28.0-2 > ii libkf5iconthemes55.28.0-2 > ii libkf5itemviews5 5.28.0-1 > ii libkf5jobwidgets55.28.0-2 > ii libkf5kiocore5 5.28.0-2 > ii libkf5kiofilewidgets55.28.0-2 > ii libkf5kiowidgets55.28.0-2 > ii libkf5newstuff5 5.28.0-1 > ii libkf5notifications5 5.28.0-1 > ii libkf5notifyconfig5 5.28.0-1 > ii libkf5service-bin5.28.0-1 > ii libkf5service5 5.28.0-1 > ii libkf5solid5 5.28.0-4 > ii libkf5sonnetui5 5.28.0-2+b1 > ii libkf5textwidgets5 5.28.0-1 > ii libkf5widgetsaddons5 5.28.0-3 > ii libkf5xmlgui55.28.0-1 > ii libmlt++36.4.1-5+b1 > ii libmlt6 6.4.1-5+b1 > ii libqt5concurrent55.7.1+dfsg-4 > ii libqt5core5a 5.7.1+dfsg-4 > ii libqt5dbus5 5.7.1+dfsg-4 > ii libqt5gui5 5.7.1+dfsg-4 > ii libqt5network5 5.7.1+dfsg-4 > ii libqt5qml5 5.7.1-2+b2 > ii libqt5quick5 5.7.1-2+b2 > ii libqt5script5 5.7.1~20161021+dfsg-2 > ii libqt5svg5 5.7.1~20161021-2+b2 > ii libqt5widgets5 5.7.1+dfsg-4 > ii libqt5xml5 5.7.1+dfsg-4 > ii libstdc++6 7.1.0-10 > ii libv4l-0 1.12.5-1 > ii melt 6.4.1-5+b1 > ii oxygen-icon-theme5:5.28.0-1 > ii qml-module-qtquick-controls 5.7.1~20161021-2 > ii qml-module-qtquick2 5.7.1-2+b2 > > Versions of packages kdenlive recommends: > pn dvdauthor > pn dvgrab > pn frei0r-plugins > pn genisoimage > pn recordmydesktop > pn swh-plugins > > Versions of packages kdenlive suggests: > pn khelpcenter > > -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#869837: kdenlive: busy loop
If I understood you correct you have started with .3, so if you upgrade,
delete again the config directories and try to use it again, still there
the issue?
Am 27.07.2017 um 10:23 schrieb Salvo Tomaselli:
> I deleted all my .kdenlive data and downgraded to .2 and it doesn't
> seem to have the issue.
>
> But now it might be difficult to reproduce, because I didn't think of
> keeping it or the cache.
>
> 2017-07-27 9:56 GMT+02:00 Patrick Matthäi :
>> Am 27.07.2017 um 00:32 schrieb Salvo Tomaselli:
>>> Package: kdenlive
>>> Version: 17.04.3-1
>>> Severity: grave
>>> Justification: renders package unusable
>>>
>>> Dear Maintainer,
>>> kdenlive does a busy loop, and is basically keeping the CPU too busy doing
>>> that, to actually do anything productive.
>>>
>>> When I start it, CPU jumps at 100%.
>> Could you reproduce this issue with kdenlive < 17.04.3? What happens if
>> you try it out with a fresh profile.
>>
>>> with strace I get this:
>>>
>>> futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
>>> FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
>>> writev(3,
>>> [{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
>>> iov_len=52}], 1) = 52
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3",
>>> iov_len=16}], 1) = 16
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
>>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
>>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>>>
>>> Over and over.
>>>
>>> Best.
>>&g
Bug#869226: kdenlive: Segmentation fault when exiting
-1 > ii libkf5i18n5 5.28.0-2 > ii libkf5iconthemes55.28.0-2 > ii libkf5itemviews5 5.28.0-1 > ii libkf5jobwidgets55.28.0-2 > ii libkf5kiocore5 5.28.0-2 > ii libkf5kiofilewidgets55.28.0-2 > ii libkf5kiowidgets55.28.0-2 > ii libkf5newstuff5 5.28.0-1 > ii libkf5notifications5 5.28.0-1 > ii libkf5notifyconfig5 5.28.0-1 > ii libkf5service-bin5.28.0-1 > ii libkf5service5 5.28.0-1 > ii libkf5solid5 5.28.0-4 > ii libkf5sonnetui5 5.28.0-2+b1 > ii libkf5textwidgets5 5.28.0-1 > ii libkf5widgetsaddons5 5.28.0-3 > ii libkf5xmlgui55.28.0-1 > ii libmlt++36.4.1-5+b1 > ii libmlt6 6.4.1-5+b1 > ii libqt5concurrent55.7.1+dfsg-4 > ii libqt5core5a 5.7.1+dfsg-4 > ii libqt5dbus5 5.7.1+dfsg-4 > ii libqt5gui5 5.7.1+dfsg-4 > ii libqt5network5 5.7.1+dfsg-4 > ii libqt5qml5 5.7.1-2+b2 > ii libqt5quick5 5.7.1-2+b2 > ii libqt5script55.7.1~20161021+dfsg-2 > ii libqt5svg5 5.7.1~20161021-2+b2 > ii libqt5widgets5 5.7.1+dfsg-4 > ii libqt5xml5 5.7.1+dfsg-4 > ii libstdc++6 7.1.0-9 > ii libv4l-0 1.12.5-1 > ii melt 6.4.1-5+b1 > ii oxygen-icon-theme5:5.28.0-1 > ii qml-module-qtquick-controls 5.7.1~20161021-2 > ii qml-module-qtquick2 5.7.1-2+b2 > > Versions of packages kdenlive recommends: > ii dvdauthor0.7.0-2 > ii dvgrab 3.5+git20160707.1.e46042e-1 > ii frei0r-plugins 1.6.1-1 > ii genisoimage 9:1.1.11-3+b2 > ii recordmydesktop 0.3.8.1+svn602-1+b2 > ii swh-plugins 0.4.17-2 > > Versions of packages kdenlive suggests: > pn khelpcenter > > -- debconf-show failed -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
severity #864642 normal thanks Am 16.07.2017 um 23:42 schrieb Ben Hutchings: > Control: tag -1 moreinfo > > Sven asked this, but forgot to add you to the recipients: > > On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote: >> Hi! >> >>> Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ? > Note that this has been root-caused as a bug in the virtual device, not > the driver. (Though it would be nice if the driver could work around > it.) > > Ben. I can confirm, that the VMs do not crash anymore with vSphere 6.5 build 5969303 from 27.07.2017, that is why I lowered the severity. But we have got still the issue with "Driver has suspect GRO implementation, TCP performance may be compromised" and the fact, that 4.9.18-1 wasn't crashing and has not this message, while 4.9.30-1 was crashing with the message. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#870864: bmon FTCBFS: uses the build architecture pkg-config
tag #870864 + pending thanks Am 05.08.2017 um 22:33 schrieb Helmut Grohne: > Source: bmon > Version: 1:4.0-4 > Tags: upstream patch > User: helm...@debian.org > Usertags: rebootstrap > > bmon fails to cross build from source, because it uses the build > architecture pkg-config. After switching detection to > PKG_PROG_PKG_CONFIG (which considers $ac_tool_prefix), cross builds > succeed. Please consider applying the attached patch. > > Helmut Thanks for your patch -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#833357: corosync: Update to 2.3.6 fails with specific configuration / upstream fixed
Package: corosync
Version: 2.3.6-2
Severity: serious
Tags: patch upstream
Hi,
updating corosync from 2.3.5 to 2.3.6 fails with some configurations (as I
already reported to the bpo list) with:
"can't autogenerate multicast address"
Upstream report and patch: https://github.com/corosync/corosync/issues/137
Please apply the patch and I would also welcome updated backports packages :)
Here is one of my /etc/corosync/corosync.conf configurations, with that it is
reproduceable:
totem {
version: 2
token: 3000
token_retransmits_before_loss_const: 10
clear_node_high_bit: yes
crypto_cipher: none
crypto_hash: none
transport: udpu
interface {
ringnumber: 0
bindnetaddr: 192.168.99.0
}
}
logging {
to_logfile: yes
logfile: /var/log/corosync/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: QUORUM
debug: off
}
}
quorum {
provider: corosync_votequorum
two_node: 1
wait_for_all: 1
}
nodelist {
node {
ring0_addr: nd1-1-cs
}
node {
ring0_addr: nd1-2-cs
}
}
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#852346: kdenlive: crash on startup
reassign #852346 src:nvidia-graphics-drivers thanks Am 23.01.2017 um 19:10 schrieb George B.: > Package: kdenlive > Version: 16.12.1-1 > Severity: important > > Hello, > > Kdenlive crashes on startup: > > ``` > OpenGL vendor: "NVIDIA Corporation" > OpenGL renderer: "Quadro M1000M/PCIe/SSE2" > OpenGL Threaded: true > OpenGL ARG_SYNC: true > OpenGL OpenGLES: false > OpenGL vendor: "NVIDIA Corporation" > OpenGL renderer: "Quadro M1000M/PCIe/SSE2" > OpenGL Threaded: true > OpenGL ARG_SYNC: true > OpenGL OpenGLES: false > QOpenGLFunctions created with non-current context > Segmentation fault (core dumped) > ``` > > syslog has > ``` > [95683.085432] FrameRenderer[9753]: segfault at a8 ip 55d95179c919 sp > 7f3f30c51650 error 4 in kdenlive[55d951452000+5f5000] > ``` > FrameRenderer is from the nvidia driver, which is crashing -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#833746: kdenlive: When import clip: clip is invalid
Am 08.08.2016 um 14:23 schrieb Massimo Barbieri: > Package: kdenlive > Version: 16.04.3-1 > Severity: important > > Dear Maintainer, > > when I try to import video clip in kdenlive I always got the message "Clip is > invalid, will be removed from project". I tryed with different video format > and > codecs but I always receive this error. > > In the terminal > / / / / / / / / ERROR / / / / // CANNOT LOAD PRODUCER: > "/home/myself/video.mov" > > Thanks for your work! > Massimo > > Does it work with an up to date testing? If not what happens if you open the video e.g. with: $ melt video.mov -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#847700: kdenlive: I can't render ANY format
Am 10.12.2016 um 19:20 schrieb david: > Package: kdenlive > Version: 16.08.3-1 > Severity: important > > Dear Maintainer, > > Tested with WebM, MP4, MP4-H265, Webm... The render doesn't end. Melt go upto > percentage 99 and that is all, without error messages :( > Hi, does it still happen with an up to date testing and kdenlive from sid (16.12.1-1)? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#836671: kdenlive: Icons of the GUI missing
Hi, Am 04.09.2016 um 17:01 schrieb Massimo Barbieri: > Package: kdenlive > Version: 16.08.0-1 > Severity: normal > > Dear Maintainer, > > after the upgrade to the last version of kdenlive some icons of the GUI are > missed and replaced with text description. For example "Set zone In" "Set > zone out" in the monitor clip, or "Insert Clip Zone in Timeline" anc many > others. > > Thanks in advance for your work!! > Max Is this still the case in testing? Got something similar for some weeks but I think it was an error in KDE itself -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#827989: kdenlive: Degraded title text when no adjucent video track is used with Affine transition
Hi, I hadn't got any feedback yet. May you retest it with 16.12.1 please? Am 08.07.2016 um 12:41 schrieb Patrick Matthäi: > Hi JB, > > could you work with this? > > > Am 23.06.2016 um 15:49 schrieb Evangelos Skarmoutsos: >> Package: kdenlive >> Version: 16.04.2-1 >> Severity: normal >> >> Dear Maintainer, >> >> When a title clip is above a video clip on different video tracks, and there >> is >> at least one empty video track between them, and Affine transition track is >> set >> to Auto, then, text does not show up correctly. >> >> To recreate the problem add a 10 second title clip at the start of Video3 >> track, a 5 second video clip (or image) at the start of Video2 track and a 5 >> second video clip (or image) at the 5th second of the Video1 track. >> Now slide around 4th to 6th second to see the difference. >> >> Since the preview is usually not large enough, the text appears as slightly >> degraded. If you add some shadow to the text it will be much easier to view >> the >> differences. >> >> Workaround: >> Selecting Affine properties and changing from track:Auto to the track:Video1, >> (or whichever track the video clip resides) resolves the issue. >> >> >> >> >> -- System Information: >> Debian Release: stretch/sid >> APT prefers testing >> APT policy: (500, 'testing') >> Architecture: amd64 (x86_64) >> Foreign Architectures: i386 >> >> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) >> Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages kdenlive depends on: >> ii ffmpeg 8:1.0.8-dmo1 >> ii kded55.22.0-1 >> ii kdenlive-data16.04.2-1 >> ii kinit5.22.0-1 >> ii kio 5.22.0-1 >> ii libc62.22-11 >> ii libgcc1 1:6.1.1-4 >> ii libgl1-mesa-glx [libgl1] 11.2.2-1 >> ii libglu1-mesa [libglu1] 9.0.0-2.1 >> ii libkf5archive5 5.23.0-1 >> ii libkf5attica55.23.0-1 >> ii libkf5auth5 5.22.0-1 >> ii libkf5bookmarks5 5.22.0-2 >> ii libkf5codecs55.23.0-1 >> ii libkf5completion55.22.0-1 >> ii libkf5configcore55.23.0-1 >> ii libkf5configgui5 5.23.0-1 >> ii libkf5configwidgets5 5.22.0-1 >> ii libkf5coreaddons55.23.0-1 >> ii libkf5crash5 5.22.0-1 >> ii libkf5dbusaddons55.23.0-1 >> ii libkf5filemetadata3 5.22.0-1 >> ii libkf5guiaddons5 5.23.0-1 >> ii libkf5i18n5 5.22.1-1 >> ii libkf5iconthemes55.22.0-1 >> ii libkf5itemviews5 5.23.0-1 >> ii libkf5jobwidgets55.22.0-1 >> ii libkf5kiocore5 5.22.0-1 >> ii libkf5kiofilewidgets55.22.0-1 >> ii libkf5kiontlm5 5.22.0-1 >> ii libkf5kiowidgets55.22.0-1 >> ii libkf5newstuff5 5.22.0-1 >> ii libkf5notifications5 5.22.0-1 >> ii libkf5notifyconfig5 5.22.0-1 >> ii libkf5plotting5 5.23.0-1 >> ii libkf5service-bin5.22.0-1 >> ii libkf5service5 5.22.0-1 >> ii libkf5solid5 5.23.0-1 >> ii libkf5sonnetui5 5.23.0-1 >> ii libkf5textwidgets5 5.22.0-1 >> ii libkf5widgetsaddons5 5.23.0-1 >> ii libkf5xmlgui55.22.0-1 >> ii libmlt++36.2.0-1 >> ii libmlt6 6.2.0-1 >> ii libqt5concurrent55.6.1+dfsg-2 >> ii libqt5core5a 5.6.1+dfsg-2 >> ii libqt5dbus5 5.6.1+dfsg-2 >> ii libqt5gui5 5.6.1+dfsg-2 >> ii libqt5network5 5.6.1+dfsg-2 >> ii libqt5qml5 5.6.1-4 >> ii libqt5quick5 5.6.1-4 >> ii libqt5script55.6.1+dfsg-2 >> ii libqt5svg5 5.6.1-2 >> ii libqt5widgets5 5.6.1+dfsg-2 >> ii libqt5xml5 5.6.1+dfsg-2 >> ii libstdc++6 6.1.1-4 >> ii libv4l-0 1.10.1-1 >> ii melt 6.2.0-1 >> ii oxygen-icon-theme4:4.14.0-1 >> ii qml-module-qtquick-controls 5.6.1-2 >> ii qml-module-qtquick2 5.6.1-4 >> >> Versions of packages kdenlive recommends: >> ii dvdauthor0.7.0-1.4+b1 >> pn dvgrab >> ii frei0r-plugins 1.4-3+b1 >> ii genisoimage 9:1.1.11-3 >> ii recordmydesktop 0.3.8.1+svn602-1+b1 >> ii swh-plugins 0.4.16+git20160602~repack1-2 >> >> Versions of packages kdenlive suggests: >> ii khelpcenter 4:16.04.1-1 >> >> -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#843824: kdenlive: Screen Grab has hard coded display setting
Hello JB,
I think this issue is still up to date with 16.12.1, since from
kdenlive-16.12.1/src/monitor/recmonitor.cpp:
710 if (!KdenliveSettings::grab_hide_frame()) m_captureArgs <<
QStringLiteral("-show_region") << QStringLiteral("1");
711 captureSize = QStringLiteral(":0.0");
712 if (KdenliveSettings::grab_capture_type() == 0) {
713 // Full screen capture
Could you apply the patch please?
Am 09.11.2016 um 23:33 schrieb Daniel Keast:
> Package: kdenlive
> Version: 0.9.10-2
> Severity: normal
>
> Dear Maintainer,
>
> The screen grab feature has the DISPLAY location hard coded. When I attempt to
> record my desktop I get a notification with the message "x11grab Could not
> open
> X display. :0.0: Input/output error".
>
> This patch fixes the issue for me:
>
> diff --git a/kdenlive-0.9.10/src/monitor/recmonitor.cpp
> b/kdenlive-0.9.10/src/monitor/recmonitor.cpp
> index f465d82..57b5536 100644
> --- a/kdenlive-0.9.10/src/monitor/recmonitor.cpp
> +++ b/kdenlive-0.9.10/src/monitor/recmonitor.cpp
> @@ -29,6 +29,8 @@
> #include "videosurface.h"
> #include
>
> +#include
> +
> #include
> #include
> #include
> @@ -731,7 +733,8 @@ void RecMonitor::slotRecord()
> m_captureArgs << "-f" << "x11grab";
> if (KdenliveSettings::grab_follow_mouse()) m_captureArgs <<
> "-follow_mouse" << "centered";
> if (!KdenliveSettings::grab_hide_frame()) m_captureArgs <<
> "-show_region" << "1";
> - captureSize = ":0.0";
> + captureSize = std::genenv("DISPLAY");
> + if (captureSize == NULL) captureSize = ":0.0";
> if (KdenliveSettings::grab_capture_type() == 0) {
> // Full screen capture
> m_captureArgs << "-s" << QString::number(screenSize.width())
> + 'x' + QString::number(screenSize.height());
>
>
> -- System Information:
> Debian Release: 8.6
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages kdenlive depends on:
> ii kde-runtime 4:4.14.2-2
> ii kdenlive-data 0.9.10-2
> ii libav-tools 6:11.8-1~deb8u1
> ii libc6 2.19-18+deb8u6
> ii libgcc1 1:4.9.2-10
> ii libgl1-mesa-glx [libgl1] 10.3.2-1+deb8u1
> ii libglu1-mesa [libglu1]9.0.0-2
> ii libkdecore5 4:4.14.2-5+deb8u1
> ii libkdeui5 4:4.14.2-5+deb8u1
> ii libkio5 4:4.14.2-5+deb8u1
> ii libknewstuff3-4 4:4.14.2-5+deb8u1
> ii libknotifyconfig4 4:4.14.2-5+deb8u1
> ii libkrossui4 4:4.14.2-5+deb8u1
> ii libmlt++3 0.9.2-2
> ii libmlt6 0.9.2-2
> ii libnepomuk4 4:4.14.2-5+deb8u1
> ii libqjson0 0.8.1-3
> ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
> ii libsolid4 4:4.14.2-5+deb8u1
> ii libsoprano4 2.9.4+dfsg-1.1
> ii libstdc++64.9.2-10
> ii libv4l-0 1.6.0-2
> ii libx11-6 2:1.6.2-3
> ii libxau6 1:1.0.8-1
> ii libxdmcp6 1:1.1.1-1+b1
> ii libxext6 2:1.3.3-1
> ii melt 0.9.2-2
>
> Versions of packages kdenlive recommends:
> ii dvdauthor0.7.0-1.3
> ii dvgrab 3.5-2+b2
> ii frei0r-plugins 1.4-3
> ii genisoimage 9:1.1.11-3
> ii recordmydesktop 0.3.8.1+svn602-1+b1
> ii swh-plugins 0.4.15+1-7
>
> Versions of packages kdenlive suggests:
> pn khelpcenter4
>
> -- no debconf information
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
Bug#847700: kdenlive: I can't render ANY format
Am 24.01.2017 um 09:37 schrieb david: > El martes 24 de enero, Patrick Matthäi escribió: >> Am 10.12.2016 um 19:20 schrieb david: >>> Package: kdenlive >>> Version: 16.08.3-1 >>> Severity: important >>> >>> Dear Maintainer, >>> >>> Tested with WebM, MP4, MP4-H265, Webm... The render doesn't end. Melt go >>> upto >>> percentage 99 and that is all, without error messages :( >>> >> Hi, >> does it still happen with an up to date testing and kdenlive from sid >> (16.12.1-1)? > Yes. I tested yesterday :( > Also with a short test video? If yes, can you play this test video source with: $ melt video.avi Does it work? Does it only shows 99% or is the melt process running and consuming ressources in the background? What is the output of: dpkg -l|egrep 'libav|libmlt|melt|ffmpeg|libsw' -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#847700: kdenlive: I can't render ANY format
Am 24.01.2017 um 11:24 schrieb david: > El martes 24 de enero, Patrick Matthäi escribió: >> Also with a short test video? If yes, can you play this test video >> source with: >> $ melt video.avi >> Does it work? > It works without problem. > >> Does it only shows 99% or is the melt process running and consuming >> ressources in the background? > It shows 100% of video. But I don't understand how is this related to the > render problem. > >> What is the output of: >> dpkg -l|egrep 'libav|libmlt|melt|ffmpeg|libsw' > > ii ffmpeg 7:3.2.2-1 > amd64Tools for transcoding, streaming and playing of multimedia > files > ii gstreamer1.0-libav:amd64 1.10.2-1 > amd64libav plugin for GStreamer > ii libavahi-client3:amd64 0.6.32-1 > amd64Avahi client library > ii libavahi-client3:i386 0.6.32-1 > i386 Avahi client library > ii libavahi-common-data:amd64 0.6.32-1 > amd64Avahi common data files > ii libavahi-common-data:i386 0.6.32-1 > i386 Avahi common data files > ii libavahi-common3:amd64 0.6.32-1 > amd64Avahi common library > ii libavahi-common3:i386 0.6.32-1 > i386 Avahi common library > ii libavahi-core7:amd64 0.6.32-1 > amd64Avahi's embeddable mDNS/DNS-SD library > ii libavahi-glib1:amd64 0.6.32-1 > amd64Avahi GLib integration library > ii libavc1394-0:amd64 0.5.4-4 > amd64control IEEE 1394 audio/video devices > ii libavcodec57:amd64 7:3.2.2-1 > amd64FFmpeg library with de/encoders for audio/video codecs - > runtime files > ii libavcodec57:i386 7:3.2.2-1 > i386 FFmpeg library with de/encoders for audio/video codecs - > runtime files > ii libavdevice57:amd647:3.2.2-1 > amd64FFmpeg library for handling input and output devices - > runtime files > ii libavfilter6:amd64 7:3.2.2-1 > amd64FFmpeg library containing media filters - runtime files > ii libavformat57:amd647:3.2.2-1 > amd64FFmpeg library with (de)muxers for multimedia containers - > runtime files > ii libavresample3:amd64 7:3.2.2-1 > amd64FFmpeg compatibility library for resampling - runtime files > ii libavresample3:i3867:3.2.2-1 > i386 FFmpeg compatibility library for resampling - runtime files > ii libavutil55:amd64 7:3.2.2-1 > amd64FFmpeg library with functions for simplifying programming > - runtime files > ii libavutil55:i386 7:3.2.2-1 > i386 FFmpeg library with functions for simplifying programming > - runtime files > ii libmlt++3 6.4.1-1 > amd64MLT multimedia framework C++ wrapper (runtime) > ii libmlt-data6.4.1-1 > all multimedia framework (data) > ii libmlt66.4.1-1 > amd64multimedia framework (runtime) > ii libswresample2:amd64 7:3.2.2-1 > amd64FFmpeg library for audio resampling, rematrixing etc. - > runtime files > ii libswresample2:i3867:3.2.2-1 > i386 FFmpeg library for audio resampling, rematrixing etc. - > runtime files > ii libswscale4:amd64 7:3.2.2-1 > amd64FFmpeg library for image scaling and various conversions - > runtime files > ii melt 6.4.1-1 > amd64command line media player and video editor > ii moc-ffmpeg-plugin 1
Bug#847700: kdenlive: I can't render ANY format
Am 24.01.2017 um 11:47 schrieb david:
> El martes 24 de enero, Patrick Matthäi escribió:
>> Hum. Could you please move away your cache and config data from kdenlive
>> (should be located in ~/.kdenlive ~/.cache ~/.local).
> I have deleted all kdenlive stuff inside .cache and .local. I don't see
> anything .kdenlive related; instead, I have deleted too .kde/share/apps.
>
> After all this, try with a render and this is kdenlive terminal output:
>
> --
> //STARTING RENDERING: true , false , "/usr/bin/melt" , "dv_pal" , "avformat"
> , "-" , "/tmp/kdenlive_rendering_Z30204.mlt" ,
> "/home/david/Documentos/marcoto.mp4" , () , ("glsl.=1",
> "properties=x264-medium", "f=mp4", "vcodec=libx264", "acodec=aac", "g=120",
> "crf=23", "ab=160k", "preset=faster", "progressive=1", "threads=4",
> "real_time=-4") , 0 , 1545
> Skipped method "slotGotProgressInfo" : Type not registered with QtDBus in
> parameter list: MessageType
> Skipped method "slotTimelineClipSelected" : Pointers are not supported:
> ClipItem*
> Skipped method "slotTimelineClipSelected" : Pointers are not supported:
> ClipItem*
> Unsupported return type 65 QPixmap in method "grab"
> Unsupported return type 65 QPixmap in method "grab"
> --
>
> Process seems locked with a "Remaining time 00:00:00". I can't see the result
> video.
>
>
If you save the project and then execute this:
$ melt ~/path/to/yourprojectfile/project.kdenlive
Does it play the whole project and what are the outputs of melt? You may
also use the -debug option
signature.asc
Description: OpenPGP digital signature
Bug#853049: kded5 crashes nearly every time on copying files with dolphin
Subject: kded5 crashes nearly every time on copying files with dolphin Package: kded5 Version: 5.28.0-1 Severity: important Dear Maintainer, nearly every time I'm moving/copying etc files with dolphin (so that the activity manager starts working), kded5 crashes, which results in a not working (unresponsive) taskbar. To get it work again I always have to switch to VT1 and then back to VT7 (so a new kded5 spawns). I have got this issue now since november. Starting with a fresh profile or removing caches and settings does not help. The only useful output is this from xsession-errors: QXcbConnection: XCB error: 3 (BadWindow), sequence: 26736, resource id: 106954752, major code: 18 (ChangeProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 26757, resource id: 106954753, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' kdeinit5: PID 2046 terminated. QXcbConnection: XCB error: 3 (BadWindow), sequence: 28026, resource id: 106954758, major code: 15 (QueryTree), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 28160, resource id: 106954771, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: PID 2234 terminated. kdeinit5: PID 2241 terminated. ark.main: "image/jpeg" is not a supported mimetype ark.main: "image/jpeg" is not a supported mimetype ark.main: "" is not a supported mimetype QXcbConnection: XCB error: 3 (BadWindow), sequence: 42287, resource id: 96469035, major code: 2 (ChangeWindowAttributes), minor code: 0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so' Qt: Session management error: networkIdsList argument is NULL Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" ark.main: "" is not a supported mimetype Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "image/jpeg" Guess plugin: "jpegthumbnail" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" ark.main: "inode/directory" is not a supported mimetype Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" Wanting MIME Type: "inode/directory" kdeinit5: PID 2049 terminated. kdeinit5: PID 2249 terminated. QXcbConnection: XCB error: 3 (BadWindow), sequence: 2780, resource id: 102767248, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: PID 2047 terminated. kdeinit5: PID 2107 terminated. QXcbConnection: XCB error: 3 (BadWindow), sequence: 2785, resource id: 98566148, major code: 18 (ChangeProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 3619, resource id: 96469064, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: PID 1597 terminated. QXcbConnection: XCB error: 3 (BadWindow), sequence: 3627, resource id: 106954756, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: PID 1648 terminated. kdeinit5: PID 2115 terminated. kdeinit5: PID 2233 terminated. kdeinit5: PID 2246 terminated. QXcbConnection: XCB error: 3 (BadWindow), sequence: 5519, resource id: 39890793, major code: 20 (GetProperty), minor code: 0 QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not
Bug#847700: kdenlive: I can't render ANY format
Could you send me the project (short clip and the project file) so I can test it? Did you ever installed something from other sources then Debian itself? Most bugs like this come from faulty external libs.. And the full output of "dpkg -l" and "apt-cache policy" would be good Am 29.01.2017 um 11:54 schrieb david: > El domingo 29 de enero, Patrick Matthäi escribió: >> If you save the project and then execute this: >> $ melt ~/path/to/yourprojectfile/project.kdenlive >> >> Does it play the whole project and what are the outputs of melt? You may >> also use the -debug option > It doesn't play it. > > Here is the output: > > -- > +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ > |1=-10| |2= -5| |3= -2| |4= -1| |5= 0| |6= 1| |7= 2| |8= 5| |9= 10| > +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ > +-+ > | H = back 1 minute, L = forward 1 minute | > | h = previous frame, l = next frame | > | g = start of clip, j = next clip, k = previous clip | > |0 = restart, q = quit, space = play | > +-+ > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [filter avcolor_space] Invalid format glsl > [filter avcolor_space] Invalid format glsl > [filter avcolor_space] Invalid format glsl > Violación de segmento > -- >
Bug#847700: kdenlive: I can't render ANY format
reassign #847700 src:mlt tag #847700 + upstream forwarded #847700 https://github.com/mltframework/shotcut/issues/337 thanks Am 29.01.2017 um 11:54 schrieb david: > El domingo 29 de enero, Patrick Matthäi escribió: >> If you save the project and then execute this: >> $ melt ~/path/to/yourprojectfile/project.kdenlive >> >> Does it play the whole project and what are the outputs of melt? You may >> also use the -debug option > It doesn't play it. > > Here is the output: > > -- > +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ > |1=-10| |2= -5| |3= -2| |4= -1| |5= 0| |6= 1| |7= 2| |8= 5| |9= 10| > +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ > +-+ > | H = back 1 minute, L = forward 1 minute | > | h = previous frame, l = next frame | > | g = start of clip, j = next clip, k = previous clip | > |0 = restart, q = quit, space = play | > +-+ > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0. > [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 2 > (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 3 > (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec > Consider increasing the value for the 'analyzeduration' and 'probesize' > options > [filter avcolor_space] Invalid format glsl > [filter avcolor_spa
Bug#854066: linux-image-4.9.0-1-amd64: Several HP desktops do not wake up anymore since 4.9
p=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.9.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.127 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.9.0-1-amd64 recommends: ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.2 Versions of packages linux-image-4.9.0-1-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02~beta3-3 pn linux-doc-4.9 Versions of packages linux-image-4.9.0-1-amd64 is related to: ii firmware-amd-graphics 20161130-2 pn firmware-atheros ii firmware-bnx2 20161130-2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas ii firmware-linux-nonfree20161130-2 ii firmware-misc-nonfree 20161130-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic ii firmware-realtek 20161130-2 pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#818961: [Debian-ha-maintainers] Freeze status, Heartbeat plans
Am 21.12.2016 um 11:50 schrieb Christoph Berg: > Re: Valentin Vidic 2016-12-20 > <20161220134034.grvwdktsmtbij...@gavran.carpriv.carnet.hr> >> And if there are big issues with systemd support I think there would be >> more bug reports for the jessie version of this package already? > It might be that with the previously poor state of HA in Jessie, users > aren't really reporting issues of that kind anymore :( > > I guess the basic question is if we want to continue to ship&support > heartbeat, or if that ship has sailed and we simply drop it. > > There are still users of the "simple" v1 mode. I'd assume they know > that for anything more complex they should switch to > corosync+pacemaker, so the question would be how much of the v1 mode > is still working. If the "average" case is broken on systemd systems, > we should fix or remove heartbeat. If the average case still works, we > can continue to ship it. > > Patrick, what's your position here? > > The drbd/fs/ip/apache example shown in the serverfault question looks > simple enough. Maybe someone could try a test setup? > > Christoph We tried out many test cases, workarounds, debugging on this issue and the result was, that the v1 mode of heartbeat can not deal with the dependency system of systemd and will never support it. Unfortunately I also do not have the logs from IRC anymore and no time until the next freeze step to provide this setup again :/ I still think, this is the best solution (since only v1 mode is affected): "IMO the package should warn (debconf dialog prio high?) the user if he upgrades heartbeat and systemd+v1 config is in use." Removing the whole heartbeat package would not be a good solution, since it is still required? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#818961: [Debian-ha-maintainers] Freeze status, Heartbeat plans
Am 21.12.2016 um 13:27 schrieb Valentin Vidic: > On Wed, Dec 21, 2016 at 01:15:12PM +0100, Patrick Matthäi wrote: >> We tried out many test cases, workarounds, debugging on this issue and >> the result was, that the v1 mode of heartbeat can not deal with the >> dependency system of systemd and will never support it. > Not sure what could be the problem with systemd dependencies. > Do you remember which services were involved so we can do a > quick test? > DRBD+lvm+ext4, apache and mariadb should be enough -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#818961: [Debian-ha-maintainers] Freeze status, Heartbeat plans
Am 21.12.2016 um 15:19 schrieb Christoph Berg: > Re: Patrick Matthäi 2016-12-21 > <89f2fc7d-a3a0-a01f-8105-7f795b0d2...@debian.org> >> We tried out many test cases, workarounds, debugging on this issue and >> the result was, that the v1 mode of heartbeat can not deal with the >> dependency system of systemd and will never support it. > Hmm, I don't get what the dependency system has to do with it, versus > a plain "heartbeat invoking systemctl via init scripts" breakage, or > something like that. > >> I still think, this is the best solution (since only v1 mode is affected): >> "IMO the package should warn (debconf dialog prio high?) the user if he >> upgrades heartbeat and systemd+v1 config is in use." > That still requires someone to understand the problem and explain it > in the warning. Just saying "it might be broken but we don't know > which bits you need to check" won't work. Simple service/host failovers will not work. the system will mostly stay in a not working state. Dont ask me too much now, sorry just came back from vacation and now I do not have the time to re-setup and debug everything again. Maybe someone else saved the irc logs (just search for the-me in the debian-ha channel on oftc) > >> Removing the whole heartbeat package would not be a good solution, since >> it is still required? > It doesn't have any reverse dependencies anymore. At the moment it's > the only HA package not in testing, so it isn't holding back any other > package. Effectively, it is already removed now (from testing). > > Christoph -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#830898: Please package extensions (like irssi-scripts)
Hi Am 12.07.2016 um 21:02 schrieb martin f krafft: > Package: znc > Version: 1.6.2-2 > Severity: wishlist > > Would you consider packaging up some of the most common extensions > to znc, like znc-extras used to provide? Not sure why that package > was removed… Sorry for my late answer. What modules are you missing? All modules (except of language modules like Perl, Tcl etc) are direct packaged in the znc main package. For 1.6.3 this is currently the case: -rw-r--r-- root/root 55304 2016-10-27 11:10 ./usr/lib/znc/adminlog.so -rw-r--r-- root/root 67600 2016-10-27 11:10 ./usr/lib/znc/alias.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/autoattach.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/autocycle.so -rw-r--r-- root/root 88072 2016-10-27 11:10 ./usr/lib/znc/autoop.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/autoreply.so -rw-r--r-- root/root 59400 2016-10-27 11:10 ./usr/lib/znc/autovoice.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/awaynick.so -rw-r--r-- root/root 63496 2016-10-27 11:10 ./usr/lib/znc/awaystore.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/block_motd.so -rw-r--r-- root/root 51208 2016-10-27 11:10 ./usr/lib/znc/blockuser.so -rw-r--r-- root/root100360 2016-10-27 11:10 ./usr/lib/znc/bouncedcc.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/buffextras.so -rw-r--r-- root/root 30728 2016-10-27 11:10 ./usr/lib/znc/cert.so -rw-r--r-- root/root 55304 2016-10-27 11:10 ./usr/lib/znc/certauth.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/chansaver.so -rw-r--r-- root/root 26632 2016-10-27 11:10 ./usr/lib/znc/clearbufferonmsg.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/clientnotify.so -rw-r--r-- root/root174816 2016-10-27 11:10 ./usr/lib/znc/controlpanel.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/crypt.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/ctcpflood.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/cyrusauth.so -rw-r--r-- root/root 88072 2016-10-27 11:10 ./usr/lib/znc/dcc.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/disconkick.so -rw-r--r-- root/root 30728 2016-10-27 11:10 ./usr/lib/znc/fail2ban.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/flooddetach.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/identfile.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/imapauth.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/keepnick.so -rw-r--r-- root/root 30728 2016-10-27 11:10 ./usr/lib/znc/kickrejoin.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/lastseen.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/listsockets.so -rw-r--r-- root/root 71688 2016-10-27 11:10 ./usr/lib/znc/log.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/missingmotd.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/modules_online.so -rw-r--r-- root/root 34824 2016-10-27 11:10 ./usr/lib/znc/nickserv.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/notes.so -rw-r--r-- root/root 26632 2016-10-27 11:10 ./usr/lib/znc/notify_connect.so -rw-r--r-- root/root 92168 2016-10-27 11:10 ./usr/lib/znc/partyline.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/perform.so -rw-r--r-- root/root 88072 2016-10-27 11:10 ./usr/lib/znc/q.so -rw-r--r-- root/root 22536 2016-10-27 11:10 ./usr/lib/znc/raw.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/route_replies.so -rw-r--r-- root/root 63496 2016-10-27 11:10 ./usr/lib/znc/sample.so -rw-r--r-- root/root 51208 2016-10-27 11:10 ./usr/lib/znc/sasl.so -rw-r--r-- root/root 59400 2016-10-27 11:10 ./usr/lib/znc/savebuff.so -rw-r--r-- root/root 79880 2016-10-27 11:10 ./usr/lib/znc/schat.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/send_raw.so -rw-r--r-- root/root 43016 2016-10-27 11:10 ./usr/lib/znc/shell.so -rw-r--r-- root/root 38920 2016-10-27 11:10 ./usr/lib/znc/simple_away.so -rw-r--r-- root/root 47112 2016-10-27 11:10 ./usr/lib/znc/stickychan.so -rw-r--r-- root/root 92168 2016-10-27 11:10 ./usr/lib/znc/watch.so -rw-r--r-- root/root231432 2016-10-27 11:10 ./usr/lib/znc/webadmin.so -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#843091: otrs2: CVE-2016-9139
Am 03.11.2016 um 19:48 schrieb Salvatore Bonaccorso: > Source: otrs2 > Version: 3.3.9-1 > Severity: important > Tags: security upstream fixed-upstream > > Hi, > > the following vulnerability was published for otrs2. > > CVE-2016-9139[0]: > |An attacker could trick an authenticated agent or customer into opening > |a malicious attachment which could lead to the execution of JavaScript > |in OTRS context > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2016-9139 > [1] https://www.otrs.com/security-advisory-2016-02-security-update-otrs/ > > Please adjust the affected versions in the BTS as needed. > Hi, yeah already saw it and stable is affected also. Upstream says the severity is low and I also would say IMHO that this is no candidate for a jessie security update. What do you think?
Bug#827339: Please revert patch for cmd, and fix default pattern
Am 17.11.2016 um 18:52 schrieb Stephan Sürken: > Hi Patrick, > > On Do, 2016-11-17 at 15:40 +0100, Patrick Matthäi wrote: > (...) >> Then the question is, why it does not work on Jessies grep? > did you overlook my comment? Or are my findings wrong? > > Thx! > > S Ah now I get it. You have adjusted the C code of apt-dater, to detect errors without using HTML. But we have got still the problem, that the default grep syntax (also your fixed grep syntax) from "typescript" produces a more or less silent "syntax error", like from the beginning of this report. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#827339: Please revert patch for cmd, and fix default pattern
Am 18.11.2016 um 17:51 schrieb Stephan Sürken: > Hi, > > On Fr, 2016-11-18 at 17:01 +0100, Patrick Matthäi wrote: >> Am 17.11.2016 um 18:52 schrieb Stephan Sürken: >>> Hi Patrick, >>> >>> On Do, 2016-11-17 at 15:40 +0100, Patrick Matthäi wrote: >>> (...) >>>> Then the question is, why it does not work on Jessies grep? >>> did you overlook my comment? Or are my findings wrong? >>> >>> Thx! >>> >>> S >> Ah now I get it. You have adjusted the C code of apt-dater, to detect >> errors without using HTML. > not quite. I rather fixed the default pattern being used when the user > does not configure one. > >> But we have got still the problem, that the default grep syntax (also >> your fixed grep syntax) from "typescript" produces a more or less >> silent >> "syntax error", like from the beginning of this report. > afaict, my patch just fixes each and every aspect of this bug report > ;). > > Hth, > > S Ok so adding patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827339#34 and drop current patch 01-grep-syntax-error ? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#827339: Please revert patch for cmd, and fix default pattern
Am 21.11.2016 um 11:49 schrieb Stephan Sürken: > Hi Patrick, > > On Mo, 2016-11-21 at 10:12 +0100, Patrick Matthäi wrote: > > (...) > >>> S >> Ok so adding patch >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827339#34 and drop >> current patch 01-grep-syntax-error ? > sure, that would be my suggestion. > > For your Debian patch, you should maybe only use the "entity fixes" of > my patch (not the additions to the regex of my personal liking which > are also in there ;). > > @Thomas: > > Of course upstream should fix this too, eventually. > > Thx! > > S Thanks for your effort! I have just uploaded 1.0.3-3. Would you (Stephan) be so kindly and upload it to jessie-bpo, if there are no new problems with it? I will be on vacation before it may enter testing. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#849752: lintian: dpkg-source failed with status 2 / no such file or directory
Package: lintian Version: 2.5.49 Severity: normal Hi, with both versions of lintian on jessie/jessie-backports (I think since a stable update of jessie itself) I get an error on checking most of my packages: # export LINTIAN_DEBUG=1; lintian -IE --pedantic /var/cache/pbuilder/result/ckport*.changes warning: the authors of lintian do not recommend running it with root privileges! N: Using dpkg-source to unpack ckport cp: cannot stat '/tmp/temp-lintian-lab-icMThgdBt5/pool/c/ckport/ckport_0.1~rc1-6_source/ckport_0.1~rc1.orig.tar.gz': No such file or directory dpkg-source: error: cp /tmp/temp-lintian-lab-icMThgdBt5/pool/c/ckport/ckport_0.1~rc1-6_source/ckport_0.1~rc1.orig.tar.gz to /tmp/temp-lintian-lab-icMThgdBt5/pool/c/ckport/ckport_0.1~rc1-6_source/ckport_0.1~rc1.orig.tar.gz gave error exit status 1 internal error: dpkg-source -x failed with status 2 at /usr/share/lintian/collection/unpacked line 71. warning: collect info unpacked about package ckport failed warning: skipping check of source package ckport So to reproduce it, here it is eg enough to: dget http://httpredir.debian.org/debian/pool/main/c/ckport/ckport_0.1~rc1-6.dsc pbuilder --build ckport_0.1~rc1-6.dsc lintian ckport_0.1~rc1-6_amd64.changes My /tmp is also correct: root@srv1:/tmp# ls -ld /tmp drwxrwxrwt 9 root root 4096 Dez 30 15:50 /tmp root@srv1:/tmp# ls -ld `mktemp -d` drwx-- 2 root root 4096 Dez 30 15:51 /tmp/tmp.XfY9dkVIVz -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.25-5 ii bzip2 1.0.6-7+b3 ii diffstat 1.58-1 ii file 1:5.22+15-2+deb8u2 ii gettext0.19.3-2 ii intltool-debian0.35.0+20060710.1 ii libapt-pkg-perl0.1.29+b2 ii libarchive-zip-perl1.39-1 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.37-1+b1 ii libdpkg-perl 1.17.27 ii libemail-valid-perl1.195-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.33-2+b1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii libtext-levenshtein-perl 0.11-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.64-1 ii libyaml-libyaml-perl 0.41-6 ii man-db 2.7.0.2-5 ii patchutils 0.3.3-1 ii perl [libdigest-sha-perl] 5.20.2-3+deb8u6 ii t1utils1.38-4 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages lintian recommends: ii dpkg1.17.27 ii libperlio-gzip-perl 0.18-3+b1 ii perl5.20.2-3+deb8u6 ii perl-modules [libautodie-perl] 5.20.2-3+deb8u6 Versions of packages lintian suggests: ii binutils-multiarch 2.25-5 ii dpkg-dev 1.17.27 ii libhtml-parser-perl3.71-1+b3 ii libtext-template-perl 1.46-1 -- no debconf information
Bug#825291: Processed (with 1 error): Re: Bug#825291: otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"
Hi, it is still unreproducable for upstream and me, except of your test environment. So I think there is the fault Am 09.06.2016 um 13:51 schrieb Debian Bug Tracking System: > Processing commands for cont...@bugs.debian.org: > >> tag #825291 + moreinfo > Bug #825291 [otrs2] otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: > DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8" > Ignoring request to alter tags of bug #825291 to the same tags previously set >> severity #825291 important > Bug #825291 [otrs2] otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: > DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8" > Severity set to 'important' from 'serious' >> tag #825291 + unreproduceable > Unknown tag/s: unreproduceable. > Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid > help security upstream pending sarge sarge-ignore experimental d-i confirmed > ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore > lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie > jessie-ignore stretch stretch-ignore buster buster-ignore. > > Bug #825291 [otrs2] otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: > DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8" > Requested to add no tags; doing nothing. >> thanks > Stopping processing here. > > Please contact me if you need assistance. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#836181: otrs2: var/httpd/htdocs/js/thirdparty/nvd3-1.7.1/nvd3.min.js is not a source file
merge #695664 #836181 thanks Am 31.08.2016 um 11:30 schrieb W. Martin Borgert: > Source: otrs2 > Version: 5.0.12-1 > > nvd3.min.js is a minified JS file, not source. > > Even if it were not minified, it still would not be source, > because NVD3 has multiple source files, aggregated by a tool > (grunt) to a single JS file. Known, but there is still nobody with javascript experience, who wants to help/maintain it with me. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#836823: jessie-pu: package glusterfs/3.5.2-2+deb8u2
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hello,
I want to upload glusterfs 3.5.2-2+deb8u3, could I go ahead?
diff:
diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u2/debian/changelog
branches/jessie/debian/changelog
--- tags/3.5.2-2+deb8u2/debian/changelog2016-05-27 15:14:36.603900286
+0200
+++ branches/jessie/debian/changelog2016-09-06 11:17:26.419773790 +0200
@@ -1,3 +1,11 @@
+glusterfs (3.5.2-2+deb8u3) jessie-proposed-updates; urgency=medium
+
+ * quota: Fix could not start auxiliary mount issue by adding upstream patch
+03-quota-fix-could-not-start-auxiliary-mount-issue.
+Closes: #825834
+
+ -- Patrick Matthäi Tue, 06 Sep 2016 11:17:19 +0200
+
glusterfs (3.5.2-2+deb8u2) jessie-proposed-updates; urgency=medium
* Add missing glusterd hook script to glusterfs-server package.
diff -Naur '--exclude=.svn'
tags/3.5.2-2+deb8u2/debian/patches/03-quota-fix-could-not-start-auxiliary-mount-issue.diff
branches/jessie/debian/patches/03-quota-fix-could-not-start-auxiliary-mount-issue.diff
---
tags/3.5.2-2+deb8u2/debian/patches/03-quota-fix-could-not-start-auxiliary-mount-issue.diff
1970-01-01 01:00:00.0 +0100
+++
branches/jessie/debian/patches/03-quota-fix-could-not-start-auxiliary-mount-issue.diff
2016-09-06 11:15:30.760415715 +0200
@@ -0,0 +1,37 @@
+From e61a2171f2389ec6cf1be962b68609c2e763cbd9 Mon Sep 17 00:00:00 2001
+From: Manikandan Selvaganesh
+Date: Mon, 11 Jan 2016 18:08:27 +0530
+Subject: [PATCH] quota : fix could not start auxiliary mount issue
+
+In versions older than 3.7, when trying to enable
+quota, the following message appears :"quota: Could
+not start quota auxiliary mount". It was because,
+/var/run/gluster was not getting created in cli side.
+In 3.7, the code has been moved to glusterd and we are
+making use of sys_mkdir.
+
+3.6 fix -> http://review.gluster.org/#/c/13308/
+
+
+Change-Id: Id4360409f76b57c0f676fe2b859f3647c4340575
+BUG: 1117888
+Signed-off-by: Manikandan Selvaganesh
+Reviewed-on: http://review.gluster.org/13215
+Smoke: Gluster Build System
+CentOS-regression: Gluster Build System
+NetBSD-regression: NetBSD Build System
+Reviewed-by: Niels de Vos
+Reviewed-by: Vijaikumar Mallikarjuna
+---
+
+--- a/cli/src/cli-cmd-volume.c
b/cli/src/cli-cmd-volume.c
+@@ -1029,7 +1029,7 @@ gf_cli_create_auxiliary_mount (char *vol
+ }
+
+ GLUSTERD_GET_QUOTA_AUX_MOUNT_PATH (mountdir, volname, "/");
+-ret = mkdir (mountdir, 0777);
++ret = mkdir_p (mountdir, 0700, _gf_true);
+ if (ret && errno != EEXIST) {
+ gf_log ("cli", GF_LOG_ERROR, "Failed to create auxiliary
mount "
+ "directory %s. Reason : %s", mountdir,
diff -Naur '--exclude=.svn' tags/3.5.2-2+deb8u2/debian/patches/series
branches/jessie/debian/patches/series
--- tags/3.5.2-2+deb8u2/debian/patches/series 2016-05-27 15:14:36.623900149
+0200
+++ branches/jessie/debian/patches/series 2016-09-06 11:15:16.372495549
+0200
@@ -1,2 +1,3 @@
01-CVE-2014-3619.diff
02-nfs-unix-domain-socket-created-as-fifo.diff
+03-quota-fix-could-not-start-auxiliary-mount-issue.diff
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#833111: otrs2: use init system for starting otrs.Daemon.pl / needrestart
Am 01.08.2016 um 02:48 schrieb Sven Strickroth: > Package: otrs2 > Version: 5.0.10-1~bpo8+1 > Severity: minor > > Dear Maintainer, > > right now the OTRS daemon (otrs.Daemon.pl) is started using cron. This leads > to restarting issues in combination with the needrestart tool which says that > cron needs to be restarted after perl (security) updates, but restarting it > doesn't help as otrs.Daemon.pl is not restarted. Only killing otrs.Daemon.pl > manually solves the issue and makes sure that the daemon is restarted. I think in this case it is better to blacklist otrs.Daemon.pl in needrestart. What do you say Thomas? > > Therefore, why not use the initsystem for starting/stopping the ORTS > daemon? That is not wanted by upstream. Cron is the recommend usage to ensure, that it gets automatic restarted in every setup, if something fails at the daemon. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
