Bug#760402: synaptic: libc upgrade always failing in synaptic

Package: synaptic Version: 0.81.2 Severity: critical Justification: breaks the whole system Dear Maintainer, when upgrading libc with Synaptic leads to a crash and to broken packages. Experienced this already with some of the last upgrades. With following steps it is reproducable on at least my

Bug#760402: synaptic: libc upgrade always failed in synaptic

Hello all, I did some more testing and found a way to reproduce it even without using synaptic: - reinstall old 2.19-9 libc files - export DEBIAN_FRONTEND=gnome - apt-get install libc6-dbg libc6-dev libc6 libc-dev-bin libc6 \ libc6-dev libc6-i386 libc6-dev-x32 multiarch-support

Bug#762417: [Pkg-libvirt-maintainers] Bug#762417: vinagre: cannot connect - libgrypt error?

Hello, found the bug being listed as release critical, so tried if I can find something out. First: It seems that vnc_connection_perform_auth_ard is only used for Apple remote desktop: VNC_CONNECTION_AUTH_ARD = 30, /* Apple remote desktop (screen sharing) */ Second @Norbert: Have you

Bug#768369: Acknowledgement ([libjpeg62-turbo] [DOS] Stack smashing)

Hello, probably the attached patch could help in diagnose the issue. It prints an error message and aborts, when the current buffer pointer is advanced past the _buffer. In debugger it shows this happens a little before what roucaries bastien in message 47 wrote. (Because he stopped at the stack

Bug#768369: Acknowledgement ([libjpeg62-turbo] [DOS] Stack smashing)

Hello, DRC suggested to have a look at the newer upstream version. In jchuff.c the buffer in question is there really grown. But only by 8 bytes. [1] When increasing by 28 bytes the stack smashing and writing beyond the buffer goes away. The resulting image looks good. (Input file from the

Bug#770005: mbuffer: dies in main on assertion err == 0

Hello, seems that the FreeBSD kernel wants the sigaction struct better initilized. With attached patch the assertion does not happen in a test vm for me anymore. Kind regards, Bernhard Description: Initialize sigaction struct Author: Bernhard Übelacker bernha...@vr-web.de Bug-Debian:

Bug#701680: [djmount] Segfault when attempting to read a file

Hello, I could reproduce an segfault at my Jessie/testing (on amd64). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd37fe700 (LWP 18338)] sock_destroy (info=info@entry=0x7fff01f0, ShutdownMethod=ShutdownMethod@entry=2) at src/genlib/net/sock.c:95 95

Bug#772898: win32-loader testing and newer fails with TRANSLATE error

Hello, probably I have found something more. I tested in a VM with a more recent windows version, therefore I cannot sure that this is the reason you saw (having to run win32-loader with compatibility set to windows 7 on a windows 8.1 32bit). I used the version from [1]. Because you already

Bug#762417: [Pkg-libvirt-maintainers] Bug#762417: vinagre: cannot connect - libgrypt error?

Hello Alex, in my attempt to get some details out of it I needed these steps: - connection to a MacOSX (Apple remote desktop) - enable fips mode - reset initialized in basic_initialization - reset thread_model in _gcry_ath_mutex_init Points 3 and 4 I had to change in debugger. Therefore I would

Bug#772898: win32-loader testing and newer fails with TRANSLATE error

Hello, just some additions. Looks similar to bug #654380. (There mingw defaulted to produce dlls depending also on some other mingw dlls) There the upstream bug report [2] mentions that plugins must not depend on a shared libgcc. So I assume that the plugins must not depend on a shared

Bug#772956: tlsdate: FTBFS on recent MIPS kernels

Hello, I could reproduce the build error in a qemu mipsel VM (installed from [1]). Also I found that in the chromiumos repository a patch from Ben Chan is applied which seem to just fix this issue [2][3]. (Otherwise this fork seems stuck at version 0.0.5.) With this patch applied the package at

Bug#771671: /sbin/kexec: Unable to load kdump kernel on i386

Hello, I tried to reproduce the issue in a i386 qemu VM and think I found something. Function is_crashkernel_mem_reserved tries to search for the start and end of the crashkernel reserved memory area. This is done by calling kexec_iomem_for_each_line and given a callback function as parameter.

Bug#741464: grub-pc-bin: hangs after displaying boot menu

Hello, I tried if I could reproduce this issue. (In my setup there is a tftp delivering grub installed by grub-mknetdir) I could not get it to hang by terminal_input at_keyboard. But similar to what Jeroen Dekkers described I was not able anymore to enter sane text with the keyboard. It feels

Bug#768369: Acknowledgement ([libjpeg62-turbo] [DOS] Stack smashing)

A small addition to the test case in Message #114: In test-768369.c lines 193 and 194 are swapped therefore an undefined value is given to malloc. When cleaning up this leads to a crash as now the stack smashing is fixed. Kind regards, Bernhard -- To UNSUBSCRIBE, email to

Bug#775235: Repeatable failure to start on i386 running under kvm

Hello, came across launchpad bug #1360241 [1] which discusses the same error. There it comes from ubuntu-ui-toolkit tests. There they did revert their mesa package to depend on llvm-3.4 instead of llvm-3.5. So did I and recompiled mesa to use llvm-3.4 (see attached patch). And with these

Bug#775235: Repeatable failure to start on i386 running under kvm

Hello, tried to reproduce it by following steps: - installed on amd64 host with qemu-system-i386 [1] and CD1 [2] and network mirror with Gnome desktop and ssh server. - got the same message Oh no! Something has gone wrong. (see attached picture) Tried to debug into the issue: # start VM

Bug#775235: gnome-shell not starting with gdm3/mesa/llvm-3.4 but does start from startx lightdm regardless

Hello Philip, probably your case is more an example for the problem described in bugs #770130 and #776911. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770130 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776911 When you rebuilt your mesa packages did you apply the patch

Bug#779312: freerdp-x11: Segfaults on start 100% of the time

Hello John Goerzen, I was able to reproduce a crash with xfreerdp. First a question: does the crash still happen, if you omit this part of the command line: --plugin rdpsnd --data alsa latency:100 -- --- After installing the 5 *-dbg packages I get such a stack: gdb --args

Bug#775235: Repeatable failure to start on i386 running under kvm

Hello, first a question about this merging with bug #770130 and #776911. These bugs seem to happen on real hardware with some intel graphics card and giving an error: *ERROR* pipe A underrun. But bug #775235 was explicitly opened by Steve McIntyre to be run inside a i386 KVM and gives an

Bug#783082: linux-image-3.16.0-4-586: video players/browsers crash with 'illegal instruction' on i586

Hello hikaru, just saw your report and tried if I could reproduce your issue. But probably you want to reproduce these steps on your hardware to verify that this is really the issue on real hardware. These steps I tried to reproduce: - install a qemu virtual machine with current jessie with

Bug#783389: hbro segfaults

Hello, tried to reproduce the issue: Without debug symbols installed this stack is visible: (gdb) bt #0 0x083b6518 in ?? () #1 0x083ae0ed in ?? () #2 0xb4dda944 in __gmpz_init () from /usr/lib/i386-linux-gnu/libgmp.so.10 #3 0xac38b11c in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28

Bug#784166: widelands: Game crashes on song change

Hello Alex, One last question: did you try to install the amd64 version specifically? I'm not sure how the multi-arch support works these days. If not, would it be easy for you to try to do it? Yes, my tests were done on my regular amd64 desktop installation. That was with

Bug#784166: widelands: Game crashes on song change

Hello Alex, just hearing that this game exists I tried to reproduce it. I installed widelands 1:18-3+b1 from jessie and started it and could not get it to crash on serveral song changes. But as your report suggests you are running Squeeze with some packages from Jessie? If this situation

Bug#784647: libav-tools: avconv fails with Illegal Instruction

... forgot the patch. Description: Optimize of i386 changed from 686 to 586. Similar to the patch patches/0011_optimize_i486.patch in wheezy by Nobuhiro Iwamatsu. Upstream moved the location from CMakeLists.txt to cmake/OpenCVCompilerOptions.cmake. Author: Bernhard Übelacker

Bug#784647: libav-tools: avconv fails with Illegal Instruction

Hello Vittorio, I could reproduce it inside a qemu VM (-cpu pentium). --- (without debug information) Program received signal SIGILL, Illegal instruction. 0xb6691c34 in ?? () from /usr/lib/i386-linux-gnu/libopencv_imgproc.so.2.4 (gdb) bt #0 0xb6691c34 in ?? () from

Bug#785248: wxhexeditor: Fails to run, suggesting download of new version

Hello Peter, (not being the maintainer I tried to reproduce) By removing from ~/.wxHexEditor the line LastUpdateCheckTime=1.4316e+09 I could reproduce the opening of the update checking window. But in Jessie/KDE I am able to simply close this window with the X in the window bar and then the

Bug#785484: systemd: on Raspberry pi B+, several essential services fail, including systemd-logind

Hello Christian, Am 19.05.2015 um 01:17 schrieb Christian Kastner: But TTBOMK, cgroup-bin never shipped an /etc/init.d/cgroup-bin file. See for example its contents in wheezy [1], or the TODO item [2] created by the previous maintainer. I think I found it here: $ dget

Bug#785356: xrdp Oh no! Something has gone wrong. is back

Hello, this issue is probably a duplicate of [776746]. See especially message #91. For a simple explanation see [1251281], message 31. [776746] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776746 [1251281] https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281/comments/31

Bug#785356: xrdp Oh no! Something has gone wrong. is back

Hello Joachim, just a small addition: to some extend I could get resolution to e.g. 1024x768 by some commands xrandr -s 1024x768 in a row. When the resolution in ~/.config/monitors.xml is modified, then it does not resize and is quite usable. (If one takes the risk of using a self built

Bug#795616: dvbcut: Illegal changelog date format

Hello Chris, I am sorry for this this mistake. I assume you tried to build dvbcut for the current gcc transition on testing/unstable where you got an error as following. # dpkg-buildpackage Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.20/Time/Piece.pm line 469, $filehandle line 12. I

Bug#795616: dvbcut: Illegal changelog date format

Opened this RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795754 Kind regards, Bernhard

Bug#793089: dvbcut: FTBFS against ffmpeg

Hello, I added Andreas Cadhalpun's patch to the package and put it on mentors.debian.net [1]. Also I filed a request for sponsorship in #793156 [2]. [1] https://mentors.debian.net/package/dvbcut [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793156 Kind regards, Bernhard -- To

Bug#852659: [le-dico-de-rene-cougnenc] segment fault

Hello Sandro, Am 08.02.2017 um 01:24 schrieb Sandro Tosi: > Hey Bernhard, > would be interested in preparing a NMU package with your patches > included (feel free to reply to me in private if you need instructions > on how to do that)? alternatively i'd be happy to NMU this myself I tried to

Bug#852018: zapping: Segfaults immediately

Hello Helge, net being the zapping maintainer, I just tried to have a look at it. It looks like alloc_aligned does truncate the pointer to 32 bits. Therefore storing the original pointer, for being able to free it later, fails. common/alloc.c: 37 p = (void *)(((long)((char *) b +

Bug#852659: [le-dico-de-rene-cougnenc] segment fault

Hello, not being the maintainer for this package, I just tried to have a look at it. 1043 *str = EquivalTable[ *str++ ] ; To me it looks like in the past the compiler did the assignment to the unincremented str. Today str gets first incremented, then *str assigned the element

Bug#853171: segmentation fault when disabling a screen with kscreen without upower installed on the system

Hello, I tried to debug this issue and spent "some" time to it. --- The class ShellCorona contains a QMap m_desktopViewforId storing pairs of idx and desktopViews pointers. When a display gets deactivated the method ShellCorona::removeDesktop [1] is called with parameter desktopView.

Bug#860393: Segfaults on startup

Hello, just tried if I can reproduce the issue. I think this is a again a case of a pointer truncation by default int for a pointer returning function. First patch is just to build with debug information to make the automatic dbgsym packages helpful. The second patch adds some includes to get

Bug#860751: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Hello, this seems to be the same problem seen in #391051 for regular expressions (collect_RE). In this bug we overrun the size limit of string_buff (tempbuff._string_buff) in function collect_string. Attached patch adds a similar check like in #391051 to collect_string. With that applied the

Bug#858316: confirm the bug on 32 bit machine

Hello, tried to have a look at it. Program received signal SIGSEGV, Segmentation fault. 0x80015110 in mount () (gdb) bt #0 0x80015110 in mount () #1 0xb7f8ff03 in fuse_mount_sys (mnt_opts=0x800163a8 "rw,nosuid,nodev", mo=0xb398, mnt=0x80016288

Bug#858037: ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault)

Hello, tried to get some more information from the crash. # IKARUS_SRC_DIR=. IKARUS_BUILD_DIR=. IKARUS_FASL_DIRECTORY='' IKARUS_LIBRARY_PATH=.:.:./../lib gdb -q --args ../src/ikarus -b ./ikarus.boot.4.prebuilt --r6rs-script ./makefile.ss Reading symbols from ../src/ikarus...done.

Bug#852532: olvwm: source code not 64-bit clean, SIGSEGV everywhere

Hello, I continued debugging from looking at #855167 and came up now with the 6 attached patches. With these applied olwm and olvwm are not crashing anymore inside my minimal test vm. Probably you want to give them a try. > Unless there is an automated way to identify all the cases of >

Bug#855167: olwm crashes trying to log in X

Hello Awtul, not being the maintainer for olwm I tried to shed shome light to it and describe some ways to get more informations out of it. (Even when olwm got removed from testing.) First one can install the systemd facility to collect coredumps: apt install systemd-coredump gdb

Bug#847651: doomsday: Segfaults at startup

Hello, tried to reproduce the issue. I think the problem is that in de::File::parent the method maybeAs() is called on a NULL pointer. With the attached patch the crash does not happen. Kind regards, Bernhard # apt install doomsday doomsday-dbgsym doomsday-common-dbgsym $ gdb -q --args

Bug#860751: mawk: segfaults on i386 during win32-loader build

Hello Thomas, sorry for the late reply. I tried to compare the mawk_1.3.3.orig.tar.gz from the current package and it compares best to the initial commit in mawk-snapshots [v1_3_3] from 2008. (Without debian directory and different VCS tags.) Since then the package just collected some patches on

Bug#897390: xwayland: Segmentation fault loading GNOME 3

tags 897390 = moreinfo quit On Wed, 02 May 2018 02:09:08 +0200 Manolinux wrote: > #1 0x7f7cd8902231 in __GI_abort () at abort.c:79 > #2 0x5642194aaa5a in OsAbort () > #3 0x5642194b0573 in ?? () > #4 0x5642194b1395 in FatalError () > #5

Bug#904692: seahorse: Segfault few seconds after start

Hello Tobias Bengfort, I tried to reproduce by just starting seahorse in a VM, but the crash did not happen here. Probably you can follow the steps in [1] to locate where the crash happens? [1] https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard

Bug#893167: Stack smashing protection trigged in eboard

Hello, just tried to reproduce the stack smashing. It looks like the variable "gdouble c[3];" in colorb_csok needs to be a "gdouble c[4];". Did not find an related upstream ticket, neither in old SF nor at Github. Also at Github this function was not yet changed, so this should be forwarded to

Bug#897707: arrayfire: ftbfs with GCC-8

Hello, just tried to have a look at #892288 but got stopped by this one. Upstream handled this issue in [arrayfire/2148] and [arrayfire/2149]. Unfortunately this patch does not apply. Also the pull request mentions another change is needed in the boost library [boostorg/776]. Kind regards,

Bug#892288: arrayfire FTBFS on i386: test segfaults

Hello, tried to reproduce this, but unfortunately it fails to build against gcc-8, for which #897707 is already open. Therefore tried to reproduce it with gcc-7. I think this is what happens: - test Asssign_LinearAssignGenSeq_Test::TestBody allocates a buffer - buffer gets deleted - the same

Bug#889878: closed by Picca Frédéric-Emmanuel (Bug#889878: fixed in hkl 5.0.0.2449-1)

Hello, tried have a look at this crash. The hkl-5.0.0.2449/Documentation/figures/.libs/sirius executable makes use of makecontext/swapcontext to execute function trajectory_gen_generator__. But it looks like the argument given to makecontext got truncated to 32 bits. So I looked for

Bug#907228: kaffeine: FTBFS with Qt 5.11

Hello, this might be fixed by upstream commit [1], connected to this upstream bug [2]. Unfortunately not yet contained in an upstream release. [1] https://cgit.kde.org/kaffeine.git/commit/src/dvb/dvbdevice_linux.cpp?id=06b78c5f24891fd38d25ed64f5029106eec7c4fb [2]

Bug#898535: Incompatible ABI change without SONAME bump

Hello, this looks like it affects package mediainfo [1] too. Kind regards, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903054

Bug#891778: zatacka crashes on map selection

Hello, tried to reproduce this crash in a Stretch amd64 VM. It wants to open the directory "maps": benutzer@debian:~$ strace -f zatacka 2>&1 | grep maps open("maps", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) Therefore a null pointer is handed to

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, > Unfortunately, the 17.12.3-1 version is no more available in the > archive, apart from the hurd architecture. So I will wait for a newer > version (I am not going to compile it myself). If one needs old package versions you have a look at snapshot.debian.org [1]. As far as I

Bug#910571: qemu-user-static i386 (and x86-64) on armel host errors while loading shared libraries (Bug #910571)

Hello, not being the maintainer I just found it interesting to investigate... This message seems to be printed while it wants to load libc.so.6 into the process, and is just printed if there is not yet a "/etc/ld.so.cache". Then it has a handling to be able to load some hardware optimized

Bug#904692: Fwd: seahorse: Segfault few seconds after start (Bug #904692)

Hello Tobias Bengfort, I am sorry, but unfortunately I missed to add you to the recipients lists in July. Kind regards, Bernhard Weitergeleitete Nachricht Betreff: Re: seahorse: Segfault few seconds after start Datum: Sat, 28 Jul 2018 13:56:10 +0200 Von: Bernhard Übelacker

Bug#910394: sqlcipher: Crashes on running any SQL Statement (Bug #910394)

Hello, just trying to reproduce the crash, but it does not happen for me with the sequnce from the man page like below. Could you probably provide some more information. Either an minimal example database and selects that triggers the crash. Or just a backtrace from an attached debugger. You find

Bug#909926: multipath-tools: multipath segfaults regularily (Bug #909926)

Hello Axel, what CPU is inside the machine producing this cores? Could you please check if your CPU supports avx2 instructions. If an internet search tells me right this line should show "avx2" for each core if yes: grep -o 'avx[^ ]*' /proc/cpuinfo Kind regards, Bernhard

Bug#911242: grub-legacy - Fails to install on disk (Bug #911242)

Hello Bastian Blank, might this crash be the same as reported in #898553 ? Kind regards, Bernhard

Bug#910571: qemu-user-static i386 (and x86-64) on armel host errors while loading shared libraries (Bug #910571)

Hello all, attached a try to minmize the testcase to just the affected instruction. Kind regards, Bernhard /* bernhard@rechner:~$ uname -a Linux rechner 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64 GNU/Linux bernhard@rechner:~$ gcc -m32 -g -O0 -static 910571_test_2.c -o

Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module

Hello Massimo, Am 24.10.2018 um 15:54 schrieb Massimo MANGHI: > ... and the new patch will be > included in the next upload, is it correct? Am I supposed to take any > further action? Something like changing the bug status or applying some > extra tag to the bug in order to specify the

Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module (Bug #911680)

Hello Massimo Manghi, just tried to reproduce the issue inside a debian buster amd64 qemu VM. I never hit the crash and found you were probably running inside a VirtualBox. Nevertheless with installed debug informations I think the crash shown in the Xorg.log points to that location: (gdb) bt

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

Hello Alex Andreotti, just tried to reproduce this issue but did not happen inside my unstable amd64 qemu VM. Probably you can install an core dump collector like systemd-coredump? Then you could see the stack where the crash happened by: coredumpctl gdb list coredumpctl gdb And even

Bug#911946: Bug #911946: rc-status: double free or corruption (!prev)

Hello Mo Zhou, I just tried to reproduce the issue and thats my findings: ... corrupted double-linked list Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht

Bug#911946: Bug #911946: rc-status: double free or corruption (!prev)

Just for reference attached some notes how to switch to openrc and some debugging attempts. # switch to unstable nano /etc/apt/sources.list apt update apt dist-upgrade apt autoremove reboot nano /etc/default/grub # remove quiet # add init=/sbin/openrc-init update-grub apt install initscripts

Bug#913014: Bug #913014: e3 (all binaries): immediate segmentation fault

Dear Maintainer, just tried to reproduce this issue. I suspected this is caused by some changes in the linux kernel, as a up to date buster amd64 userland inside a qemu VM with following kernel shows no problem: Linux debian 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64

Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.

Hello all, tried to reproduce and still receive the crash triggered by either SVG import or the manual action in the python console. The parameter --enable-system-expat seems to just defines HAVE_SYSTEM_EXPAT, which seems not used later. Attached patch makes coin3 not to build the subdirectory

Bug#906609: fixed in gnucash 1:3.3-1

Hello Dimitry, I saw that a version 3.3-1 got uploaded so I had a look at the build logs, but found some of them failing with this error: /<>/libgnucash/engine/gnc-timezone.cpp:55:22: error: operator '!' has no right operand #if ! WORDS_BIGENDIAN ^ I fear this happens

Bug#910634: spice: FTBFS on all architectures (Bug #910634)

Hello Salvatore Bonaccorso, just tried to find some information without deeper knowledge of spice or openssl. In the end I think the update of openssl from 1.1.0h-4 to 1.1.1-4 makes the difference. Since some 1.1.1 version /etc/ssl/openssl.cnf seems to contain: CipherString =

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, just came around and found this could be related to that bug report [1], related to package libkf5kontactinterface5. Kind regards, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910581

Bug#907862: gtkpod segfaults on startup

Hello, just tried to get some more information from this backtrace. This is what I assume the last frames look like when not optimizing: g_type_check_value_holds playcounts_plist_read, line 1115 playcounts_init itdb_parse_internal ... main playcounts_plist_read: ...

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

Hello Emmanuel, I made a mistake and did my first investigations on testing instead of unstable. So my findings of my first mail are unrelated (but hope they still help). So I did another try and got all tests fail like in the reproducible build log. Something bad happens in these lines: (gdb)

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

modeling/libraries/pml/MultiComponent.h:134 129 } 130 inline void MultiComponent::removeSubComponent(Component* c) { 131 auto it = std::find(components.begin(), components.end(), c); 132 if (it != components.end()) { 133 components.erase(it); 134 c->

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

Hello Christoph Anton Mitterer, I just tried to reproduce this issue. It looks like this issue got introduced in upstream commit [1]. There an error message got added that leads to an immediate process exit. This error is shown when file /usr/share/tracker/domain-ontologies/default.rule is not

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

Hello Christoph Anton Mitterer, this issue seems a duplicate of bug #908800. Kind regards, Bernhard

Bug#892871: tome: Segfaults when started

Control: reassign 892871 libasan4 7.3.0-5 Control: found 892871 7.3.0-12 Control: fixed 892871 7.3.0-13 Dear Maintainer, did some tests with snapshot.debian.org and found that crash does not happen anymore since libasan4:i386 (7.3.0-13). Kind regards, Bernhard

Bug#918339: dovecot-mysql: dovecot/auth segfaults with double-free in mysql_close() / passdb_deinit()

Hello Dominik Röttsches, the missing debug symbols for libmariadbclient.so.18 might hide in libmariadb3-dbgsym. You may also want to install these packages too: dovecot-core-dbgsym dovecot-mysql-dbgsym They should be available in a different debug symbol repository described in [1]. I had a

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, I missed that, sorry about that. On Mon, 26 Nov 2018 15:22:39 +0100 =?utf-8?Q?Francesco_Potort=C3=AC?= wrote: > >can you still observe the crash, or got it fixed by updates > >in mid October? (Like mentioned in #910581) > > It does not crash any more, ... So the initial

Bug#918014: apache2: Segfault in mod_filter only wehen started by systemd

Hello Dominik George, might this be also caused by "libcap-ng's use of pthread_atfork causes segfaults" [1]. A version of libcap-ng that should fix that issue should hit testing the next days. Maybe you can check if this fixes the crash you reported, too, or if it is a separate one? Kind regards,

Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

Hello Francois Marier, this looks like a duplicate of bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919765 Kind regards, Bernhard

Bug#914565: php7.3-intl: Segfaults after apache2 graceful restart

While looking into #915642 I found that this bug might just be another case of bug #904808. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808 Kind regards, Bernhard

Bug#915642: AuthBasicProvider PAM crashes apache

Dear Maintainer, I just tried to reproduce and found it crash on service startup when using the given /etc/apache2/sites-enabled/default.conf. It looks like here the apache2 process wants to fork and calls the fork_handlers. Unfortunately one of them belongs to an unloaded module. Therefore we

Bug#917018: wget: Unusable - permanent segmentation fault

Hello rwpenney, just tried to reproduce and collect some information for the maintainer on a minimal buster amd64 qemu VM. Unfortunately I could not reproduce the crash and after 700 files I stopped my test. Maybe you could run the wget command like that: gdb -q -ex 'set pagination off' -ex

Bug#917018: wget: Unusable - permanent segmentation fault

Control: fixed 917018 wget/1.19.1-1 Control: tags 917018 + upstream Dear Maintainer, hello RW Penney, I had a look and think I found something. You have by any chance made something like 'chmod 000 ~/.wget-hsts' ? Because in that case we end up in a backtrace like below. (And stretch systems

Bug#914616: Fixed by latest binNMU

Control: notfixed 914616 20181001.4.a99aaec~ds6-2+b1 Hello Petter Reinholdtsen, in another bug I got told that BTS is not handling binNMU versions, therefore ending up with fixed+found versions being the same (915364). Maybe that is also the case here why the autoremoval stays. Let's try to just

Bug#911084: Bug #911084: sagemath crashes as cantor backend

Hello kinky nekoboi, Am 01.12.2018 um 13:45 schrieb kinky_nekoboi: > is there any progress on this? no more progress that I am aware of, just tried to reproduce and collect some information. Kind regards, Bernhard

Bug#915364: Bug #915364: qbittorrent again crashes when starting talks of symbol lookup error

Hello Martin Haase, > ii libtorrent-rasterbar9 1.1.9-1 You probably have also to update your libtorrent-rasterbar9 package to version 1.1.9-1+b1. libtorrent-rasterbar (1.1.9-1+b1) sid; urgency=low, binary-only=yes * Binary-only non-maintainer upload for amd64; no source changes. *

Bug#915364: qbittorrent again crashes when starting talks of symbol lookup error

Dear Maintainer, sorry, tried to mark it as fixed in the rebuild 1.1.9-1+b1. But cont...@bugs.debian.org processed just version 1.1.9-1. Kind regards, Bernhard

Bug#916060: tuxmath: Starts and immediately closes

Dear Maintainer, I just tried to reproduce and collect some more information, used a minimal buster amd64 qemu VM. This issue seems to be more located in libt4k-common0. It uses "rsvg_handle_get_desc(file_handle)" to retrieve a char pointer to the description and tries to convert that into an

Bug#911084: Bug #911084: sagemath crashes as cantor backend

Dear Maintainer, hello Kinky Nekoboi, just tried to reproduce this issue and there is really a crash. In a minimal buster amd64 qemu VM, with installed cantor and cantor-backend-sage packages. Then follow these steps: - start cantor - select Sage backend - enter in the field below the "Session

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, can you still observe the crash, or got it fixed by updates in mid October? (Like mentioned in #910581) If it is fixed that bug might be closed. Kind regards, Bernhard

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, can you still observe the crash, or got it fixed by updates in mid October? (Like mentioned in #910581) If it is fixed that bug might be closed. Kind regards, Bernhard

Bug#906609: fixed in gnucash 1:3.3-1

Am 22.11.2018 um 23:15 schrieb Dmitry Smirnov: > On Thursday, 22 November 2018 9:50:02 AM AEDT Chris Lamb wrote: >> grep-excuses claims: >> >> missing build on armel: gnucash, python-gnucash (from 1:2.6.19-1) >> missing build on mips: gnucash, python-gnucash (from 1:2.6.19-1) >> >> Is

Bug#914565: Bug #914565: php7.3-intl: Segfaults after apache2 graceful restart

Hello Dino, if possible you might want to install the package php7.3-intl-dbgsym matching to your php7.3-intl. That is in a separate repository [1]. Then that last frame should show up in the debugger with a function name and line of source code. Kind regards, Bernhard [1]

Bug#906609: fixed in gnucash 1:3.3-1

On Fri, 23 Nov 2018 00:26:28 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: > but I cannot make a clue out of the > armel "Not-For-Us" [1] for the build dependeny guile-2.2. > What does that mean? Hello Dimitry, hello Chris, I just stepped over the answer to "Not-For-Us" in [1] and [2] for the

Bug#914565: Bug #914565: php7.3-intl: Segfaults after apache2 graceful restart

Hello Dino, I tried to have another look at this issue. > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') I found your report claims you are running testing, but php7.3-intl 7.3.0~rc5-2 is currently just in unstable. Are there more packages installed from

Bug#920467: ngraph-gtk: fails at runtime on 32-bit archs

Control: tags 920467 + upstream patch Dear Maintainer, tried to have a look at the stack smashing. It happens inside a call to g_stat/stat64. The reason is as far as I see that in nconfig.c the type GStatBuf has just a size of 88 bytes, therefore no more memory is reserved. Inside nstat or

Bug#925483: tilda: does not start (segfault)

Hello Guenter Grodotzki, I am not the maintainer for tilda, just got here and tried to collect some more information. For some reason your upstream report contains one (interesting) lines more than made it into the debian report. Just as a hint: the real important information has to be queried

Bug#926212: gnome-shell crashed (segfault)

Hello Guenter Grodotzki, I just tried to help triage that issue. For some reason you just added the segfault line. I assume there was one line following starting with "Code:". Please add that line too when submitting bugs. As this information is still kind of small, you might consider to install

Bug#926351: python3-tesserocr: segfaults on import

Dear Maintainer, just tried to help triaging this issue. Seems this is "expected" behaviour with LC_ALL not set to "C". In the end it leads to this upstream bug: https://github.com/sirfz/tesserocr/issues/165 It contains some workarounds and more information. Kind regards, Bernhard #

  1   2   3   >