[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2020-07-02 Thread Steve Langasek
** Changed in: valgrind (Ubuntu Disco) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2020-06-30 Thread Bug Watch Updater
** Changed in: valgrind (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-12-09 Thread Launchpad Bug Tracker
This bug was fixed in the package valgrind - 1:3.15.0-1ubuntu3.1 --- valgrind (1:3.15.0-1ubuntu3.1) eoan; urgency=medium * Don't look for debug alt file in debug image if it is already found (LP: #1848211) -- Balint Reczey Wed, 27 Nov 2019 13:52:54 +0100 ** Changed in:

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-12-03 Thread Balint Reczey
Verified with 1:3.15.0-1ubuntu3.1 on Eoan: root@ee-valgrind:~# echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse > deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted > universe multiverse > deb http://ddebs.ubuntu.com $(lsb_release

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-12-01 Thread Bug Watch Updater
** Changed in: valgrind (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To manage

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-12-01 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=396656. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-30 Thread Mathew Hodson
** Also affects: valgrind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942614 Importance: Unknown Status: Unknown ** Changed in: valgrind Status: Confirmed => Unknown ** Changed in: valgrind Remote watch: Debian Bug tracker #942614 => KDE Bug Tracking

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-29 Thread Balint Reczey
The apport failure is unrelated and is caused and tracked by LP: #1854237. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-29 Thread Timo Aaltonen
Hello Sebastien, or anyone else affected, Accepted valgrind into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/valgrind/1:3.15.0-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-29 Thread Balint Reczey
I have uploaded the SRU for 19.10. ** Changed in: valgrind (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: valgrind (Ubuntu Eoan) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: valgrind (Ubuntu Focal) Assignee: (unassigned) => Balint Reczey

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package valgrind - 1:3.15.0-1ubuntu5 --- valgrind (1:3.15.0-1ubuntu5) focal; urgency=medium * Drop MPI 1 support to fix FTBFS with openmpi 4.0 valgrind (1:3.15.0-1ubuntu4) focal; urgency=medium * Don't look for debug alt file in debug image if it is

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-28 Thread Balint Reczey
I've sent the fix upstream at: https://bugs.kde.org/show_bug.cgi?id=396656 ** Bug watch added: KDE Bug Tracking System #396656 https://bugs.kde.org/show_bug.cgi?id=396656 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-28 Thread Balint Reczey
Valgrind is typically used with binaries from the same Ubuntu release or locally built ones. Since dwz was enabled by default for Debhelper compat level 12 in 19.04 I suggest not backporting the fix to 18.04. Since the issue was not reported against 19.04 and 19.04 goes EOL soon I suggest not

[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

2019-11-28 Thread Balint Reczey
** Changed in: valgrind (Ubuntu Bionic) Status: New => Triaged ** Changed in: valgrind (Ubuntu Disco) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211