Package: qtcreator-data
Version: 3.2.0+dfsg-1
Severity: minor
Tags: l10n
Dear Maintainer,
I updated lately qtcreator to latest version in Jessie.
Since then, I assume, the ui translations get not shown on my system.
Instead the user interface stays with builtin texts.
qtcreator 3.0.1+dfsg-1 was
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 sy
Hello,
patch got applied upstream [1] and is contained in new release version 10.3.
There are already packages for 10.3 in unstable.
[1]
http://git.libav.org/?p=libav.git;a=commit;h=dc71f1958846bb1d96de43a4603983dc8450cfcc
Kind regards,
Bernhard
--
To UNSUBSCRIBE, email to debian-bugs-dist-re
Package: kexec-tools
Version: 1:2.0.7-3
Severity: important
Dear Maintainer,
* What led up to the situation?
- Updating kexec-tools from 2.0.4-1_amd64 to 2.0.7-3_amd64
- interactive shutdown by the KDE menu.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Am 30.09.2014 17:54, schrieb Michael Biebl:
>> But to the user it is neither shown how long systemd is waiting
>> until signal SIGKILL is sent or which process caused this delay.
>
> This is also fixed in v215. systemd will show how long the timeout is
> and how much time has already passed.
>
>
Am 30.09.2014 19:25, schrieb Michael Biebl:
> Am 30.09.2014 um 19:10 schrieb Bernhard Übelacker:
>> Will try with a test system.
>
> Ah right. Missed that part. Can you rebase the patch on top of v215
> and maybe also post it upstream for review (either mailing list [1]
&
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 conf
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
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 fir
Hello,
in my opinion this is caused this way:
- synaptic calls vte_terminal_forkpty which calls __vte_pty_fork
- Now we have a parent process which gets in the variable pid the pid of
the child process. A call to vte_terminal_watch_child is needed and
gives no warning.
- But also we have now th
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
Bug-Debian: https://bugs.debian.org/770005
Hello Tokarev,
Am 30.01.2016 um 12:04 schrieb Michael Tokarev:
However I see one interesting difference between our setup.
What is your screen size, and desktop area size? On your video,
the VM window size is close to your desktop size. I remember
seeing some strange effects when the VM windo
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
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 hint
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 s
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 libwin
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 l
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.
U
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 li
Hello,
some small additions:
I cannot reproduce it anymore with xine-ui.
And more important, another workaround is to start with this environment:
$ VDPAU_NVIDIA_NO_OVERLAY=1 kaffeine
But unfortunately then I think tearing gets visible.
>From the nvidia driver readme [1]:
Both the overlay and
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 debian-bugs-dist-req
;xconfigure.event != xevent->xconfigure.window
? " (discarding substructure)"
- : ""));
+ : ""/*)*/);
if (window && GDK_WINDOW_TYPE (window) == GDK_WINDOW_ROOT)
{
window_private->width = xevent->xconfigure.width;
Des
Hello Michelle Konzack,
not being maintainer I was just curious about
this problem, so I tried to reproduce ...
- Installed a amd64 Wheezy VM
- Inside installed cups-pdf printer.
- Changed in /etc/cups/cupsd.conf from "LogLevel warn" to "LogLevel debug"
Then following commands led not to the same
Hello,
tried to debug it in a VM.
# apt install moc-dbgsym
$ gdb -q --args mocp
Reading symbols from mocp...Reading symbols from
/usr/lib/debug/.build-id/a2/ee23893fc19ab8924a10916a485b2a9c478e7c.debug...done.
done.
(gdb) set width 0
(gdb) set height 0
(gdb) run
Starting program: /usr/bin/mocp
Hello,
it seems that the value that start to lead to wrong values is 2048M.
Also the returned hash from there is always the same as for an empty file.
I first thought it has something to do with large file support, but it
looks like that is already enabled.
(gdb) print sizeof(off_t)
$1 = 8
Hello,
not being the maintainer I just tried to reproduce the issue.
I received the segmentation fault, but unfortunately in some
"Interface wrapper code" "Generated by SIP", that seems also
not contained in the dbg package:
# coredumpctl gdb
(gdb) bt
#0 0x in ?? ()
#1 0xb3da30f0 in ca
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
Hello,
tried to reproduce the issue.
I think the problem is that in Cl_IsClientMobj the method maybeAs()
is called on a NULL pointer on mo->thinker.d.
With the attached patch the crash does not happen.
And this time I took the opportunity to play in
doom1-share.wad and doom2.wad (just short) and
Package: git-gui
Version: 1:2.11.0-3
Severity: normal
Tags: patch
Dear Maintainer,
using "git gui" to "Amend Last Commit" scrambles the
"Author" name in the commit, if the name contains at least a "Ü".
A "new" commit is not affected. But on every amend it gets
scrambled more.
New: From: =?UT
Package: kexec-tools
Version: 1:2.0.14-1
Severity: wishlist
Dear Maintainer,
trying to get kdump-tools in place I found that in Stretch
using the kernel in stretch-backports (4.12.6-1~bpo9+1)
I get following error:
Sep 14 21:02:11 rechner systemd[1]: Starting Kernel crash dump capture
service
Hello,
I installed a Thinkpad T60 last year around 16.19.2016 with Debian Testing.
With the kernel contained at that time suspend to disk was working well.
(linux-image-4.6.0-1-686-pae 4.6.4-1, [1])
Just recently I got this system back and upgraded it to current Stretch.
(linux-image-4.9.0-3-686-
Hello,
upstream applied Nicolas George's patch and released version 31
some days ago.
I hope it is not too late for stretch?
As I own an affected device I would like to supply some more
informations and workarounds to people with similar devices.
Kind regards,
Bernhard
-
- Calling efibootmg
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 p
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 "/home/benutzer/rdiff-backup-fs-test/mnt"
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 bui
Hello Pino Toscano,
thank you for taking care for this report.
May I still ask what I should do for the other packages in Stretch,
that are still built using an old 0.9.0*-lirc version and are
probably suffering from the same crash as this report is about?
Get they rebuilt automatically before St
Hello Michael,
I am sorry, but my old address got shut down.
On Wed, 21 Dec 2016 19:30:10 +0100 Michael Biebl wrote:
> just wanted to ask, if you still run into this issue with a newer kernel
> (from testing). If so, I think it would probably best to re-assign this.
>
> Regards,
> Michael
Unfo
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 + al
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
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "dvbcut"
* Package name: dvbcut
Version : 0.7.1-1
Upstream Author : Bernhard Übelacker
* URL : https://github.com/bernhardu/dvbcut-deb
* License
Hello James,
sorry for the late reply.
I prepared a new version removing mplayer2 and opened a RFS in [1].
Thanks,
Bernhard
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844734
Am 18.11.2016 um 18:08 schrieb James Cowgill:
> On 18/11/16 14:28, Bernhard Übelacker wrote:
>> Hello James,
>> sorry for the late reply.
>>
>> I prepared a new version removing mplayer2 and opened a RFS in [1].
>
> Why did you remove mpv?
Hello James,
becau
--buildsystem=autoconf --with=autoreconf,autotools-dev --parallel
>
> this is useless with compat level 10 (at least it should be)
> please bump compat to 10 and debhelper >=10 :)
> also, consider dropping them as build-dependencies
>
>
> [ Bernhard Übelacker ]
>
>
notfound 850073 0.73.0
found 850073 0.7.0-1
thanks
Hello Dave,
sorry for the delay.
I got a little distracted by creating a hppa chroot ...
I assumed version 0.73.0 was just mixed up from the sbuild version,
so I am trying to change it to 0.7.0.
Due to [2] there is currently a version 0.7.1-1
On Wed, 19 Jun 2024 18:19:59 +0100 Peter Green wrote:
Package: pesign
Version: 116-7
While working on the time64 transition in raspbian, I discovered pesign failing
to build with a linker error.
> cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/pesig
On Sun, 30 Jun 2024 18:28:17 +0200 Michael Saxl wrote:
Hello,
just in case it would be of any help to clearly see where
the allocation takes place.
Attached file contains my steps to reproduce the crash in a minimal trixie VM.
And shows the allocation from jemalloc and the free from glibc:
Kin
On Wed, 17 Jul 2024 18:43:24 +0200 Steffen Weinhart
wrote:
So the solution (or workaround) is to lower the nofile hard limit.
Just reduced it to 8192:8192 for ktorrent (and kate as well), and
suddenly it works again.
But should this be the final solution? Does kioslave really need to (try
t
Am 10.05.24 um 04:13 schrieb Alban Browaeys:
On Mon, 19 Apr 2021 16:31:34 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
mailto:bernha...@mailbox.org>> wrote:
> Dear Maintainer,
> I tried to have a look and I could reproduce the crash [1].
>
> I think this is caused by a call to gtk_list_store_se
On Fri, 19 Jul 2024 14:49:25 +0200 Ulrich Teichert
wrote:> Package: libsofthsm2
When using OpenSSL 3.0.13 (installed by the latest security update for OpenSSL),
signing with pkcs11 fails with a segmentation fault. This is not the case with
openSSL OpenSSL 3.0.11. Maybe the library just needs a
On Sat, 20 Jul 2024 17:28:59 +0200 "Francesco Poli (wintermute)"
wrote:
Dates and times seem to be completely wrong, but the system clock is OK:
Hello,
I just tried to debug the issue and found this is caused by the line below.
src/wtmpdb.c:
365 uint64_t login_t = strtoul(argv[
Am 27.07.24 um 16:14 schrieb Francesco Poli:
P.S.: If anyone is curious about what I do not fully understand, here's
my naive reasoning: the strtoull(3) man page states that strtoull
returns an 'unsigned long long' (which is guaranteed to be at least 64
bit wide, but could be wider than 64 bit o
Hello,
On Wed, 08 Nov 2023 20:17:49 +0100 =?utf-8?q?Andr=C3=A9_Offringa?=
wrote:
$ gmemusage
realloc(): invalid next size
Aborted
Looks like caused by having not enough space
for process names longer than 13 characters.
A package built with the modification below
shows no longer this crash
Package: kio-extras-data
Version: 4:23.08.4-1
Severity: normal
X-Debbugs-Cc: buebelac...@mailbox.org
Dear Maintainer,
I upgraded lately an i386 installation to Bookworm and tried to
access files on a connected Android phone.
Unfortunately there was not visible response from the UI when
clickin
On Sun, 26 May 2024 22:36:53 +0200 Marcel Partap wrote:
tmux:
Installed: 3.4-5
Candidate: 3.4-5
Version table:
*** 3.4-5 510
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
510 http://ftp.de.debian.org/debian unstable/main amd64 Packages
500 http:/
On Mon, 20 Mar 2023 11:34:43 +0100 Christophe Lohr
wrote:
Package: libgl1-mesa-dri
Version: 22.3.3-1
Severity: normal
X-Debbugs-Cc: christophe.l...@cegetel.net
Dear Maintainer,
Xorg is carshing with a segfault:
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55c365ce4cf9
Hello,
this issue is still present with current testing.
For some weird reason this loop in line 195 is never left.
Putting a printf into this loop confirms that n counts correctly,
but the loop is not left when it reaches 13 (NB_BUILDING).
Strangely a similar loop with the same condition in lin
ends on uninitialised value(s)".
Maybe those are responsible for the malloc abort.
Attached file fixes most of the issues shown by valgrind entering the
main menu.
Kind regards,
BernhardDescription: Fix a few delete and uninitilised values shown by valgrind
Author: Bernhard Übelacker
Last
On Wed, 24 Jan 2024 15:07:46 +0100 wouldsmina wrote:
2024-01-24T09:38:16.810558+01:00 ldap kernel: [ 1553.168747] slapd[13335]:
segfault at 0 ip 7fc2370b49c1 sp 7fbd359fc0c0 error 4 in
dynlist-2.5.so.0.1.8[7fc2370b1000+6000] likely on CPU 1 (core 0, socket 2)
2024-01-24T09:38:16.810568
Hello,
I tried to reproduce this inside a minimal stable/bookworm VM
and received a qmlcachegen crash.
See attached file for details.
The resulting backtrace is quite similar to that found in:
https://bugreports.qt.io/browse/QTBUG-117361
Might avoid the crash, but cannot say if this would make
On Thu, 02 May 2024 12:28:29 +0800 Paul Wise wrote:
The jbig2 manual page is broken. Looks like it was generated via
help2man using the binary in the build tree but without using
LD_LIBRARY_PATH so the binary could not find libraries it uses,
so jbig2 could not start, so it didn't print the usa
On Tue, 07 May 2024 11:30:41 +0200 antonio wrote:
Dear Maintainer,
when I try to add a online account (Systemsettings->Pesonalization->Online
Accounts->Add new account... button) I get this error:
Thread 1 "systemsettings" received signal SIGSEGV, Segmentation fault.
0x7fffc40f8765 in Acco
Hello,
I am no maintainer, just tried to reproduce this issue which I could
inside a minimal Bullseye amd64 qemu VM with the instructions
from the linked Ubuntu bug.
I could not reproduce it within Bookworm or Trixie/testing.
Without "LogLevel DEBUG" it was also not observable.
Unfortunately di
Hello Cláudio,
I am not maintainer of the din package, just reading through some crash reports.
Unfortunately I cannot follow your claim "The crash occurred in the module
libzstd.so.1".
None of the 5 threads show a frame inside libzstd.
It seems just listed in the Module list.
Thread 166294 sho
Hello,
just tried to extract the backtrace from the attached core dump.
Kind regards,
Bernhard
Core was generated by `/usr/bin/evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x7f5ad98da8b6
On Fri, 2 Feb 2024 00:58:31 -0800 Josh Triplett wrote:
Feb 02 00:28:37 o kernel: gnome-shell[1083]: segfault at 20 ip 7fececdf8f04
sp 7ffc5ad85ed8 error 4 in
libmutter-clutter-12.so.0.0.0[7fececda5000+9] likely on CPU 3 (core 4,
socket 0)
Feb 02 00:28:37 o kernel: Code: c3 0f 1f
Hello,
I am just trying to get the source line from the dmesg code line.
[ 97.073761] bluetoothd[838]: segfault at 561314652a23 ip 56167406a375 sp
7fffb128a200 error 4 in bluetoothd[561674048000+ec000] likely on CPU 11
(core 5, socket 0)
[ 97.073799] Code: 00 31 c0 e9 54 ff ff ff
Hello,
I am not maintainer of gnome-nettool, just tried to debug this issue.
gnome-nettool collects the information from an execution
of a dig command [1] and parses the output.
Unfortunately the parsing is done into some fixed size arrays
and the dig output overflows those.
E.g. the destination
Hello,
I am not the maintainer of libuhd, just tried to get some more
information from the provided dmesg Code lines.
These end in some boost::asio functions:
boost::asio::detail::scheduler::concurrency_hint() const at
/usr/include/boost/asio/detail/scheduler.hpp:142
Unfortunately this allows
Am 04.05.24 um 13:46 schrieb Bernhard Übelacker:
These end in some boost::asio functions:
boost::asio::detail::scheduler::concurrency_hint() const at
/usr/include/boost/asio/detail/scheduler.hpp:142
Forgot to attach how I got there:
debugging.txt
And for reference the upstream ticket
On Tue, 19 Dec 2023 20:22:43 +0100 Eduard Bloch wrote:
#7 0x7fb14945a510 __restore_rt (libc.so.6 + 0x3c510)
#8 0x7fb149186702 n/a (amdgpu_drv.so + 0x16702)
#9 0x7fb149186c96 n/a (amdgpu_drv.so + 0x16c96)
#10 0x55
On Fri, 1 Dec 2023 00:26:27 +0100 Lucy wrote:
#3 0x7fbe9c25afd0 __restore_rt (libc.so.6 + 0x3bfd0)
#4 0x557d83358770 n/a (baloo_file + 0x13770)
#5 0x557d8335885d n/a (baloo_file + 0x1385d)
#6 0x557d83365bf1 n/a (baloo_file + 0x20bf1)
#7 0x7fbe9cadd6f0 _ZN7QObject5eventEP6QEv
Hello,
I am not a samba maintainer, just trying to collect some more information.
As far as I see the crash happens
because "cli_credentials_get_password(creds)" in line 62
returns a null pointer, which gets forwarded to
the call to strlcpy without further check.
Kind regards,
Bernhard
(rr) r
On Tue, 05 Dec 2023 23:39:39 + Witold Baryluk
wrote:
Thread 1 "doomsday" received signal SIGSEGV, Segmentation fault.
0x75419e83 in _XFlush () from /lib/x86_64-linux-gnu/libX11.so.6
(gdb) bt
#0 0x75419e83 in _XFlush () at /lib/x86_64-linux-gnu/libX11.so.6
#1 0x754
Hello,
this seems to be the same issue as here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092
And the fix seems to be prepared here:
https://salsa.debian.org/kernel-team/linux/-/commit/37a0ac93027302ffbfae41ddc844312e88e72eef
On Sat, 28 Oct 2023 12:52:30 +0200 Tobias Frost wrote:
Control: tags -1 confirmed
Here's a backtrace when clicking on Settings -> System.
Thread 1 "blastem" received signal SIGSEGV, Segmentation fault.
tern_foreach_int (head=, fun=0x555c12a0 ,
data=0x7fffd7f0, keybuf=0x7fffd8c0 "
Hello,
I am not maintainer of stlcmd, just tried to collect some more information.
This crash seems to be a stack overflow because of a recursive function call.
There is a comment near that recursive call, which could be interesting here.
And this issue seems not to be a packaging issue in Debia
On Sat, 10 Feb 2024 11:01:54 +0100 Petter Reinholdtsen wrote:
[Petter Reinholdtsen]
> I do not use ssr much myself, and have not had time to test.
I applied the upstream commit in git branch fix-1040375-glinject and
tested it on Bookworm, but alas, the .so file still segfaults with a
useless ba
control: forwarded 993018 https://bugs.kde.org/show_bug.cgi?id=485134
control: found 993018 1:3.20.0-2.1
Hello,
I got recently remembered about this bug and patch.
So I try to find out what upstream thinks about this.
It can still be observed with current version in Trixie/testing.
Kind regard
Hello Olly,
(gdb) bt
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1 0x7fa84248315f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2 0x7fa842435472 in __GI_raise (sig=sig@entry=6) a
Hello ng,
On Wed, 22 Nov 2023 22:47:01 -0300 ng wrote:
[18950.426861] Thunar[3027]: segfault at 0 ip 5615a96c98cc sp
7ffd2dbd7320 error 4 in thunar[5615a964+92000] likely on CPU 7 (core 3,
socket 0)
[18950.426895] Code: f3 48 83 ec 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31
Hello,
I tried to find some more information, with the help of a prebuilt full-system
VM image.
On Thu, 4 Apr 2024 21:00:59 + (UTC) Thorsten Glaser wrote:
Sometimes, it does not crash with a smashed stack but instead:
Setting up sasl2-bin (2.1.28+dfsg1-6+b1) ...
BDB0002 __fop_file_setup:
Hello,
tried to reproduce the issue and got on a first run this stack:
(gdb) bt
#0 iter_thread_int (fth=0x157681210) at rect.c:500
#1 0x7fffaa36bad0 in iter_thread_float () at rect.c:253
#2 0x7fffa9c9b010 in start_thread (arg=0x7fffa740f100) at
pthread_create.c:444
#3 0x7fffa9d3e
Hello,
I found this one interesting and tried to reproduce it,
and hit this issue quite reliable with an unstable armel chroot,
inside an armhf unstable qemu VM,
or with a Android/LineageOS with real arm CPU.
Unfortunately valgrind is no longer built for armel, and a local armel rebuild
shows iss
On Sat, 24 Feb 2024 23:55:18 + =?utf-8?q?Lucas_L=C3=B3pez?=
wrote:
I copied the example server file /usr/share/doc/vtun/examples/vtund-server.conf
into
/etc/vtund.conf and enabled server mode in /etc/default/vtun. When I start the
service
with systemctl I get the following error on the dm
On Fri, 31 May 2024 13:03:58 +0200 Eric Degenetais
wrote:
> valgrind gitg &
[... zillions of error reports ...]
==103518== Conditional jump or move depends on uninitialised value(s)
==103518==at 0xD95C49B: ???
==103518==by 0x2108005F: ???
==103518==
==103518==
Architecture: amd64
On Mon, 27 May 2024 11:22:02 +0100 Jack Beckitt-Marshall
wrote:
When I perform certain actions on my GNOME desktop, such as using the Location
bar (Ctrl+L) in Nautilus, clicking on System Information in GNOME Control
Center, or click Fonts in GNOME Tweaks, the programs close with a segmentatio
On Thu, 06 Jun 2024 14:59:55 +1000 "Trent W. Buck" wrote:
I accidentally did, which made virsh coredump (unexpected behaviour):
virsh -c esx://x?no_verify
Stack trace of thread 956182:
#0 0x7ff6c0ca5e3a __libc_free (libc.so.6 + 0x98e3a)
On Wed, 12 Jun 2024 07:19:02 -0300 David Bremner wrote:
David Bremner writes:
>
> Attempt #3
>
> swaks -t brem...@debian.org --pipe 'valgrind /usr/lib/sendmail -bs'
>
> This also runs without errors, so I'm out of ideas for the moment.
Attempt #4:
Rebuild with asan
Hello David, hello Axe
Am 21.06.24 um 01:57 schrieb Bernhard Übelacker:
Especially the third point is puzzling, I could not yet see why this
pointer-content-mixup happens.
Hello David, hello Axel,
I did some further tests and found following location where cli_program
is delared here:
./lib/cli++/cli++.h:35
On Thu, 13 Jun 2024 20:24:33 +0800 =?UTF-8?B?RGFuYWkgU0FFLUhBTiAo6Z+T6YGU6ICQKQ==?=
wrote:
==659486== Process terminating with default action of signal 11 (SIGSEGV)
==659486== Access not within mapped region at address 0x0
==659486==at 0x4847DC4: strcmp (in
/usr/libexec/valgrind/vgprelo
On Fri, 21 Jun 2024 08:03:32 +0200 (CEST) kl...@tuta.io wrote:
Package: sponsor-requestsSeverity: wishlistDear mentors,I am looking for a
sponsor ...
control: reassign -1 sponsor-requests
Hello kl222,
please check your email setup and maybe send as text only.
Unfortunately it broke your requ
control: reassign -1 sponsorship-requests
On Fri, 21 Jun 2024 08:35:11 +0200 (CEST) kl...@tuta.io wrote:
Package: sponsorship-requestsSeverity: wishlistDear mentors,I am looking for ...
Hello kl222,
please check your email setup and maybe send as text only.
Unfortunately it broke your request
Am 21.06.24 um 20:47 schrieb David Bremner:
Hi Bernhard;
Thanks for the patch. This does seem to be progress, but I don't think
it completely fixes Axel's bug. At least for me I still see
-> .
nullmailer-smtpd: Error catching the return value from nullmailer-queue: No
child processes
nullmai
Am 22.06.24 um 00:42 schrieb Bernhard Übelacker:
I did some archaeology and found the issue got visible
at 2017-12-30 in the Buster development cycle with the
migration of nullmailer 1:2.1-5 into testing.
debian-9-stretch:
Connection
Hello David, hello Axel,
I had hoped the expected behaviour might have been the error message 😉
Maybe it is the expected behaviour?
Following is the output of the last not crashing version 1.13
and the current version in testing 2.2+10~g7ed88a0 with the cli_program fix.
Both look quite si
On Thu, 23 May 2024 10:28:52 +0200 Jeroen Ploemen wrote:
Package: gpscorrelate
Severity: normal
Control: found -1 2.1-1
hi Shriram,
it seems the recent upload of gpscorrelate has issues preventing
migration to testing [1]: the autopkgtest fails for all architectures
except amd64 and i386.
I
On Wed, 12 Jun 2024 10:09:08 +0200 julien.pu...@gmail.com wrote:
Hi,
I made a few more tests and found out it only happened in fullscreen
mode: no problem in window mode.
Hello,
I am not maintainer of evince, just trying to collect some more information
about the crash.
I was able to reprod
On Wed, 12 Jun 2024 15:21:35 +0200 Elias Batek
wrote:
Backtrace
ASSERT (krita): "clip" in file
./libs/ui/widgets/kis_image_from_clipboard_widget.cpp, line 80
Thread 1 "krita" received signal SIGABRT, Aborted.
0x756a9e2c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
Am 26.06.24 um 13:33 schrieb Jeroen Ploemen:
On Mon, 24 Jun 2024 15:28:58 +0200
Bernhard Übelacker wrote:
There was a patch pushed to git [3] which explicitly lists valgrind
archs. I stepped over a package valgrind-if-available [4].
Maybe depending on this might be of some help here?
Thanks
On Mon, 24 Jun 2024 15:28:58 +0200 =?UTF-8?Q?Bernhard_=C3=9Cbelacker?=
wrote:
At the bottom is also a minimal reproducer which showed the difference
with and without valgrind to me.
Sorry, I copied a slightly wrong version of the minimal reproducer
in the attachement of my first message,
wh
101 - 200 of 1328 matches
Mail list logo
