Bug#1099648: gajim: Minimizing gajim makes it impossible to maximize again.

For me it is now fixed (in 2.1.0-1, the current Gajim version in Trixie).

Bug#1099775: xfce4-power-manager-plugins: To change brightness, you need to install "pkexec"

at and) pkexec got autoremoved. That's why in my case, it worked fine in Bookworm and broke in Trixie. Thanks, Gert -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Archi

Bug#1099648: gajim: Minimizing gajim makes it impossible to maximize again.

I believe this upstream bug report is related: https://dev.gajim.org/gajim/gajim/-/issues/12165 (I have the same issue, also XFCE).

Bug#1095438: sna: Allow DRI3 on gen2/3

ker...@lists.debian.org) (i686-linux-gnu-gcc-13 (Debian 13.3.0-6) 13.3.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.10.11-1 (2024-09-22) Xorg X server log files on system: -- -rw-r--r-- 1 gert gert 30928 Dec 20 22:06 /home/gert/.

Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

I think this issued can be closed. In fact it is a really sad story. Problems occurred at i915 classic. Xwayland upstream didnot want to remove the activation of ES 2.0, which totally was not working. But they also did not want to approve merge-requests, which solve the problems. Then Debian was

Bug#1053804: also at trixie

Same problem at Debian trixie(testing) with filezilla 3.65.0-3 : 2023-10-16T21:24:24.379086+02:00 debian systemd[1809]: Started app-gnome-filezilla-4525.scope - Application launched by gnome-shell. 2023-10-16T21:24:26.646156+02:00 debian kernel: [ 5791.686214] traps: filezilla[4525] trap invalid

Bug#1053804: code snippet

Unfortunately something went wrong with copying text, so debian/rules is copied twice. Also code is mangled a little bit. This is the correct code snippet: ifeq ($(DEB_HOST_ARCH_CPU),i386) # Workaround GCC bug on i386 # Append -msse4.1 to CFLAGS and CXXFLAGS     sed 's?-Wall?-Wall -msse4.1?'

Bug#1053804: filezilla: Filezilla aborts with invalid opcode at i386

ogs -k NEWS override_dh_link: # Remove doc from filezilla binary package, # a symlink to filezilla-common is created by dh_link rm -rf debian/filezilla/usr/share/doc/ dh_link gert@debian:/mnt/data/srcfilezilla5/filezilla-3.63.0/debian$ vi rules gert@debian:/mnt/data/srcfilezilla5/filezilla-3.63.0/

Bug#1034195: upstream gcc bug

Phil I made an upstream issue at GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109504 . Perhaps you can add other packages there, that have the same problem?

Bug#1034195: Question

Hi Phil, Thanks for soon reply. What do you mean by upstream. I only know a ticket at filezilla, but this is closed. I think this is  a regression bug at gcc 12, but I could not find a bugreport upstream or at Debian for gcc. Greetings, Gert

Bug#1034195: GCC bug

I saw the problem already is known at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020327 and https://trac.filezilla-project.org/ticket/12777 I downloaded source filezilla-3.63.2.1 from filezilla website and got the same problem as mentioned

Bug#1034195: filezilla: Filezilla not available anymore at i386

Source: filezilla Version: 3.63.0-1 Severity: important Dear Maintainer, Recently I automatically upgraded to version 3.63.0-1. With this version the package and binary filezilla is no longer available at i386 architecture (32 bits). This is also visible at the Debian package overview for filez

Bug#1032412: Plymouth changed

At plymouth the computation of Window.GetWidth() and Window.GetHeight() has changed 2 years ago. It now contains the sizes of the largest screen i.s.o. the smallest screen. See merge-request https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/121 : "use resolution of higher res monit

Bug#1032412: no message at dual screen

I have the same problem at dual screen with sizes 1280 x 1024 and 1280 x 800. New debian-logo tries to write the message "resuming from hibernation" below borh screens. This is caused by wrong computation of max height. In my case it computes 2 * 112 + 1024, which should be only 1024. .Prob

Bug#1025213: Mutter issue upstream 2602

Sorry, previous message has wrong link. Mutter issue upstream opened athttps://gitlab.gnome.org/GNOME/mutter/-/issues/2602 .

Bug#1025213: Issue upstream

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025213

Bug#1025213: Mutter mr 2241

Problem is caused by mutter merge-request 2241: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2241 . Shadow buffer is only used at software rendering. Damage history is needed at copy from shadow buffer to onscreen, to synchronize buffers. I will open an issue upstream. "

Bug#1025213: Extra info

I also tried mutter 43.2-4 without the Debian patches, specially the Support-Dynamic-triple-double-buffering.patch . This did not solve the problem, The only difference is that during blinking of the cursor there is switching between 2 different (old) backgrounds i.s.o. 3.

Bug#1025213: mutter

Thank you for adding gallium i915 to mesa 22.3.2-1. Now at least the default Debian testing release is usable at my laptop. But the  problem stills persists, if the i915-driver is removed and kms_swrast is used. In fact it is a mutter-problem (43.2-4) with shadow buffering. Problem can be best v

Bug#1025213: Extra info

I installed  all mesa-packages of previous installed version 22.2.0-1. I also installed previous installed kernel 5.19.11-1. With these versions the problem still existed.

Bug#1025213: DRM platform with kms_swrast

If the i915 dri driver is present gnome-shell is using the DRM platform (not the Wayland platform?) with this driver. If i915 is not present gnome-shell uses the DRM platform with the kms_swrast-driver! I did not see this with the lsof-command, because the name of the "zink"-driver was shown whic

Bug#1025213: i915g

The Gallium dri driver i915 22.3.0 also at my laptop is working and stops the flickering problem. Unfortunately it still is not supported and also has issues. Specially with shaders it is not compatible with classic i915. Less shaders are compiled without errors and also there is no fallback (whic

Bug#1025213: Extra info

I tried to install gnome-shell-common gnome-shell and gnome-shell-extension-prefs 43.0.2. This did not succeed because of failing login  (protocol)? Then I compiled source gnome-shell 43.0.2 and installed at /usr/local... I verified the version with gnome-shell --version. This downgrade did not

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

Hello Simon, Unfortunately my 32-bit Dell-laptop does not crash and I think the software-boys should not stop delivery of software for older hardware, forcing to waste good working hardware. Therefore I will use Debian testing as long as it supports 32-bit, so at least some one is testing so

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

Package: gnome-shell Version: 43.1-2 Severity: serious Justification: Policy 3.8 Dear Maintainer, Recently a general upgrade was executed with gnome-shell upgrading from version 43.0-2 to 43.1-2. After this upgrade the gnome-shell wayland screen is flickering and mangled at any action. Flickeri

Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

I suspect to have this same bug. In case it's useful, I got kernel logs via serial console, see attachment. Therein I have marked where VGA console output stops. Serial console goes a bit further. SysRq+B still works. My system: MSI 785GM-E51 (AMD 785G+SB710) + Dell Radeon R5 240 OEM (Oland). I

Bug#1010357: Solved

This problem is solved upstream at recent Debian version  gtk4 4.6.4+ds-3

Bug#1010357: upstream issue reported

Reported upstream at https://gitlab.gnome.org/GNOME/gtk/-/issues/4894

Bug#1010357: extra info

No problem if I use: LIBGL_ALWAYS_SOFTWARE=1  MESA_DEBUG=1 gnome-control-center gnome-control-center also works if I use: MESA_GLES_VERSION_OVERRIDE=1.0 MESA_DEBUG=1 gnome-control-center (gnome-control-center:5552): GLib-WARNING **: 10:59:38.934: GError set over the top of a previous GError or

Bug#1010357: Extra info

I am using a DELL Latitude D620 laptop with Core Duo inside. It only supports i386. lscpu Architecture:    i686   CPU op-mode(s):    32-bit   Address sizes: 32 bits physical, 32 bits virtual   Byte Order:    Little Endian CPU(s):  2   On-line CPU(s) list

Bug#1010357: gnome-shell: Gnome settings by gnome-control-center and other apps abort with SIGSEGV

_mesa_error shows it is caused by gtk-4. At gsk/gl/gskglcommandqueue.c exist the lines: glVertexAttribPointer (2, 4, GL_HALF_FLOAT, GL_FALSE, and glVertexAttribPointer (3, 4, GL_HALF_FLOAT, GL_FALSE, gert@debian:~$ gnome-control-center Mesa: User error: GL_INVALID_ENUM in glVertexAttribPointer(type

Bug#1008907: backtrace

Reading symbols from /usr/bin/pipewire... (No debugging symbols found in /usr/bin/pipewire) warning: Can't open file /memfd:pipewire-memfd (deleted) during file-backed mapping note processing [New LWP 1511] [New LWP 1515] [Thread debugging using libthread_db enabled] Using host libthread_db lib

Bug#1008907: pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1

Package: pipewire Version: 0.3.49-1 Severity: grave Justification: renders package unusable Dear Maintainer, 2022-04-03 13:26:47 upgrade pipewire:i386 0.3.48-1 0.3.49-1 No sound and no speaker symbol visible. Apr 3 14:02:25 debian wireplumber[755]: Failed to set scheduler settings: Operation n

Bug#1003091: Upstream issue opened

I reported the bug upstream for Xwayland: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1288 It will be fixed.

Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

Package: xwayland Version: 2:21.1.4-1 Severity: important Tags: upstream Dear Maintainer, I am using graphics: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) Subsystem: Dell Mobile 945GM/PM/GMS, 943/940GML and 945GT Express

Bug#1000172: upstream issue fixed

I reported the bug upstream at gnome-shell: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4883 Upstream bug solved with merge-request: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2072 https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2074

Bug#999686: upstream issue

I reported the bug upstream at pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1866

Bug#998368: upstream issue

I reported the bug upstream at pulseaudio: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1297

Bug#1000320: RM: ginkgocadx -- ROM; FTBS; dead upstream

3.1 which is blocked on #919903 Thanks, Gert

Bug#1000172: gnome-shell: Mouse hangs long when moving over sidepages of Show Applications page

Package: gnome-shell Version: 41.1-1 Severity: normal Tags: upstream Dear Maintainer, Problem occurs at the Show Applications page. If the mouse moved over the slideSidePages at the left or the right of the page with application icons, it hangs about 15 to 30 seconds, before the arrow and a row

Bug#999686: added suggested fix

In fact this bug is a problem at wireplumber, not at pipewire-pulse. Program wireplumber uses config-file /usr/share/alsa-card-profile/mixer/paths/analog-output-speaker.conf . Like at pulseaudio the problem can be solved by commenting out thye next lines: ; Make sure the internal speakers ar

Bug#999686: pipewire-pulse: Pipewire-pulse disabling auto-mute mode

Package: pipewire-pulse Version: 0.3.40-1 Severity: normal Tags: upstream Recently I installed new updates, which also installed new packages pipewire- pulse and wireplumber. 2021-11-07 22:29:42 remove pipewire-media-session:i386 0.3.38-2 2021-11-07 22:29:43 upgrade libpipewire-0.3-dev:i386

Bug#998368: pulseaudio: Pulseaudio disabling auto-mute mode

Package: pulseaudio Version: 15.0+dfsg1-2 Severity: normal Tags: upstream Dear Maintainer, Recently I installed new updates, including pulseaudio: 2021-10-19 23:32:51 upgrade pulseaudio:i386 14.2-2 15.0+dfsg1-2 2021-10-19 23:47:37 status installed pulseaudio:i386 15.0+dfsg1-2 After these updat

Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

should not got into testing as is, and for that reason the severity should be "serious" at least (But I don't want to go into a severity fight, so I don't add a control line to change this). Best,  Gert

Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

ot message lines) Turning off the boot "quiet" option, and/or adding "nomodeset" doesn't change things. regards, Gert -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: TUF Gam

Bug#994449: linux-image-5.14.0-trunk-amd64: Please enable CONFIG_UDMABUF

package: src:linux Version: 5.14.3-1~exp1 Severity: wishlist Dear Maintainer, UDMABUF is useful qemu, and required to get blob support, which in turn is needed by mesa/virgl to get support for ARB_buffer_storage and OpenGL 4.4 in the guest, and Vulkan support in the guest. Many thanks, Gert

Bug#983466: Is a mesa-bug

because wayland itself needs 2 fence registers for 2 momitors  i and X11 only 1. A trace without using wayland shows the 15th register is used without giving any problem: Feb 24 20:10:59 debian systemd[1270]: Started GNOME Shell on X11. Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWith

Bug#956437: closed by Debian FTP Masters (reply to Aurélien COUDERC ) (Bug#956426: fixed in desktop-base 11.0.2)

Hello Aurelien, Unfortunately this solution does not help. Message is still written through word "Debian" with same color white, and therefore unreadable. I tested it at     text_height = first_line_height * 7.5;     min_height = Window.GetHeight();     #Debug("text_height=" + text_height + "

Bug#983466: linux-image-5.10.0-3-686-pae: Black screen at dual monitor with warn from i915_gem_ww_ctx_backoff

Package: src:linux Version: 5.10.13-1 Severity: normal Tags: upstream Dear Maintainer, I am running Debian bullseye with wayland on dual monitor, above each other. I use package dash-to-dock version 69 (newest). At each dock there are 13 buttons defined to startup applications; each monitor

Bug#981572: Problem disappeared.

After recent Debian updates the problem does not exist anymore. So I think the bug can be closed. Gert

Bug#981572: pulseaudio: Pulseaudio disabling auto-mute mode

Intel, STAC9200 Analog     Direct sample mixing device dmix:CARD=Intel,DEV=1     HDA Intel, STAC9200 Digital     Direct sample mixing device usbstream:CARD=Intel     HDA Intel     USB Stream Output --===0378059268== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="bug-pulseaudio-pactl_info.x0hTKi" Server String: /run/user/1000/pulse/native Library Protocol Version: 34 Server Protocol Version: 34 Is Local: yes Client Index: 14 Tile Size: 65496 User Name: gert Host Name: debian Server Name: pulseaudio Server Version: 14.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-_00_1b.0.analog-stereo Default Source: alsa_input.pci-_00_1b.0.analog-stereo Cookie: 6cbf:3d0e

Bug#972909: insighttoolkit4 ftbfs with python3.9

python version (everything else would be insane regarding the build time and the disk space needed for building the package). If you don't object I'll now check whether the configuration error also occurs with 3.8 and lower the severity if there are no problems. Best, Gert [1] https

Bug#963667: [Aptitude-devel] Bug#963667: aptitude: Aptitude segmentation fault

ank you as well! Gert

Bug#963667: Aptitude segfault when user lacks read permission

I have the same outcome, but I don't know if it's the same cause. Anyway, I found aptitude segfaults, when the active uid cannot read some file. Reproduce: $ whoami gert $ su -c 'touch /etc/apt/preferences.d/test' $ aptitude search nouveau (works fine) $ su -c 'chmod

Bug#969395: chromium 83.0.4103.116-3+b1 crash immediately, SEGV_MAPERR

Package: chromium Version: 83.0.4103.116-3+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Chromium crashes immediately with screen awsnap errorcode 256 Log; Sep  1 20:37:43 debian dbus-daemon[439]: [system] Activating via systemd: service name='org.bluez' unit='dbus

Bug#963121: Additional analysis and suggested bugfix

Problem also occurs at systemd version 245.6-2 . Indeed I am using GNOME where the login session is managed by systemd --user. The problem is not concerning an ordinary user service, which is killed by SIGKILL after 90 seconds. There is no SIGKILL-message!! As described at the initial bug-text a r

Bug#958566: Minor comment

Andreas, thanks for the bug fix. It is working. But there still is a minor cosmetic bug, not influencing the correct working of the package. The display of an unknown card will never work, because it displays the list of unsupported cards. Besides the lspci-command also detects the wired ne

Bug#958566: Improved patch added.

Tags: patch Improved patch is included, which contains correct indentation. It also displays  more information about the chosen version of firmware. #!/bin/sh set -e # make_download_vars() { if [ -n "$latest" ]; then

Bug#959002: 959002

Thanks for your quick reply. So my only solution is using b43. I recently got severe performance problems with this, making wifi unusable. This happened after automatically upgrading to package version firmware-b43-installer_019-5 . I reported this bug with proposed fix at https://bugs.debian.o

Bug#959002: Extra info

I do not understand why this problem is marked as fixed at 6.30.223.271-14, because this just is the version I used when I got the problem. I also tested with the same laptop at ubuntu 18.04 the broadcom-sta-dkms version 6.30.223.271-8ubuntu0,1 and got the same problem there. At internet the m

Bug#959002: backports version

broadcom-sta-dkms , that gave same errors. Also restarts did not help. I have no idea this has some relation, but at April a new version of wireless-regdb is upgraded with lot of changes. 2020-04-18 23:30:05 upgrade wireless-regdb:all 2019.06.03-1 2019.06.03-3. gert@debian:/lib/firmware$ ls -l

Bug#958566: Suggested patch added

Script postinst of package firmware-b43-installer is modified to load the classic firmware for broadcom-cards, according to  note at https://wiki.archlinux.org/index.php/Broadcom_wireless#b43 Logic is added to also load the correct version, in case the firmware is unconditionally loaded. N

Bug#958566: Additional info

https://wiki.archlinux.org/index.php/Broadcom_wireless#b43 contains the next note, suggesting to use b43-firmware-classic for BCM4311 and other named cards. Package b43-firmware-classic uses  old firmware version 5.100.138. *Note:* * BCM4306 rev.3, BCM4311, BCM4312 and BCM4318 rev.2 have b

Bug#959002: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

Package: broadcom-sta-dkms Severity: grave Justification: renders package unusable Dear Maintainer, Because I recently had trouble with Wifi after an upgrade of package firmware-b43-installer, I purged this package and tried to install package broadcom-sta-dkms, according to the recently updated

Bug#958566: Wrong package name

I think it should be a bug to package firmware-b43-installer.

Bug#958566: Additional info

It is an old problem with version 6.30.163.46. See e.g. https://bugs.gentoo.org/541080

Bug#958566: b43-fwcutter: Wifi Broadcom at BCM4311 very slow after installing new firmware-b43-installer_019-5_all.deb

Package: b43-fwcutter Version: 1:019-5 Severity: grave Justification: renders package unusable Dear Maintainer, After the recent upgrade to package firmware-b43-installer_019-5_all wifi connection was extremely slow causing e.g. timeouts at Firefox. This package contains firmware version 6.30.16

Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

aster) commit 125654bfa6f99a251b581522182e85748dd8043a (release/2.4) (it will be in 2.4.10, but we're not going to do a release "just because of this patch", as this problem can always be fixed by fixing openssl.cnf :-) ) gert -- "If was one thing all people took for granted, was conviction that if you fe

Bug#956910: gnome-shell: System hangs with GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))

Package: gnome-shell Version: 3.34.4-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After today's upgrade the system hangs with GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_S

Bug#956426: plymouth: Message is unreadable at initial Debian screen on dual monitor

Package: plymouth Version: 0.9.4-2 Severity: normal Dear Maintainer, Default plymouth theme with name "futureprototype" is used. I am using 2 different monitors with size 1280 x 1024 and 1280 x 800. Message like "resuming from hibernation" is written in the middle of the text "Debian" with the

Bug#944683: FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js

/usr/share/nodejs/axios/dist/axios.min.js Best, Gert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.9-gentoo (S

Bug#941664: RM: vtk6-doc,vtk6-examples -- NBS;not built anymore

Control: -1 -moreinfo The dependency was fixed with gdcm-3.0.4-2 (just uploaded) Thanks, Gert

Bug#941664: vtk6: was the removal of vtk6-examples and vtk6-doc intentional?

Control: reassign -1 ftp.debian.org Control: retitle -1 RM: vtk6-doc,vtk6-examples -- NBS;not built anymore Yes, the removal was intentional, since vtk6 is EOL upstream and will get phased out slowly, Best, Gert

Bug#943677: please package insighttoolkit5 (5.0 and 5.1 beta 1 are out)

one rather useless python test in 4.13.1 to get it pass). Best, Gert Am Sonntag, den 27.10.2019, 16:56 -0400 schrieb Yaroslav Halchenko: > > While preparing a new package, > https://github.com/InsightSoftwareConsortium/ITK/issues/1200#issuecomment- > 524836729 > might be of

Bug#937480: pymia: Python2 removal in sid/bullseye

Hi Sandro, NMU is fine with me, as nearly all the packages in debian-med the package is lowNMU, so no delay is necessary. Maybe next time consider to send the diff as merge request on salsa, it makes it easier to apply ;) Best, Gert

Bug#942418: libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland

Package: libmutter-5-0 Version: 3.34.1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading from buster stable to bullseye testing and restarting, only a blank screen appears. Problem caused by failing wayland, which is by default enabled since debian bu

Bug#933887:

Also ran into this issue. I have created a merge request to fix this: https://salsa.debian.org/giraffe-team/kopanocore/merge_requests/6 HTH Gert

Bug#933414: ginkgocadx: Please rebuild against wxWidgets GTK 3 package

Am Mittwoch, den 31.07.2019, 12:58 +0200 schrieb Andreas Tille: > Control: tags -1 help > > Hi Gert, > > As far as I can see /usr/bin/vtkParseOGLExt exists only in vtk6. > > Could you please take over from here? sure, Gert

Bug#930277: unblock: gdcm_2.8.8-9

dependencies. With version gdcm-2.8.8-9 the symbols file is dropped again because this seem so be the only viable approach to alliviate this problem when it comes to C++ libraries. Many thanks, Gert unblock gdcm/2.8.8-9 -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500

Bug#930275: unblock: dcmtk/3.6.4-2.1

pload removes the patch introducing the port to charls-2.0 and the patch that forces the use of the system provided charls library, since the old version charls-1 is no longer in the archives. As a result dcmtk will use the bundled version. Many thanks, Gert unblock dcmtk/3.6.4-2.1 -- System Inform

Bug#554167: Updating Mawk in Debian

on https://invisible-island.net/mawk/mawk.html (Desktop and servers). I regularity write big awk scripts to process files of several gigabytes and use mawk daily. e.g.: https://github.com/ghuls/multigrep/blob/master/multigrep.sh Thanks, Gert > Hi! > > On Fri, 2018-12-28 at 11:24:44 -0

Bug#923750: gdcm: FTBFS in buster/sid

I can't reproduce this in current sid. I've did a new upload with a minior unrelated fix incorporated by Gianfranco. If this passed on the build servers, I'm going to close the bug, best, Gert

Bug#923697: imagemagick-6.q16: evaluate-sequence on different size images: crash in Buster, fine in Stretch

ersion it still works. Thank you, Gert -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org convert: ImageMagick

Bug#919193: orthanc: FTBFS with dcmtk-3.6.4

functions that take strings now also take a size parameter for each string - DIMSE_findUser now takes an additional parameter Best, Gert

Bug#915862: linux-image-4.18.0-3-686-pae: Doesn't boot/printk on Geode LX

After testing several other kernels, I think I have found the root cause: Geode LX does not support PAE. How could I have missed that, sorry for the noise. I don't know how to close this bug properly myself.

Bug#915862: linux-image-4.18.0-3-686-pae: Doesn't boot/printk on Geode LX

This kernel, from the installer, does boot: http://ftp.de.debian.org/debian/dists/testing/main/installer-i386/20181206/images/hd-media/ It has the same version numbers as the "normal" deb that doesn't boot (on which I reported). See attachment for dmesg. [0.00] Linux version 4.18.0-3-686

Bug#915862: linux-image-4.18.0-3-686-pae: Doesn't boot/printk on Geode LX

me problem. Note that the info below is while booted with the backports kernel (same commandline options etc). The info above (Subject/Version) I edited to match the nonbooting kernel. Thank you, Gert -- Package-specific info: ** Version: Linux version 4.18.0-0.bpo.1-686 ** Command line: BOOT_IM

Bug#914817: [Debian-med-packaging] Bug#914817: camitk: FTBFS on i386

Am Sonntag, den 02.12.2018, 15:45 +0100 schrieb Mattia Rizzolo: > > Guess having this bug reassigned to vtk7, and Gert uploading a fixed > vtk7. Then camitk can be finally rebuilt on i386 as well. > I made an upload of vtk7 to exprimental, there mostly because I want to see wh

Bug#911604: haveged start up fails due to apparmor denying write access to /run/haveged.pid

What helped was adding the line /run/haveged.pid w, to /etc/apparmor.d/local/usr.sbin.haveged That works, thank you. FWIW, I did not have this problem when I used systemd as init. I just switched to openrc-init, and then I did. I don't know why that would make a difference. Buster, i386, /bin

Bug#911793: Bug#914483: Control: reassign -1 src:gdcm 2.8.7-2

" is not so > relevant... after all they are different libraries, they shouldn't > mess with each other that much (there chances of it, but…). The problem is that vtk6 and vtk7 share many symbols, so linking both into the same executable is likely to create problems. [...] > Gert: yo

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

911793) did push the > autoremoval for another month (thanks to Adrian as well, as that's > exactly what is happening). > > Thank you to Mattia for finding the ABI problem and to Matthieu for > his comments. > > Thank you to Gert for the explanation about vtk7 (by the

Bug#914397: nftables: after Stretch->Buster upgrade, named set needs "auto-merge"

After analyzing my config, I can now give a full example. The subnet came from a geoblock list, the separate host came from an abusers list. That causes the conflict in Buster (which can be fixed with auto-merge). And I tried it again on a different Stretch machine, and it indeed works fine. (S

Bug#914397: nftables: after Stretch->Buster upgrade, named set needs "auto-merge"

Whoops, the "System Information" is not from the affected system, but from the system I used to write the report. So ignore that. System Information from the affected system: linux-image-4.18.0-2-amd64 4.18.10-2+b1 nftables 0.9.0-1 libnftables0 0.9.0-1 libnftnl7 1.1.1-1 libxtables12 1.8.2-2 libg

Bug#914397: nftables: after Stretch->Buster upgrade, named set needs "auto-merge"

Package: nftables Version: 0.9.0-1 Severity: normal Hi, I make use of a "named set" for blacklisting purposes. The relevant part in /etc/nftables.conf: table ip filter { set blacklist { type ipv4_addr flags interval include "/etc/ipset-black

Bug#906535: [Debian-med-packaging] Bug#906535: src:gdcm: Please support Python3

Hello Andreas, the python3 version is already in experimental, so you should be able to upload the new version of invesalius there and test it. I'll take care of the upload of the python3 supporting version of gdcm to sid when I'm back from my vacations. Best, Gert

Bug#897756: 897775 & 897756 *: ftbfs with GCC-8 (because of an error in insighttooklit4)

- checked and #897775 was indeed fixed by this version. many thanks, Gert

Bug#902766: python3.7 causing python3-twisted failure?

Am Samstag, den 30.06.2018, 18:38 +0100 schrieb Neil Williams: > Do you have python3.7 installed? A similar error was reported against > python3-pexpect with python3.7: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902646 > > 'async' is a reserved keyword in Python 3.7. > Yes, because it

Bug#902766: python3-twisted fails in the post-installation script when doing a first-time install

Apparently with the latest python-3.6 "async" can no longer be used as a variable name because it is a keyword. Best, Gert -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture:

Bug#901635: itksnap: Crashes when opening example file

o see if it also crashes when the software rasterer is used for OpenGL? Best, Gert

Bug#895246: gconf: Intent to Adopt

onf configuration, to be able to convert it to a new backend. If only for that keeping gconf for the next release cycle is a good thing, and thank you, Adrian, for stepping up to adopt the package. best, Gert

  1   2   3   4   5   >