Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

On Mon, Dec 11, 2017 at 11:10:42PM +0100, Salvatore Bonaccorso wrote: > Hi Ben, > > On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote: > > On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote: > > > There were several commits interspersed with sched/topology fixes > > > upstream

Bug#884069: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

Tested on most important system (IBM BladeCenter HS22). It boots OK, but infiniband don't work (interface is up, but rdma - no): [ 147.690952] ko2iblnd: disagrees about version of symbol rdma_resolve_addr [ 147.690956] ko2iblnd: Unknown symbol rdma_resolve_addr (err -22) [ 147.691009]

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote: > [This message is bcc'd to all bug reporters.] > > Apologies for this regression. Salvatore Bonaccorso has tracked down > which change in 3.16-stable triggers the crash, and I identified some > related upstream

Bug#872533: marked as done (node-chai FTBFS with nodejs 6.11.2)

Your message dated Tue, 12 Dec 2017 05:34:41 + with message-id and subject line Bug#872533: fixed in node-chai 4.1.2+dfsg-1 has caused the Debian Bug report #872533, regarding node-chai FTBFS with nodejs 6.11.2 to be marked as done. This means that you

Bug#851086: [Pkg-citadel-devel] Bug#859789: RFH: citadel/webcit

On 2017-12-11 7:42 AM, Michael Meskes wrote: Anyone interested in citadel/webcit? If not I'm going to have it removed I guess. There used to be a team maintaining these packages, but I'm the only one who worked on it in recent years. Not having used the software myself I don't really intend

Bug#883613: marked as done (pocl 0.14 test failures on i386)

Your message dated Tue, 12 Dec 2017 03:19:03 + with message-id and subject line Bug#883613: fixed in pocl 0.14-1 has caused the Debian Bug report #883613, regarding pocl 0.14 test failures on i386 to be marked as done. This means that you claim that the

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

[This message is bcc'd to all bug reporters.] Apologies for this regression. Salvatore Bonaccorso has tracked down which change in 3.16-stable triggers the crash, and I identified some related upstream changes which appear to fix it. An updated package is available at:

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

Source: linux Version: 4.9.0-4 Followup-For: Bug #884116 I've got the same error after upgrading from 4.9.0-3 to the newer kernel. I could provide information if required -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

On 2017-12-11 21:34, Luca Boccassi wrote: > BTW I've been running the packages built from 384-stretch-backports on > my desktop and I haven't encountered issues. Thanks for testing :-) I think I'll wait until 384 is in testing for a good week and update stretch-backports to 384 thereafter,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 884140 src:linux Bug #884140 [linux-image] Kernel 3.16.51-2 general protection fault in sched_init_smp() Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux'. No longer marked as found in

Processed (with 1 error): Re: Bug#884140: Kernel 3.16.51-2 general protection fault in sched_init_smp()

Processing control commands: > forcemerge 883938 -1 Bug #883938 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51 Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22 Unable to merge bugs because: package of #884140 is

Bug#831835: Workaround in progress: Browser Add-On

On 2017-11-18, 24...@secmail.pro wrote: CloudFlare's MITM activity is widely discussed in the Tor Project ticket. This bug is mentioned on this webpage: https://trac.torproject.org/projects/tor/ticket/24351 I am the reporter of that bug, titled "Block Global Active Adversary Cloudflare".

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

The provided work-around (setting numa=off) worked here. Do you need further information about the system in use? BTW: Thank you for the NUMA advice, it was about 21.00 CET when I started a search engine and found the bug entry and the suggested work-around, so, your advice came just in time.

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#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Hi Ben, On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote: > On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote: > > There were several commits interspersed with sched/topology fixes > > upstream that I thought were cleanup and therefore didn't backport to > > the 3.16 stable

Bug#878498: snakemake FTBFS with Python 3.6 as default

On Mon, Dec 11, 2017 at 03:45:50PM +0100, Andreas Tille wrote: > > Will let you know when I'm through with those and all is pushed to > > alioth again. The current master passes build in a cowbuilder that has access to python3-ratelimiter, and lintian's only serious complaints are the privacy

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote: > There were several commits interspersed with sched/topology fixes > upstream that I thought were cleanup and therefore didn't backport to > the 3.16 stable branch. Now I suspect that at least some of them are > needed. > > I'm attaching

Bug#884063: marked as done (vlc-plugin-base: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/vlc/plugins/codec/libzvbi_plugin.so)

Your message dated Mon, 11 Dec 2017 21:35:52 + with message-id and subject line Bug#884063: fixed in vlc 3.0.0~rc1-1 has caused the Debian Bug report #884063, regarding vlc-plugin-base: fails to upgrade from 'sid' - trying to overwrite

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

There were several commits interspersed with sched/topology fixes upstream that I thought were cleanup and therefore didn't backport to the 3.16 stable branch. Now I suspect that at least some of them are needed. I'm attaching backports of 3 of the commits that I left out. Can you test whether

Bug#883937: marked as done (fix the build with libical3)

Your message dated Mon, 11 Dec 2017 21:17:21 + with message-id and subject line Bug#883937: fixed in gnome-todo 3.26.2-2 has caused the Debian Bug report #883937, regarding fix the build with libical3 to be marked as done. This means that you claim that

Bug#863612: marked as done (opendmarc: still ignore inet SOCKET configuration)

Your message dated Mon, 11 Dec 2017 21:19:13 + with message-id and subject line Bug#863612: fixed in opendmarc 1.3.2-3 has caused the Debian Bug report #863612, regarding opendmarc: still ignore inet SOCKET configuration to be marked as done. This means

Bug#875349: marked as done (libp11: Please migrate to openssl1.1 in Buster)

Your message dated Mon, 11 Dec 2017 21:00:14 + with message-id and subject line Bug#875349: fixed in libp11 0.4.7-2 has caused the Debian Bug report #875349, regarding libp11: Please migrate to openssl1.1 in Buster to be marked as done. This means that

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Hi here the bisect log (unless overseen something with the last good commit): git bisect start # good: [3717265153a66c2ecbd745ea8eef213289b4a55e] Linux 3.16.48 git bisect good 3717265153a66c2ecbd745ea8eef213289b4a55e # bad: [c45c05f42d5d3baf5d18e648c064788381fcfa1c] Linux 3.16.51 git bisect bad

Processed: severity of 863612 is serious

Processing commands for cont...@bugs.debian.org: > severity 863612 serious Bug #863612 [opendmarc] opendmarc: still ignore inet SOCKET configuration Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 863612:

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

On Wed, 2017-12-06 at 11:37 +0100, Andreas Beckmann wrote: > On 2017-12-06 10:53, Julien Aubin wrote: > > Okay I will try it. Could you please provide me the build guide and > > install > > guide ? > > From README.source: > > Building "bleeding edge" from SVN for users > > As new upstream

Bug#884134: python-rpy: Incompatible with the version of R in stretch

On 11 December 2017 at 19:37, Matthew Woodcraft wrote: | Package: python-rpy | Version: 1.0.3-30 | Severity: grave | | Installing and importing the stretch version of python-rpy fails with the | stretch version of R: | | « | apt install python-rpy | python | Python 2.7.13 (default, Nov 24 2017,

Bug#828477: marked as done (openvpn: FTBFS with openssl 1.1.0)

Your message dated Mon, 11 Dec 2017 21:04:51 +0100 with message-id <20171211200450.7wxkpgsigwuvq...@fliwatuet.svr02.mucip.net> and subject line Re: Bug#828477: openvpn: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828477, regarding openvpn: FTBFS with openssl 1.1.0 to be marked as

Bug#883937: marked as pending

tag 883937 pending thanks Hello, Bug #883937 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-gnome/gnome-todo.git/commit/?id=04cc486 --- commit

Processed: Bug#883937 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 883937 pending Bug #883937 [src:gnome-todo] fix the build with libical3 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 883937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883937

Processed: summary 883938 Seems to affect machines with 2+-sockets/NUMA. Workaround: set numa=off on the kernel command and downgrade to 3.16.48-1 or earlier

Processing commands for cont...@bugs.debian.org: > summary 883938 Seems to affect machines with 2+-sockets/NUMA. Workaround: set > numa=off on the kernel command and downgrade to 3.16.48-1 or earlier Summary replaced with message bug 883938 message Summary replaced with message bug 883938

Processed: summary 883938 Seems

Processing commands for cont...@bugs.debian.org: > summary 883938 Seems Summary replaced with message bug 883938 message Summary replaced with message bug 883938 message > thanks Stopping processing here. Please contact me if you need assistance. -- 883938:

Bug#884134: python-rpy: Incompatible with the version of R in stretch

Package: python-rpy Version: 1.0.3-30 Severity: grave Installing and importing the stretch version of python-rpy fails with the stretch version of R: « apt install python-rpy python Python 2.7.13 (default, Nov 24 2017, 17:33:09) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits"

Bug#876695: Fixed upstream

I'm thinking January, there's usually a new Parts Library at the end of the year so I'm thinking about updating both at the same time. Is there a way I can cross compile to test if the patch fixes this error? On Sun, Dec 10, 2017 at 12:37 PM, Nicolas Guilbert wrote: > Hi Leo,

Bug#884128: libical: don't release with buster

Source: libical Version: 2.0.0-1 Severity: serious Hi, We have src:libical3 now, so libical2 should be dropped before the freeze. We shouldn't need to release buster with both libical 2 and 3. Filing this bug so we don't forget about that. Emilio -- System Information: Debian Release:

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Bernhard Schmidt wrote: Can you check whether numa=off on the kernel command line fixes this as well? Indeed it does. Appending numa=off to the kernel command line fixes the bug in my KVM virtual machines as well as my physical servers (at least the ones I've tested so far). So this might be

Bug#884019: marked as done (terminology: FTBFS if $HOME is not writable)

Your message dated Mon, 11 Dec 2017 18:04:36 + with message-id and subject line Bug#884019: fixed in terminology 1.1.1-2 has caused the Debian Bug report #884019, regarding terminology: FTBFS if $HOME is not writable to be marked as done. This means that

Bug#843866: marked as done (photofloat: FTBFS: Can't find bundle for base name org.mozilla.javascript.resources.Messages, locale en_US)

Your message dated Mon, 11 Dec 2017 18:01:21 + with message-id and subject line Bug#880592: Removed package(s) from unstable has caused the Debian Bug report #843866, regarding photofloat: FTBFS: Can't find bundle for base name

Bug#858990: marked as done (kvirc: Please migrate to openssl1.1 in buster)

Your message dated Mon, 11 Dec 2017 18:00:32 + with message-id and subject line Bug#858990: fixed in kvirc 4:4.9.2~git20171211+dfsg-1 has caused the Debian Bug report #858990, regarding kvirc: Please migrate to openssl1.1 in buster to be marked as done.

Bug#830750: marked as done (photofloat: traceback on run)

Your message dated Mon, 11 Dec 2017 18:01:21 + with message-id and subject line Bug#880592: Removed package(s) from unstable has caused the Debian Bug report #830750, regarding photofloat: traceback on run to be marked as done. This means that you claim

Bug#844972: marked as done (photofloat: FTBFS: Exception in thread "main" java.lang.reflect.InvocationTargetException)

Your message dated Mon, 11 Dec 2017 18:01:21 + with message-id and subject line Bug#880592: Removed package(s) from unstable has caused the Debian Bug report #844972, regarding photofloat: FTBFS: Exception in thread "main"

Bug#883778: problems building guile-2.0 on armel

On Fri, Dec 08, 2017 at 05:32:38PM -0600, Rob Browning wrote: >Steve McIntyre writes: > >> Interestingly, in armhf mode the package builds just fine on the same >> type of hardware (built ok on hoiby). Wondering what on earth is going >> on... > >Agreed. > >For what it's worth,

Bug#824827: marked as done (Error: Encryption failed!)

Your message dated Mon, 11 Dec 2017 17:56:21 + with message-id and subject line Bug#880101: Removed package(s) from unstable has caused the Debian Bug report #824827, regarding Error: Encryption failed! to be marked as done. This means that you claim that

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Hi Karsten, Thanks for the test. Can you check whether numa=off on the kernel command line fixes this as well? Bernhard -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 873417 hashcat Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0 Added indication that 873417 affects hashcat > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#867501: marked as done (python-jingo FTBFS: test failures)

Your message dated Mon, 11 Dec 2017 17:52:05 + with message-id and subject line Bug#880044: Removed package(s) from unstable has caused the Debian Bug report #867501, regarding python-jingo FTBFS: test failures to be marked as done. This means that you

Bug#811628: marked as done (FTBFS with GCC 6: cannot convert x to y)

Your message dated Mon, 11 Dec 2017 17:48:34 + with message-id and subject line Bug#879463: Removed package(s) from unstable has caused the Debian Bug report #811628, regarding FTBFS with GCC 6: cannot convert x to y to be marked as done. This means that

Bug#848187: marked as done (xserver-xorg-video-freedreno: FTBFS with xserver 1.19)

Your message dated Mon, 11 Dec 2017 17:50:29 + with message-id and subject line Bug#879818: Removed package(s) from unstable has caused the Debian Bug report #848187, regarding xserver-xorg-video-freedreno: FTBFS with xserver 1.19 to be marked as done.

Bug#843382: marked as done (imgtex: libapache-mod-fastcgi is gone)

Your message dated Mon, 11 Dec 2017 17:49:23 + with message-id and subject line Bug#879577: Removed package(s) from unstable has caused the Debian Bug report #843382, regarding imgtex: libapache-mod-fastcgi is gone to be marked as done. This means that

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

I can reproduce the bug on multiple (physical) servers running in our data center. When booting my virtual servers with the new kernel, the issue did not arise... ...until I enabled NUMA. Booting a virtual machine with 2 sockets and 16 cores each works fine when NUMA is disabled in KVM. With

Bug#790220: marked as done (webkit2pdf: depends on libwebkitgtk-1.0-0 which is deprecated)

Your message dated Mon, 11 Dec 2017 17:47:22 + with message-id and subject line Bug#879167: Removed package(s) from unstable has caused the Debian Bug report #790220, regarding webkit2pdf: depends on libwebkitgtk-1.0-0 which is deprecated to be marked as

Bug#790219: marked as done (webkit-image: depends on libwebkitgtk-1.0-0 which is deprecated)

Your message dated Mon, 11 Dec 2017 17:45:58 + with message-id and subject line Bug#879128: Removed package(s) from unstable has caused the Debian Bug report #790219, regarding webkit-image: depends on libwebkitgtk-1.0-0 which is deprecated to be marked as

Bug#784559: marked as done ([webkit-image] Qt4's WebKit removal)

Your message dated Mon, 11 Dec 2017 17:45:58 + with message-id and subject line Bug#879128: Removed package(s) from unstable has caused the Debian Bug report #784559, regarding [webkit-image] Qt4's WebKit removal to be marked as done. This means that you

Bug#790203: marked as done (gphpedit: depends on libwebkitgtk-1.0-0 which is deprecated)

Your message dated Mon, 11 Dec 2017 17:46:29 + with message-id and subject line Bug#879158: Removed package(s) from unstable has caused the Debian Bug report #790203, regarding gphpedit: depends on libwebkitgtk-1.0-0 which is deprecated to be marked as

Bug#867052: marked as done (libunique: Not suitable for release in buster)

Your message dated Mon, 11 Dec 2017 17:35:52 + with message-id and subject line Bug#878761: Removed package(s) from unstable has caused the Debian Bug report #867052, regarding libunique: Not suitable for release in buster to be marked as done. This means

Bug#880289: marked as done (jackson-datatype-guava: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib

Your message dated Mon, 11 Dec 2017 17:34:03 + with message-id and subject line Bug#878472: Removed package(s) from unstable has caused the Debian Bug report #880289, regarding jackson-datatype-guava: FTBFS: dh_auto_test:

Bug#805297: marked as done (python-ceres: FTBFS: ImportError: No module named mock)

Your message dated Mon, 11 Dec 2017 17:34:31 + with message-id and subject line Bug#878543: Removed package(s) from unstable has caused the Debian Bug report #805297, regarding python-ceres: FTBFS: ImportError: No module named mock to be marked as done.

Bug#876427: marked as done (cmigrep: FTBFS with ocaml 4.05.0)

Your message dated Mon, 11 Dec 2017 17:33:39 + with message-id and subject line Bug#878448: Removed package(s) from unstable has caused the Debian Bug report #876427, regarding cmigrep: FTBFS with ocaml 4.05.0 to be marked as done. This means that you

Bug#824579: marked as done (iok: Uses deprecated libunique3)

Your message dated Mon, 11 Dec 2017 17:35:26 + with message-id and subject line Bug#878756: Removed package(s) from unstable has caused the Debian Bug report #824579, regarding iok: Uses deprecated libunique3 to be marked as done. This means that you

Bug#805158: marked as done (gurgitate-mail: FTBFS: find: `debian/gurgitate-mail/usr/lib': No such file or directory)

Your message dated Mon, 11 Dec 2017 17:27:56 + with message-id and subject line Bug#878283: Removed package(s) from unstable has caused the Debian Bug report #805158, regarding gurgitate-mail: FTBFS: find: `debian/gurgitate-mail/usr/lib': No such file or

Bug#831737: marked as done (pbnj: missing dependency on libshell-perl)

Your message dated Mon, 11 Dec 2017 17:23:51 + with message-id and subject line Bug#877889: Removed package(s) from unstable has caused the Debian Bug report #831737, regarding pbnj: missing dependency on libshell-perl to be marked as done. This means

Bug#871829: marked as done (blam: depends on libwebkit1.1-cil which is deprecated)

Your message dated Mon, 11 Dec 2017 17:17:00 + with message-id and subject line Bug#877751: Removed package(s) from unstable has caused the Debian Bug report #871829, regarding blam: depends on libwebkit1.1-cil which is deprecated to be marked as done.

Bug#790217: marked as done (webkit-sharp: depends on libwebkitgtk-1.0-0 which is deprecated)

Your message dated Mon, 11 Dec 2017 17:17:30 + with message-id and subject line Bug#877786: Removed package(s) from unstable has caused the Debian Bug report #790217, regarding webkit-sharp: depends on libwebkitgtk-1.0-0 which is deprecated to be marked as

Bug#882538: outguess: missing source for jpeg-6b-steg/configure

Thanks Helmut and Paul for your messages. There are more information about this issue in Debian Legal[1]. I tried to make a new configure.ac (or configure.in) but I had no success. I will try again when I have more time (I hope it can be soon). [1]

Processed: [bts-link] source package src:tiff

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:tiff > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Just as a note: Upgrading to jessie-backports version 4.9.51-1~bpo8+1 is also an option, which works. Christoph <> signature.asc Description: OpenPGP digital signature

Processed: found 875688 in 1:6.0.0~beta2-1

Processing commands for cont...@bugs.debian.org: > found 875688 1:6.0.0~beta2-1 Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy reports can be created and run Marked as found in versions libreoffice/1:6.0.0~beta2-1. > thanks Stopping processing here. Please contact

Processed: notfound 875688 in 6.0.0~beta2-1

Processing commands for cont...@bugs.debian.org: > notfound 875688 6.0.0~beta2-1 Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy reports can be created and run There is no source info for the package 'libreoffice-report-builder' at version '6.0.0~beta2-1' with

Bug#883938:

Same here with DELL R7910 and dual Xeon E5-2660v3. Downgrading the kernel did help.

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Hi The issue is as well happening with 3.16.51 vanilla (and config generated with localmodconfig, make deb-pkg built). Trying to bisect now. Regards, Salvatore

Processed: found 875688 in 6.0.0~beta2-1

Processing commands for cont...@bugs.debian.org: > found 875688 6.0.0~beta2-1 Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy reports can be created and run There is no source info for the package 'libreoffice-report-builder' at version '6.0.0~beta2-1' with

Processed: tagging 875688

Processing commands for cont...@bugs.debian.org: > tags 875688 - moreinfo Bug #875688 [libreoffice-report-builder] report builder inactive; only legacy reports can be created and run Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#884116: Further information

After some more searching I found that the screen artifacts start after this message (from dmesg): [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

Package: src:linux Version: 4.9.65-3 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? I did an upgrade today and linux image was upgraded from 4.9.51-1 to 4.9.65-3. * What was the outcome of this action? Various screen artifacts appear

Bug#872305: marked as done (diaspora: Package fails to install)

Your message dated Mon, 11 Dec 2017 15:19:10 + with message-id and subject line Bug#872305: fixed in diaspora 0.6.0.1+debian-2 has caused the Debian Bug report #872305, regarding diaspora: Package fails to install to be marked as done. This means that you

Bug#866877: marked as done (diaspora: fails on being triggered)

Your message dated Mon, 11 Dec 2017 15:19:10 + with message-id and subject line Bug#866877: fixed in diaspora 0.6.0.1+debian-2 has caused the Debian Bug report #866877, regarding diaspora: fails on being triggered to be marked as done. This means that you

Processed: affects 876608

Processing commands for cont...@bugs.debian.org: > affects 876608 diaspora Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable Added indication that 876608 affects diaspora > thanks Stopping processing here. Please contact me if you need

Processed: affects 875612

Processing commands for cont...@bugs.debian.org: > affects 875612 diaspora Bug #875612 [ruby-compass-rails] ruby-compass-rails: ruby-compass obsolete and now broken Added indication that 875612 affects diaspora > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#872305: marked as pending

tag 872305 pending thanks Hello, Bug #872305 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/diaspora.git/commit/?id=494820c --- commit

Bug#866877: marked as pending

tag 866877 pending thanks Hello, Bug #866877 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/diaspora.git/commit/?id=494820c --- commit

Processed: Bug#872305 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 872305 pending Bug #872305 [diaspora] diaspora: Package fails to install Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 872305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872305

Bug#884069: Same problem on Supermicro H8DGi-F

Same here with Supermicro H8DGi-F (with only one cpu installed)

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

Same here, whole cluster of machines down here with this kernel. Same panic message, so I won't repeat it here. These are Supermicro boxes with Xeon CPUs: $ lscpu Architecture:  x86_64 CPU op-mode(s):    32-bit, 64-bit Byte Order:    Little Endian CPU(s):    16

Processed: Bug#866877 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 866877 pending Bug #866877 [diaspora] diaspora: fails on being triggered Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 866877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866877

Bug#851086: RFH: citadel/webcit

On 11.12.2017 13:42, Michael Meskes wrote: > Anyone interested in citadel/webcit? If not I'm going to have it removed I > guess. > > There used to be a team maintaining these packages, but I'm the only one who > worked on it in recent years. Not having used the software myself I don't > really

Processed: Control

Processing commands for cont...@bugs.debian.org: > fixed #868773 1:0.9.6-2 Bug #868773 [src:khal] khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address') Marked as fixed in versions khal/1:0.9.6-2. > End of message, stopping processing here. Please contact me if you need

Bug#883731: audacious: Debian packaging has incorrect license

Nicholas D Steeves writes ("Re: Bug#883731: audacious: Debian packaging has incorrect license"): > Will I also need to provide formal copies in debian/COPYING.emails or > would a README.copyright or similar pointing to the bug report > suffice? In particular I'm concerned about lines like this

Bug#875688: libreoffice-report-builder: report builder inactive; only legacy reports can be created and run

Hi Rene and Lionel, we just tested version 6.0.0~beta2-1 and unfortunately we find that Report Builder is inactive ... Regards! Guido

Bug#878498: snakemake FTBFS with Python 3.6 as default

On Mon, Dec 11, 2017 at 03:35:53PM +0100, chrysn wrote: > I've got them all down locally; it'll need some cleaning up (and > possibly upstreaming) of patches, and I have yet to run it in a pbuilder > to see which build dependencies popped up that are undeclared so far, > but I don't expect any

Bug#878498: snakemake FTBFS with Python 3.6 as default

> The problem is that when trying to build this I get a lot of errors in > the build time tests. Is there any volunteer to have a look? I've got them all down locally; it'll need some cleaning up (and possibly upstreaming) of patches, and I have yet to run it in a pbuilder to see which build

Bug#884090: superlu: Source includes "SRC/mc64ad.c" listed in Files-Excluded header

Hi Drew! > Looks like you're looking at the SRC dir after debian patches have been > applied. Indeed; thanks for pointing that out and for closing the bugs. :) (FYI as Lintian will report a warning on this in recent versions, you may need to specify an override with a suitable explanatory

Processed: severity of 589003 is serious

Processing commands for cont...@bugs.debian.org: > severity 589003 serious Bug #589003 [cdrdao] cdrdao deletes cue file Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 589003:

Processed: geis: diff for NMU version 2.2.17-1.2

Processing control commands: > tags 849604 + patch Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc” Added tag(s) patch. > tags 849604 + pending Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc” Added tag(s) pending. > tags 853415 + pending

Bug#853415: geis: diff for NMU version 2.2.17-1.2

Control: tags 849604 + patch Control: tags 849604 + pending Control: tags 853415 + pending Dear maintainer, I've prepared an NMU for geis (versioned as 2.2.17-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- regards,

Processed: geis: diff for NMU version 2.2.17-1.2

Processing control commands: > tags 849604 + patch Bug #849604 [src:geis] libgeis: please add dependency “Suggests: libgeis-doc” Ignoring request to alter tags of bug #849604 to the same tags previously set > tags 849604 + pending Bug #849604 [src:geis] libgeis: please add dependency “Suggests:

Bug#884107: apscheduler FTBFS: test failure

Source: apscheduler Version: 3.4.0-1 Severity: serious Some recent change in unstable makes apscheduler FTBFS: https://tests.reproducible-builds.org/debian/history/apscheduler.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apscheduler.html ... debian/rules

Bug#880866: python-dotenv: diff for NMU version 0.7.1-1.1

Control: tags 880866 + patch Control: tags 880866 + pending Dear maintainer, I've prepared an NMU for python-dotenv (versioned as 0.7.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- regards, Mattia Rizzolo GPG

Processed: python-dotenv: diff for NMU version 0.7.1-1.1

Processing control commands: > tags 880866 + patch Bug #880866 [src:python-dotenv] python-dotenv FTBFS with python 3.6 as only supported version Added tag(s) patch. > tags 880866 + pending Bug #880866 [src:python-dotenv] python-dotenv FTBFS with python 3.6 as only supported version Added tag(s)

Bug#884012:

Having the same issue, this causes a lot of IO due to writing logs and gnome-shell constantly being near 100% cpu. Is there any way to disable org.gnome.Shell.CalendarServer service, or to prevent it from restarting ? Thanks, -- Vincent Alquier vincent.alqu...@gmail.com

Bug#884102: yowsup FTBFS: TypeError: Error when calling the metaclass bases

Source: yowsup Version: 2.5.0~git20160904.d69c1ff-1 Severity: serious Tags: buster sid Some recent change in unstable makes yowsup FTBFS: https://tests.reproducible-builds.org/debian/history/yowsup.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yowsup.html ...

Bug#851086: RFH: citadel/webcit

Anyone interested in citadel/webcit? If not I'm going to have it removed I guess. There used to be a team maintaining these packages, but I'm the only one who worked on it in recent years. Not having used the software myself I don't really intend to spend more time on it and both packages have

  1   2   >