Bug#897436: broken nautilus integration

Package: nautilus-owncloud Version: 2.4.1+dfsg-1 Severity: serious I can't pinpoint it to an exact update, but I noticed that the owncloud/nextcloud nautilus integration no longer works. When I start nautilus from the command line, I get: $ nautilus sys:1: PyGIWarning: Nautilus was imported

Bug#862757: dnssec-trigger 0.15 release

Hi Diane Am 02.05.2018 um 07:17 schrieb Diane Trout: > Should I release this version or wait for what Michael did? You don't have to wait for me. I provided a patch for the issue for the maintainer to review and apply. I did not / do not intend to NMU this package. Regards, Michael -- Why is

Bug#896783: python-slip: missing build dependency on python3-distutils

Am 24.04.2018 um 11:35 schrieb Adrian Bunk: > Source: python-slip > Version: 0.6.5-2 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-slip.html > > ... > cd /build/1st/python-slip-0.6.5; \ > /usr/bin/python3 setup.py build > Traceback (most recent

Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs

Am 23.04.2018 um 14:12 schrieb Simon McVittie: > Control: tags -1 + moreinfo unreproducible > > On Mon, 23 Apr 2018 at 13:02:26 +0200, Vincent Lefevre wrote: >> On 2018-04-18 14:43:47 -0400, rektide de la faye wrote: >>> I recently updated a number of packages on my Debian/testing laptop, >>> via

Bug#896494: FTBFS: test-suite failures

Source: libqtdbusmock Version: 0.7+bzr49+repack1-2 Severity: serious Hi, libqtdbusmock fails to pass its test-suite, resulting in a FTBFS: https://buildd.debian.org/status/package.php?p=libqtdbusmock /usr/bin/ctest --force-new-ctest-process -j4 Test project

Bug#896258: [Pkg-utopia-maintainers] Bug#896258: python3-bytesize: bytesize fails to import

Am 20.04.2018 um 22:01 schrieb Helmut Grohne: > Package: python3-bytesize > Version: 1.2-2 > Severity: serious > User: helm...@debian.org > Usertags: python-import > > After installing python3-bytesize importing the module bytesize > into a python interpreter fails with the following error: > >

Bug#896303: [Pkg-utopia-maintainers] Bug#896303: python3-blockdev: gi.overrides.BlockDev fails to import

Control: tags -1 + moreinfo Am 20.04.2018 um 22:01 schrieb Helmut Grohne: > Package: python3-blockdev > Version: 2.16-2 > Severity: serious > User: helm...@debian.org > Usertags: python-import > > After installing python3-blockdev importing the module gi.overrides.BlockDev > into a python

Bug#896198: python3-slip-dbus: slip.dbus fails to import

Control: tags -1 + moreinfo Am 20.04.2018 um 22:01 schrieb Helmut Grohne: > Package: python3-slip-dbus > Version: 0.6.5-2 > Severity: serious > User: helm...@debian.org > Usertags: python-import > > After installing python3-slip-dbus importing the module slip.dbus > into a python interpreter

Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

Am 19.04.2018 um 16:02 schrieb Michael Biebl: > Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System: >> sugar (0.112-4) unstable; urgency=medium >> . >>* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230) > > Hm, you dropped the dependency, but I d

Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System: > sugar (0.112-4) unstable; urgency=medium > . >* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230) Hm, you dropped the dependency, but I don't think this is actually a proper fix, as I still see this in the code: $ grep import

Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs

Am 18.04.2018 um 20:43 schrieb rektide de la faye: > Package: libglib2.0-0 > Version: 2.56.1-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I recently updated a number of packages on my Debian/testing laptop, via > aptitude > and included in that upgrade

Bug#862883: Port from libnm-glib/libnm-util to libnm

Am 18.04.2018 um 19:55 schrieb Pino Toscano: > In data mercoledì 18 aprile 2018 19:35:01 CEST, Michael Biebl ha scritto: >> Control: tags -1 + patch >> >> I made some more minor tweaks to v2: >> >> - Update debian/changelog >> - Drop debian/patches/add_gl

Bug#862877: Port from libnm-glib/libnm-util to libnm

Hi Pino Am 18.04.2018 um 19:50 schrieb Pino Toscano: > In data mercoledì 18 aprile 2018 19:01:53 CEST, Michael Biebl ha scritto: >> Control: tags -1 + patch >> >> Attached is a debdiff which is based on lubo's patch. >> >> Changes to the initial patch >>

Bug#862678: Switch from network-manager-dev to libnm-dev

Hi Ari, did you find some time to look into this? Anything I can help you with? Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature

Bug#862883: Port from libnm-glib/libnm-util to libnm

+ + * Non-maintainer upload. + * Update solid-networkstatus to use libnm. (Closes: #862883) + * Drop debian/patches/add_glib_for_nm, no longer necessary with the above +changes. + + -- Michael Biebl <bi...@debian.org> Sat, 14 Apr 2018 13:02:04 + + kde-runtime (4:17.08.3-1) unstable; u

Bug#862877: Port from libnm-glib/libnm-util to libnm

-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Port networkmanagerstatus to libnm. (Closes: #862877) + + -- Michael Biebl <bi...@debian.org> Wed, 18 Apr 2018 18:35:20 +0200 + kdelibs4support (5.44.0-2) sid; urgency=medium * New revision diff -Nru kdelibs4support-

Bug#862883: Port from libnm-glib/libnm-util to libnm

On Sat, 14 Apr 2018 21:32:30 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 14.04.2018 um 15:21 schrieb Michael Biebl: > > > I tried updating solid-networkstartus to use QT_NO_KEYWORDS and the Q_ > > macros, but ran into a problem. The QNtrack headers use the slots

Bug#895444: [Pkg-ayatana-devel] Bug#895444: Bug#895444: Uses deprecated NetworkManager.pc

Am 16.04.2018 um 11:32 schrieb Mike Gabriel: > Hi Michael, > > On  Sa 14 Apr 2018 20:58:01 CEST, Mike Gabriel wrote: > >> Hi, >> >> On  Sa 14 Apr 2018 01:04:15 CEST, Michael Biebl wrote: >> >>> Control: severity -1 serious >>> >>>

Bug#862883: Port from libnm-glib/libnm-util to libnm

Am 14.04.2018 um 15:21 schrieb Michael Biebl: > I tried updating solid-networkstartus to use QT_NO_KEYWORDS and the Q_ > macros, but ran into a problem. The QNtrack headers use the slots > keyword, so if I set -DQT_NO_KEYWORDS, > solid-networkstatus/kded/ntracknetworkstate.cpp fail

Bug#862883: Port from libnm-glib/libnm-util to libnm

Am 14.04.2018 um 14:07 schrieb Michael Biebl: > Am 14.04.2018 um 14:01 schrieb Michael Biebl: >> On Wed, 20 Dec 2017 09:58:16 +0100 Lubomir Rintel <lkund...@v3.sk> wrote: >>> This doesn't seem to build with current libnm and glib, perhaps because >>> &q

Bug#862883: Port from libnm-glib/libnm-util to libnm

Am 14.04.2018 um 14:01 schrieb Michael Biebl: > On Wed, 20 Dec 2017 09:58:16 +0100 Lubomir Rintel <lkund...@v3.sk> wrote: >> This doesn't seem to build with current libnm and glib, perhaps because >> "signals" is a reserved word in MOC? > > That said, I'm not

Bug#862883: Port from libnm-glib/libnm-util to libnm

On Wed, 20 Dec 2017 09:58:16 +0100 Lubomir Rintel wrote: > This doesn't seem to build with current libnm and glib, perhaps because > "signals" is a reserved word in MOC? > > Build log: > > In file included from /usr/include/qt4/QtCore/qobject.h:47:0, > >

Bug#862884: Disable libnm-glib support

Hi Mike Am 14.04.2018 um 09:45 schrieb Mike Miller: > On Sat, Apr 14, 2018 at 01:02:45 +0200, Michael Biebl wrote: >> I intend to upload a new version of network-manager soonish which will >> drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in >> preparation

Bug#895446: Error in startup script: bad screen distance "4.5"

Package: gitk Version: 1:2.17.0-1 Severity: grave gitk no longer successfully starts here. When I run it from a terminal, I get $ gitk Error in startup script: bad screen distance "4.5" while executing "$canv conf -scrollregion [list 0 0 $canvxmax $ymax]" (procedure "setcanvscroll" line

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Am 04.04.2018 um 21:27 schrieb Axel Beckert: >> As soon as you clean up the stray >> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the >> problem should go away? > > No, because there's also a symlink to it which (according to the > timestamp) seem to have been created by

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Am 04.04.2018 um 21:06 schrieb Michael Biebl: > Am 04.04.2018 um 20:20 schrieb Axel Beckert: >> Hi, >> >> Simon McVittie wrote: >>>> This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ >>>> that shouldn't be there, and this takes

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Am 04.04.2018 um 20:20 schrieb Axel Beckert: > Hi, > > Simon McVittie wrote: >>> This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ >>> that shouldn't be there, and this takes precedence over the more recent >>> one from the Debian package that gets installed to /usr/lib.

Bug#893783: spyder3: does not start even after --reset

On Thu, 22 Mar 2018 10:47:17 + Jitse Niesen wrote: > I don't know the root cause, but it seems to be an incompatibility > between python-tornado and pyzmq and possibly jupyter-client, caused by > a change in tornado version 5. Maybe pyzmq needs to be at least version

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: tags -1 fixed-upstream patch Control: forwarded -1 https://github.com/systemd/systemd/pull/8456 Fixed upstream by https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130 -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: > No I don't think I have one > dpkg -l udev only shows udev and64 what about systemd? i386 or amd64 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description:

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > Looks like commenting out > > SystemCallArchitectures=native > > fixes  the issue. Does that mean you have a udev:i386 installed on a amd64 system? If so, that would basically be a duplicate of #869719 -- Why is it that all of the

Bug#893426: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: reassign -1 systemd Control: found -1 238-1 It was correctly pointed out by Andreas Henriksson, that redefining noreturn is probably not such a good idea, so let's reassign this back. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: reassign -1 libgpg-error-dev Control: found -1 1.28-1 Control: affects -1 + systemd Am 18.03.2018 um 19:54 schrieb Helmut Grohne: > Package: systemd > Version: 238-2 > Severity: serious > User: helm...@debian.org > Usertags: rebootstrap > > systemd fails to build from source on amd64.

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: > Package: systemd > Version: 238-2 > Followup-For: Bug #893369 > > It didn't work so I just added the options in /etc/default/grub. > Here are the journal and the systemctl list-jobs output (which is just "no > jobs"). > Ok, thanks. Once you are

Bug#893402: Uses deprecated llvm3.9

Am 18.03.2018 um 19:13 schrieb Lisandro Damián Nicanor Pérez Meyer: > El 18 mar. 2018 2:39 p.m., "Michael Biebl" <bi...@debian.org > <mailto:bi...@debian.org>> escribió: > > Am 18.03.2018 um 18:33 schrieb Michael Biebl: > > Source: qtcreator &

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > I'll do all that, thanks. Do you know how I can set a correct keymap in > the grub "e" text editor ? I don't. But this is literally the first google hit regarding that question

Bug#893402: Uses deprecated llvm3.9

Am 18.03.2018 um 18:33 schrieb Michael Biebl: > Source: qtcreator > Version: 4.5.2-2 > Severity: serious > > llvm 3.9 is deprecated and in the process of being removed for stretch, > see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408 Sorry, wrong C, I meant thi

Bug#893402: Uses deprecated llvm3.9

Source: qtcreator Version: 4.5.2-2 Severity: serious llvm 3.9 is deprecated and in the process of being removed for stretch, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408 Please update your package to use the latest, recommended version which is llvm6.0. Thanks, Michael --

Bug#893369: systemd-udevd is killed at startup

On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= wrote: > Package: systemd > Version: 238-2 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > After an update and a restart of the system, boot fails. It enters a loop, >

Bug#892738: consolekit: consolekit removal causes a regression

Am 18.03.2018 um 01:03 schrieb Michael Biebl: > Am 17.03.2018 um 18:33 schrieb Benedikt Spranger: >> On Sat, 17 Mar 2018 03:02:19 +0100 >> Michael Biebl <bi...@debian.org> wrote: >> >>> On Mon, 12 Mar 2018 12:51:35 +0100 Benedikt Spranger >>> &

Bug#892738: consolekit: consolekit removal causes a regression

Am 17.03.2018 um 18:33 schrieb Benedikt Spranger: > On Sat, 17 Mar 2018 03:02:19 +0100 > Michael Biebl <bi...@debian.org> wrote: > >> On Mon, 12 Mar 2018 12:51:35 +0100 Benedikt Spranger >> <b.spran...@linutronix.de> wrote: >>> Package: consolekit

Bug#892738: consolekit: consolekit removal causes a regression

On Mon, 12 Mar 2018 12:51:35 +0100 Benedikt Spranger wrote: > Package: consolekit > Version: 0.4.6-6 > Severity: serious > > Dear Maintainer, > > please readd consolekit to the archive. Without consolekit the > dependency to libpam-systemd as alternative to consolekit

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 18:31 schrieb Elimar Riesebieter: > * Michael Biebl <bi...@debian.org> [2018-03-08 17:09 +0100]: > >> Am 08.03.2018 um 17:05 schrieb Michael Biebl: >>> Control: tags -1 moreinfo >>> >>> Am 08.03.2018 um 16:23 schrieb valette:

Bug#892360: systemd pid 1 freezes at startup on x86 systems

Am 08.03.2018 um 18:27 schrieb Elimar Riesebieter: > * Michael Biebl <em...@michaelbiebl.de> [2018-03-08 17:05 +0100]: > >> Control: tags -1 moreinfo >> >> Am 08.03.2018 um 16:23 schrieb valette: >> >>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMP

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:09 schrieb Michael Biebl: > Could you check if > https://github.com/systemd/systemd/issues/8387 > looks related > > I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem. If not, follow the instructions at https://freedesktop.org/wiki/S

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:05 schrieb Michael Biebl: > Control: tags -1 moreinfo > > Am 08.03.2018 um 16:23 schrieb valette: > >> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) > > Is this also happening with a Debian provided kernel? > I see both you

Bug#892360: systemd: Breaks also all my tested amd64 machines

Control: tags -1 moreinfo Am 08.03.2018 um 16:23 schrieb valette: > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) Is this also happening with a Debian provided kernel? I see both you and Elimar use a custom one. Is this a virtualized environment or read hardware? Do you get a coredump? If

Bug#891413: [Pkg-utopia-maintainers] Bug#891413: network-manager-pptp: PPTP connections fail on Authentication

Control: affects -1 + network-manager-pptp Am 25.02.2018 um 22:01 schrieb Chris Boot: > Control: reassign -1 src:ppp > Control: tags -1 confirmed > Control: found -1 2.4.7-2+1~exp1 > Control: retitle -1 ppp: MS-CHAP authentication broken ... > Yes, it looks like it's an error on my part in >

Bug#891413: [Pkg-utopia-maintainers] Bug#891413: network-manager-pptp: PPTP connections fail on Authentication

Am 25.02.2018 um 12:30 schrieb Adam Hough: > Package: network-manager-pptp > Version: 1.2.4-5+b1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >    * What led up to the situation? > > I did a normal apt upgrade which updated network-manager-pptp, >

Bug#865043: Please drop Build-Depends on deprecated libck-connector-dev

On Sun, 18 Jun 2017 22:08:54 +0200 Michael Biebl <bi...@debian.org> wrote: > Source: lxdm > Version: 0.5.3-2 > Severity: normal > Tags: patch > > Hi, > > ConsoleKit is dead upstream since almost 4 years [1] and unmaintained in > Debian [2]. With logind a much be

Bug#888162: [pkg-cryptsetup-devel] Bug#888162: cryptsetup: `loopaesOpen --key-file=-` doesn't read the key from stdin but tries to open key file "./-"

Hi Guilhem, On Wed, 24 Jan 2018 14:38:50 +0100 Guilhem Moulin wrote: > On Wed, 24 Jan 2018 at 09:13:53 +0100, Milan Broz wrote: > > Fixed upstream in > > https://gitlab.com/cryptsetup/cryptsetup/commit/8728ba08e2e056a4c18b55407146eea7ac0043c6 > could you please release an

Bug#889144: systemd 237-1: problem starting dnsmasq

Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard: > Michael Biebl: > >> If other services depend on dnsmasq, please keep >> https://www.lucas-nussbaum.net/blog/?p=877 in mind >> > Please do not.  It is an erroneous conclusion based upon a faulty > analysi

Bug#889144: stricter PIDfile handling breaks several daemons

Am 04.02.2018 um 21:26 schrieb Sven Hartge: > On Sun, 4 Feb 2018 15:41:37 + Simon Kelley > wrote: > >> With my dnsmasq maintainer hat on, the current arrangement looks like this. >> >> 1) /run/dnsmasq is a directory owned by dnsmasq:nogroup >> 2)

Bug#878757: Openvswitch must started before networking servise

On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov wrote: > Package: openvswitch-switch > Version: 2.6.2~pre+git20161223-3 > Priority: critical > > The Openvswitch daemon must be started before the network.service. > Because when the initiation of the network started

Bug#889144: stricter PIDfile handling breaks several daemons

Am 03.02.2018 um 14:35 schrieb Sven Hartge: > Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl: >> The alternative afaics would be, that the daemon writes the pid file as >> munin:munin then (or ulog:ulog for the above case). > > No, this would open a potential DoS vector. &

Bug#889144: stricter PIDfile handling breaks several daemons

Control: forwarded -1 https://github.com/systemd/systemd/issues/8085 Hi Sven, I filed an upstream issue at https://github.com/systemd/systemd/issues/8085 trying to summarize what the issue is afaiu from reading this and related bug reports. If you have further feedback or corrections, please

Bug#889144: stricter PIDfile handling breaks several daemons

Am 03.02.2018 um 13:27 schrieb Sven Hartge: > Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl: > >> Am 02.02.2018 um 20:07 schrieb Sven Hartge: > >>> ulogd2 drops its priviliges on its own. It needs to start as root to >>> connect to the netlink sockets. > &g

Bug#889144: stricter PIDfile handling breaks several daemons

Am 02.02.2018 um 20:07 schrieb Sven Hartge: > ulogd2 drops its priviliges on its own. It needs to start as root to > connect to the netlink sockets. So, ulogd2 creates a directory /run/ulog which is owned by ulog:ulog but then creates the pid file /run/ulog/ulog.pid owned by root:root. I assume

Bug#888000: Port from deprecated libnm-glib bindings to libnm

Source: gnome-shell-extension-disconnect-wifi Version: 3.22.14-1 Severity: serious Tags: patch User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: libnm Hi, the libnm-glib/libnm-util libraries have been deprecated upstream in favour of libnm (along with their corresponding gir

Bug#887998: Port from deprecated libnm-glib bindings to libnm

Source: gnome-shell-extension-show-ip Version: 8-2 Severity: serious Tags: patch User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: libnm Hi, the libnm-glib/libnm-util libraries have been deprecated upstream in favour of libnm (along with their corresponding gir bindings) Your

Bug#887815: [Pkg-utopia-maintainers] Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

Control: reassign -1 network-manager Control: found -1 1.10.2-1 Control: affects -1 network-manager-iodine Hi Guido Am 20.01.2018 um 13:58 schrieb Michael Biebl: > Am 20.01.2018 um 12:09 schrieb Guido Günther: >> /usr/include/libnm/nm-setting-tc-config.h:43:1: error: '

Bug#887815: [Pkg-utopia-maintainers] Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

Am 20.01.2018 um 12:09 schrieb Guido Günther: > /usr/include/libnm/nm-setting-tc-config.h:43:1: error: 'NMTCQdisc' is > deprecated: Not available before 1.10.2 I suppose this is the problem in configure.ac LIBNM_CFLAGS="$LIBNM_CFLAGS -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2"

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

On Fri, 19 Jan 2018 02:24:35 +0100 Cyril Brulebois wrote: > Getting back to src:vte2.91 though, that's not sufficient, as the > resulting udeb depends (right now or after a rebuild against a patched > pcre2) on libstdc++6. We don't do c++ in d-i. That's going to be hard:

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

On Thu, 18 Jan 2018 19:11:36 -0500 Jeremy Bicha wrote: > Control: block -1 by 887674 > > On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois wrote: > > - vte2.91 needs to build an installable udeb; I think I've reported a > >few issues already, but I don't

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

Am 19.01.2018 um 03:02 schrieb Michael Biebl: > On Thu, 18 Jan 2018 19:11:36 -0500 Jeremy Bicha <jbi...@debian.org> wrote: >> Control: block -1 by 887674 >> >> On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois <k...@debian.org> wrote: >>> - vte2.91 needs

Bug#885525: /usr/bin/nm-applet: nm-applet crashes when connecting to VPN

Hi Sean Am 16.01.2018 um 06:33 schrieb Sean DuBois: > Mike, > I don't believe that part is needed, I did a full diff against upstream > and there is a g_strdup in both. If you do an apt-get source it does a > g_strdup by default. May be wrong though! > > What happens with not establishing the

Bug#867937: mate-power-manager: Build-Depends on deprecated libgnome-keyring-dev

Control: tags -1 + patch Am 15.01.2018 um 11:08 schrieb Mike Gabriel: > Please note that a fix is not yet being worked on on the MATE upstream > side and I expect a fix for this with MATE 1.20 at the earliest. In the mean time I would kindly ask you to disable the optional keyring functionality

Bug#886325: [Pkg-utopia-maintainers] Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

Am 04.01.2018 um 14:37 schrieb Alberto Brosich: > Package: dbus > Version: 1.10.24-0+deb9u1 > Severity: grave > Justification: renders package unusable > > I'm working on Debian stable. > > After a small update and a reboot, dbus daemon does not start with the > following message: > >

Bug#884784: systemd-network segfaults

Control: severity -1 important Control: tags -1 moreinfo Control: found -1 236-1 Control: notfound -1 235-3 Am 19.12.2017 um 18:50 schrieb Rémi Denis-Courmont: > Package: systemd > Version: 235-3 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > >

Bug#880883: Some findings about g_closure_ref()/g_closure_unref()

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=791706 Hi Punit, thanks a lot for your excellent work so far! On Sat, 2 Dec 2017 20:48:08 + Punit Agrawal wrote: > I have a few ideas on how to improve the code by re-factoring > INC_ASSIGN/DEC_ASSIGN

Bug#884048: gnome-shell: /usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with segfault

Control: severity -1 important > Dec 10 13:17:40 lavaine kernel: [ 3324.799650] gnome-shell-cal[2352]: > segfault at 10812 ip 7f2eeafd0324 sp 7ffd0bc3d6d0 error 4 in > libical.so.2.0.0[7f2eeaf8d000+5e000] To explain what's happening here: gnome-shell links directly against libical

Bug#884305: valgrind related tests fail on all architectures besides amd64/s390x

Source: rsyslog Version: 8.31.0-2 Severity: serious Forwarded: https://github.com/rsyslog/rsyslog/issues/2213 In the latest upload, I enabled the extended test suite which makes use of valgrind on all architectures which provide valgrind. This failed for all architectures aside amd64 and s390x:

Bug#884302: [Pkg-utopia-maintainers] Bug#884302: avahi-ui-utils: recommends virtual package (non-deterministic, potentially pulling in non-free package)

Control: severity -1 normal Am 13.12.2017 um 16:02 schrieb Jonas Smedegaard: > Package: avahi-ui-utils > Version: 0.7-3 > Severity: serious > Justification: Policy 2.2.1 > > avahi-ui-utils recommends vnc-viewer. > > vnc-viewer is a virtual package, which means it is not deterministic > which

Bug#883977: *** stack smashing detected ***: evolution terminated

On Sat, 09 Dec 2017 18:01:35 -0500 Joachim Breitner wrote: > Hi, > > rebuilding evolution fixes the problem for me. > > Maybe re-assign to evolution? That's most likely a result of the uncoordinated libical3 transition / NMU of evolution-data-server. Jeremy did sourceful

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Control: tags -1 moreinfo Control: severity -1 normal Am 08.12.2017 um 00:06 schrieb Duncan Hare: > browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw > 0 0 > tmpfs/tmptmpfs >

Bug#882055: Gedit breaks when writing to a file

Control: severity -1 normal Control: retitle -1 gedit aborts when writing to a file with setuid bit Am 25.11.2017 um 12:17 schrieb Narcis Garcia: > Sorry, I forgot to test with and without setuid bit: > > $ id -un > userA > $ echo "Content text" > file.txt > $ sudo chown userB file.txt > $ sudo

Bug#882055: Gedit breaks when writing to a file

Control: tags -1 moreinfo unreproducible On Thu, 23 Nov 2017 13:28:02 +0100 Narcis Garcia wrote: > Worked fine, with no error, on Gedit version 3.10 > > The problem seems to be, although text file is readable and writable to > owner & group & others, when saving from

Bug#881301: gnome-shell: segfault error 4 in libgobject-2.0.so.0.5400.2

Control: found -1 3.26.1-3 Am 14.11.2017 um 15:25 schrieb Lucas Dyer: > On Sun, 12 Nov 2017 at 15:09:17 +0100, Michael Biebl <bi...@debian.org> wrote: >> Is this a regression in 3.26.2-1 or can you reproduce the segfaults with >> 3.26.1-3 from testing as well? >

Bug#881301: gnome-shell: segfault error 4 in libgobject-2.0.so.0.5400.2

Am 09.11.2017 um 22:27 schrieb Lucas Dyer: > Package: gnome-shell > Version: 3.26.2-1 Is this a regression in 3.26.2-1 or can you reproduce the segfaults with 3.26.1-3 from testing as well? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from

Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

Am 05.11.2017 um 13:14 schrieb Michael Biebl: > Looking through past build logs, it consistently seems to fail at this > point: > > make[7]: Entering directory > '/<>/debian/build/deb/tests/refcount' > make closures objects objects2 properties properties2 propertie

Bug#881352: [Pkg-utopia-maintainers] Bug#881352: udisks2: Breaks installation with kernel panic

Am 10.11.2017 um 23:09 schrieb André Esteves: > Every time I do 'dpkg --configure -a' he starts by installing udisks2 > package it breaks and the kernel panics... Can you provide a more complete kernel log from around the crash -- Why is it that all of the instruments seeking intelligent life

Bug#881352: [Pkg-utopia-maintainers] Bug#881352: udisks2: Breaks installation with kernel panic

Am 10.11.2017 um 17:53 schrieb André Esteves: > Subject: udisks2: Breaks installation with kernel panic > Package: udisks2 > Version: 2.7.4-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > > What led up to the situation? > > Upgrading system tyhrough ssh

Bug#880982: ifup does not trigger scripts any more after booting

Control: reassign -1 ifupdown Am 06.11.2017 um 17:53 schrieb Narcis Garcia: > Package: udev > Version: 232-25+deb9u1 > Severity: serious > > Tested with updated Debian 9 (amd64): > > Interface is declared at /etc/network/interfaces : > auto enp2s0 > allow-hotplug enp2s0 > iface enp2s0 inet dhcp

Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

Looking through past build logs, it consistently seems to fail at this point: make[7]: Entering directory '/<>/debian/build/deb/tests/refcount' make closures objects objects2 properties properties2 properties3 properties4 signal1 signal2 signal3 signal4 \ make[8]: Entering directory

Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

Source: glib2.0 Version: 2.54.2-1 Severity: serious As can be seen at https://buildd.debian.org/status/logs.php?pkg=glib2.0=arm64 glib2.0 FTBFS on arm64 quite often. Looking through the build history, arm-arm-04 (and to a lesser extent arm-arm-01) seems to be much more susceptible to build

Bug#880703: test-suite failure on s390x

Source: json-glib Version: 1.4.2-1 Severity: serious Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/28 The test-suite fails on s390x: 1/14 array OK 0.01 s 2/14 boxed OK 0.01 s 3/14 builder

Bug#880702: test-suite failures on i386

Source: json-glib Version: 1.4.2-1 Severity: serious Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/27 The test-suite fails on i386: 1/14 array FAIL 0.01 s 2/14 boxed OK 0.01 s 3/14 builder

Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

Am 03.11.2017 um 17:25 schrieb Michael Biebl: > It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625 Let me rephrase that a little: I'm pretty sure it's the same underlying issue and it would be great if you can give the patch in the upstream bug tracker a try. --

Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789625 Control: tags -1 + patch Am 03.11.2017 um 16:36 schrieb Jeremy Bicha: > Control: severity -1 serious > > On Fri, Nov 3, 2017 at 11:25 AM, Theppitak Karoonboonyanan > wrote: >> Since Pango 1.40.13, Thai word

Bug#874621: screen lock cannot be unlocked in vnc session

Control: severity -1 important On Fri, 8 Sep 2017 12:22:37 +0530 Pirate Praveen wrote: > package: gnome-shell > version: 3.22.3-3 > severity: grave > justification: makes it unusable and it is a regression Downgrading to important as this certainly doesn't make gnome-shell

Bug#878411: gnome-session-bin doesn't set environmental variable of GTK_IM_MODULE

On Fri, 13 Oct 2017 21:37:35 +0900 Takahide Nojima wrote: > Package: gnome-session-bin > Version: 3.26.1-1 > Severity: serious > Tags: patch > > I updated gnome desktop from debian sid. However, I found I can not > type Japanese language anymore. > > I finally found

Bug#874526: Keyboard grab doesn't work under Wayland

On Sat, 14 Oct 2017 15:12:34 -0400 Jeremy Bicha wrote: > On Wed, Sep 6, 2017 at 5:58 PM, Josh Triplett wrote: > > The mechanism gnome-boxes uses to grab the keyboard doesn't work under > > the default GNOME Wayland session. This makes it impossible to

Bug#878911: avahi FTBFS with debhelper 10.9.2

On Tue, 17 Oct 2017 19:45:11 +0300 Adrian Bunk wrote: > Source: avahi > Version: 0.7-3 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avahi.html > > ... >dh_systemd_start > dh_systemd_start: Could not find "avahi-daemon.socket" in

Bug#879006: gnome-software FTBFS with fwupd 1.0.0-1

We probably need to cherry-pick this commit from master: https://git.gnome.org/browse/gnome-software/commit/?id=781c81721964e841fd35a0cd7a10c8ed51afa339 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description:

Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot

Bernhard, could you try to run a git bisect to find the relevant change which broke fsck for you. https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log/disk-utils/fsck.c?h=stable/v2.30 There aren't that many changes for fsck. -- Why is it that all of the instruments seeking

Bug#877672: [systemd] System Stalled at Pam-nologon

Control: severity -1 normal Due to lack of feedback I'm downgrading the severity to normal and will close the bug report in two weeks if no further information is provided. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#872635: util-linux: FTBFS on armel: test failure

Forwarding this bug report to the debian-arm porters list so not only Aurelien and Steve are aware of the issue. Would be great if you can take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872635 and help us find a solution. On Sat, 19 Aug 2017 17:10:13 +0200 Cyril Brulebois

Bug#878203: [pkg-apparmor] Bug#878203: Bug#878203: AA breaks libvirt when running with kernel 4.13

Am 11.10.2017 um 13:06 schrieb Christian Boltz: > I noticed one denial that probably isn't covered by the upstream profile > yet: > > apparmor="DENIED" operation="open" profile="libvirt-c6ae5f8d- > e017-484d-9176-96b0e079c66d" name="/proc/726/cmdline" pid=6188 > comm="qemu-system-x86"

Bug#878203: [pkg-apparmor] Bug#878203: AA breaks libvirt when running with kernel 4.13

Am 11.10.2017 um 04:35 schrieb Seth Arnold: > Hello Michael, do you still have the DENIED lines from your kernel logs > when experiencing this problem? If so please share them here. > > Thanks > attached is the output of "grep audit /var/log/kern.log" -- Why is it that all of the instruments

Bug#878203: AA breaks libvirt when running with kernel 4.13

Package: apparmor Version: 2.11.0-11 Severity: serious After the kernel upgrade from 4.12 to 4.13 my KVM/libvirt instances failed to start: Okt 10 19:24:44 pluto libvirtd[673]: 2017-10-10 17:24:44.404+: 797: error : virProcessRunInMountNamespace:1159 : internal error: child reported: Kernel

<    1   2   3   4   5   6   7   8   9   10   >