Processed: Bug#1008513 marked as pending in node-ignore

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1008513 [node-ignore] FTBFS unsufficient coverage Added tag(s) pending. -- 1008513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008513: marked as pending in node-ignore

2022-03-27 Thread Yadd
Control: tag -1 pending Hello, Bug #1008513 in node-ignore reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-ignore/-/commit/c3e396d981000df6f83811bc

Bug#1008514: FTBFS -- upstream test suite failure

2022-03-27 Thread julien . puydt
Package: node-immutable Version: 4.0.0-2 Severity: serious Tags: ftbfs Trying to build the package in an unstable sbuild, I get the following failure: + NODE_PATH=node_modules:/usr/share/nodejs jest --ci __tests__/ArraySeq.ts Error at Function.missingTransform (/usr/share/nodejs/buble/dist/bub

Bug#1008512: FTBFS in upstream test suite

2022-03-27 Thread julien . puydt
Package: node-https-proxy-agent Version: 5.0.0+~cs8.0.0-3 Severity: serious Tags: ftbfs Trying to rebuild the package in an unstable sbuild gives the following failure in upstream test suite: 1) HttpsProxyAgent "http" module should receive the 407 authorization code on the `http.

Bug#1008513: FTBFS unsufficient coverage

2022-03-27 Thread julien . puydt
Package: node-ignore Version: 5.2.0-1 Severity: serious Tags: ftbfs Building the package in an unstable sbuild, I get: ERROR: Coverage for lines (92.3%) does not meet global threshold (100%) ERROR: Coverage for functions (91.66%) does not meet global threshold (100%) ERROR: Coverage for branches (

Bug#1008511: FTBFS failures in the upstream test suite

2022-03-27 Thread julien . puydt
Package: node-configurable-http-proxy Version: 4.5.0+~cs15.1.4-3 Severity: serious Tags: ftbfs Building the package in an unstable sbuild, I get failures: Randomized with seed 97263 Started ..F...06:23:50.587 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /nope 06:23:50.860 [C

Bug#1008510: FTBFS unsufficient coverage

2022-03-27 Thread julien . puydt
Package: node-base64url Version: 3.0.1-7 Severity: serious Tags: ftbfs Trying to build the package in an unstable sbuild, the upstream test suite fails because it doesn't find a 100% coverage: ERROR: Coverage for lines (97.22%) does not meet global threshold (100%) ERROR: Coverage for branches (75

Bug#1008509: FTBFS - six upstream tests failing

2022-03-27 Thread julien . puydt
Package: node-config Version: 3.3.7-1 Severity: serious Tags: ftbfs While rebuilding your package with an unstable sbuild, it failed at six points in the upstream test suite, with the same error: » An unexpected error was caught: TypeError: Cannot set property offset of [object Object] wh

Bug#1008508: marked as done (borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 08:09:27 +0200 with message-id <24be2ebc-f41a-c8f8-6664-27aae30b0...@debian.org> and subject line Re: Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10 has caused the Debian Bug report #1008508, regarding borgbackup: Uni

Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10

2022-03-27 Thread Axel Beckert
Hi, Axel Beckert wrote: > borgbackup became uninstallable in Debian Unstable due a dependency on > python3 < 3.10 while Python 3.10 has landed in Unstable yesterday. Ah, I just saw https://release.debian.org/transitions/html/python3.10-default.html so I assume this can be fixed with a BinNMU whic

Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10

2022-03-27 Thread Axel Beckert
Package: borgbackup Version: 1.2.0-1 Severity: serious Hi, borgbackup became uninstallable in Debian Unstable due a dependency on python3 < 3.10 while Python 3.10 has landed in Unstable yesterday. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'uns

Processed: Bug#1005438 marked as pending in pygame

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005438 {Done: Scott Talbert } [src:pygame] pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned exi

Bug#1005438: marked as pending in pygame

2022-03-27 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #1005438 in pygame reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pygame/-/commit/ee23ea00fa9caedf8f391

Bug#1005438: marked as done (pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ -

2022-03-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 03:18:45 + with message-id and subject line Bug#1005438: fixed in pygame 2.1.2+dfsg-1 has caused the Debian Bug report #1005438, regarding pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/

Bug#1008343: marked as done (snek: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 18:03:01 -0700 with message-id <87r16mc2ii@keithp.com> and subject line Re: Bug#1008343: snek: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1008343, regarding snek: FTBFS: E: Build killed with sign

Processed: Bug#1008478 in package dpkg marked as pending

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > tag 1008478 pending Bug #1008478 [dpkg] dpkg-fsys-usrunmess depends on umask 022 Added tag(s) pending. -- 1008478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008478: in package dpkg marked as pending

2022-03-27 Thread Guillem Jover
Control: tag 1008478 pending Hi! Bug #1008478 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=77756084e --- dpkg-fsys-usrunmess: Ex

Processed: Re: Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 meson 0.62.0-1 Bug #1008382 [src:glib2.0] glib2.0: FTBFS: ld: cannot find -lgdbus-example-objectmanager: No such file or directory Bug reassigned from package 'src:glib2.0' to 'meson'. No longer marked as found in versions glib2.0/2.72.0-1. Ignoring requ

Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies

2022-03-27 Thread Simon McVittie
Control: reassign -1 meson 0.62.0-1 Control: retitle -1 meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies Control: affects -1 + src:glib2.0 On Sat, 26 Mar 2022 at 21:44:54 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to bu

Bug#1008502: vdirsyncer: Unknown error occured: unmatched ')'

2022-03-27 Thread Christof Schulze
Package: vdirsyncer Version: 0.16.8-2 Severity: grave Justification: renders package unusable Dear Maintainer, Running vdirsyncer sync causes the above error message about unmatched ')'. This renders 0.4.4 - the version in stable - unusable. The root cause is that python-click-threading 0.4.4, w

Processed: Re: Bug#1008316: dpkg-fsys-usrunmess breaks system boot

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Bug #1008316 [dpkg] dpkg-fsys-usrunmess breaks system boot Changed Bug title to 'dpkg-fsys-usrunmess: Does not deal with untracked kernel modules' from 'dpkg-fsys-usrunmess breaks system boo

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

2022-03-27 Thread Guillem Jover
Control: retitle -1 dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Hi! On Sat, 2022-03-26 at 19:21:44 +0100, Eric Valette wrote: > Package: dpkg > Version: 1.21.4 > Severity: critical > Justification: breaks the whole system > Gobally the scripts does a very good job but it mi

Processed: bugs metadata

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1008316 1.20.6 Bug #1008316 [dpkg] dpkg-fsys-usrunmess breaks system boot Marked as found in versions dpkg/1.20.6. > found 1008478 1.20.6 Bug #1008478 [dpkg] dpkg-fsys-usrunmess depends on umask 022 Marked as found in versions dpkg/1.20.6. >

Bug#1005833: [DRE-maint] Bug#1005833: src:ruby-redis: fails to migrate to testing for too long: autopkgtest regression

2022-03-27 Thread Cédric Boutillier
Quoting Paul Gevers (2022-03-21 21:13:29) > Is there any progress on this issue? Is no progress is there another way > to move the problem forward? E.g. revert ruby-redis to the previous > version if redis and fakeredis can agree on the change in behavior? I am preparing an upload of ruby-fakere

Processed: severity of 1008498 is normal, reassign 1008498 to ftp.debian.org ...

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1008498 normal Bug #1008498 [src:hgsubversion] Should hgsubversion be removed? Severity set to 'normal' from 'serious' > reassign 1008498 ftp.debian.org Bug #1008498 [src:hgsubversion] Should hgsubversion be removed? Bug reassigned from p

Bug#1008498: Should hgsubversion be removed?

2022-03-27 Thread Andrej Shadura
Hi, On Sun, 27 Mar 2022, at 23:33, Moritz Muehlenhoff wrote: > Source: hgsubversion > Version: 1.9.3+git20190419+6a6ce-5 > Severity: serious > > Your package came up as a candidate for removal from Debian: > > - Still depends on Python 2 and removed from testing since 2020 > - Dead upstream (no co

Bug#1008500: Should undertaker be removed?

2022-03-27 Thread Moritz Muehlenhoff
Source: undertaker Version: 1.6.1-4.2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Last maintainer upload in 2016 If you disagree and want to continue to maintain this package, please just cl

Bug#1008499: Should neard be removed?

2022-03-27 Thread Moritz Muehlenhoff
Source: neard Version: 0.16-0.1 Severity: serious Your package came up as a candidate for removal from Debian: - Last maintainer upload in 2013 - Depends on Python 2 and thus removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug

Bug#1008498: Should hgsubversion be removed?

2022-03-27 Thread Moritz Muehlenhoff
Source: hgsubversion Version: 1.9.3+git20190419+6a6ce-5 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and removed from testing since 2020 - Dead upstream (no commits after 2019) If you disagree and want to continue to maintain this pac

Bug#1008497: linux-image-5.10.0-13-arm64: 5.10.0-13-arm64 gets stuck after loading ramdisk on VMWareFusion under M1. 5.10.0-12-arm64 works.

2022-03-27 Thread Andreas Fink
Package: src:linux Version: 5.10.106-1 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Brand new Mac Studio M1 Ultra Install VMWare Fusion Pro Tech Preview for ARM/M1 Download 11.3

Processed: tagging 997213

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 997213 + patch Bug #997213 [src:i2p] i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:25: error: package javax.servlet.http does not exist Added tag(s) patch. > thanks Stopping processing here. Please contac

Bug#997213: NMU to DELAYED/5

2022-03-27 Thread Pierre Gruet
Dear Maintainer, I have prepared a NMU of i2p fixing bugs #997213 and #986474. Please find enclosed the corresponding source debdiff. I made the upload to DELAYED/5, please feel free to ask me to cancel it if you want. Best regards, -- Pierre diff -Nru i2p-0.9.48/debian/changelog i2p-0.9.4

Bug#1005596: marked as done (modem-manager-gui: FTBFS: ../appdata/meson.build:3:5: ERROR: Function does not take positional arguments.)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 20:35:59 + with message-id and subject line Bug#1005596: fixed in modem-manager-gui 0.0.20-3 has caused the Debian Bug report #1005596, regarding modem-manager-gui: FTBFS: ../appdata/meson.build:3:5: ERROR: Function does not take positional arguments. to be

Bug#1008415: libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2

2022-03-27 Thread Mike Gabriel
Hi Axel, On Sa 26 Mär 2022 23:57:57 CET, Axel Beckert wrote: But a short look through those binary packages most likely having reverse-dependencies (libnih-dbus1 and libnih1), I though found a single reverse dependency not coming from the libnih package: $ apt-cache rdepends libnih1 libnih1 R

Processed: forcibly merging 1003012 1008235

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1003012 1008235 Bug #1003012 {Done: Salvatore Bonaccorso } [bash] bash: Corrupted multibyte characters in command substitutions Bug #1008235 [bash] bash: corrupting variables containing long unicode content Set Bug forwarded-to-address

Processed: your mail

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1001669 help Bug #1001669 [src:openvpn-auth-ldap] openvpn-auth-ldap: flaky autopkgtest on amd64 Added tag(s) help. > End of message, stopping processing here. Please contact me if you need assistance. -- 1001669: https://bugs.debian.org/cg

Bug#1001669: closed by Debian FTP Masters

2022-03-27 Thread Aniol Martí
On Wed, 23 Mar 2022 09:09:00 +0100 Aniol Martí wrote:> I've tried several times and I can't reproduce the bug. I would need further details or assistance. Besides, I also noticed that the last test passed fine: https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/

Bug#1008465: [Debian-pan-maintainers] Bug#1008465: python-fabio: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils')

2022-03-27 Thread Jerome Kieffer
Hi Lucas, Thanks for the report. This looks like a bug I recently fixed in pyFAI ... I'll have a look tomorrow. Probably just a missing dependency like in https://github.com/silx-kit/pyFAI/commit/7bcb6dd7419b48580d97cd91a28d05f86b301f1c Cheers, Jerome On Sat, 26 Mar 2022 22:57:37 +0100 Lucas N

Processed: Re: Bug#1008337: shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX'

2022-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1008337 https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967 Bug #1008337 [src:shotwell] shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX' Set Bug forwarded-to-address

Bug#1008337: shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX'

2022-03-27 Thread Jörg Frings-Fürst
forwarded 1008337 https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967 thanks Hello Lucas, thank you for spending your time helping to make Debian better with this bug report. Am Samstag, dem 26.03.2022 um 21:48 +0100 schrieb Lucas Nussbaum: > Source: shotwell > Version: 0.30.14-2 > Severit

Bug#1008456: marked as done (python-whitenoise: FTBFS: FAILED tests/test_django_whitenoise.py::test_get_gzip - AssertionError: asser...)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 14:35:21 + with message-id and subject line Bug#1008456: fixed in python-whitenoise 6.0.0-1 has caused the Debian Bug report #1008456, regarding python-whitenoise: FTBFS: FAILED tests/test_django_whitenoise.py::test_get_gzip - AssertionError: asser... to be

Bug#1008436: marked as done (golang-github-ugorji-go-codec: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/ugorji/go/codec github.com/ugorji/go/codec/codecg

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 12:19:09 + with message-id and subject line Bug#1008436: fixed in golang-github-ugorji-go-codec 1.2.7-1 has caused the Debian Bug report #1008436, regarding golang-github-ugorji-go-codec: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=o

Bug#1008441: marked as done (astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 13:53:12 +0200 with message-id <5c4c8692-bb95-eb25-1782-937913b52...@debian.org> and subject line Re: astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 has caused the Debian Bug report #10084

Bug#1008486: dpkg-fsys-usrunmess: should include warning that systems will be unsupported

2022-03-27 Thread Ansgar
Package: dpkg Version: 1.21.2 Severity: serious Hi, the `dpkg-fsys-usrunmess` program should include a warning that it will convert the system into a state that will no longer be supported in the future by Debian. Ansgar

Processed: Bug#1008429 marked as pending in golang-github-docker-distribution

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1008429 [src:docker-registry] docker-registry: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -test.short -test.timeout=1h github.com/docker/distribution github.com/docker/distribution/cmd/registry [...] github

Bug#1008429: marked as pending in golang-github-docker-distribution

2022-03-27 Thread Shengjing Zhu
Control: tag -1 pending Hello, Bug #1008429 in golang-github-docker-distribution reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github

Bug#1008329: apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met

2022-03-27 Thread Lucas Nussbaum
On 26/03/22 at 23:36 +0100, Tino Didriksen wrote: > This was an expected failure due to new incompatible tool packages, and > same goes for all the other Apertium-related FTBFS. > > How can one prevent such a slew of superfluous automatic bugs from being > filed? Is there a way to mark packages as

Bug#1008360: [Debian-on-mobile-maintainers] Bug#1008360: phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’

2022-03-27 Thread Guido Günther
control: tags -1 +pending Hi, On Sat, Mar 26, 2022 at 09:47:37PM +0100, Lucas Nussbaum wrote: > Source: phoc > Version: 0.12.0-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220326 ftbfs-bookworm > > Hi, > > During a rebuild o

Processed: Re: [Debian-on-mobile-maintainers] Bug#1008360: phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’

2022-03-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +pending Bug #1008360 [src:phoc] phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’ Added tag(s) pending. -- 1008360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008360 Debian Bug Trac

Bug#1008417: marked as done (golang-github-rican7-retry: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/Rican7/retry github.com/Rican7/retry/backoff github.com/Rican7/ret

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 10:03:56 + with message-id and subject line Bug#1008417: fixed in golang-github-rican7-retry 0.3.1-1 has caused the Debian Bug report #1008417, regarding golang-github-rican7-retry: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.co

Bug#1008446: marked as done (diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 08:33:46 + with message-id and subject line Bug#1008446: fixed in diffoscope 209 has caused the Debian Bug report #1008446, regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

Bug#1008377: zanshin: FTBFS: unsatisfiable build-dependencies: libkf5akonadi-dev (>= 4:21.08.40~), libkf5akonadicalendar-dev (>= 4:21.08.40~), libkf5kontactinterface-dev (>= 21.08.40~)

2022-03-27 Thread Aurélien COUDERC
Le 26 mars 2022 21:52:54 GMT+01:00, Lucas Nussbaum a écrit : > >Hi, Dear Lucas, >During a rebuild of all packages in sid, your package failed to build >on amd64. Thanks for your bug report. I uploaded zanshin to unstable instead of experimental by mistake. This will be fixed once KDE PIM tr

Bug#1008318: marked as done (nanopb: missing dependency python3-protobuf)

2022-03-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Mar 2022 07:48:39 + with message-id and subject line Bug#1008318: fixed in nanopb 0.4.5-3 has caused the Debian Bug report #1008318, regarding nanopb: missing dependency python3-protobuf to be marked as done. This means that you claim that the problem has been dealt

Bug#1008156: telegram-desktop: Crash when switch account

2022-03-27 Thread Mattia Monga
Package: telegram-desktop Version: 3.6.1+ds-2 Followup-For: Bug #1008156 X-Debbugs-Cc: mo...@debian.org I can confirm the same problem. Moreover, my instance crashes also when I choose the "Settings" ("Impostazioni" in Italian) menu. -- Package-specific info: -- System Information: Debian Rel