Public bug reported:
After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
stop on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
This can be reproduced with a simple “hello world” program:
$ cat hello.c
#include
int main()
{
// printf() displays the string
@dannf Thanks, it works for me from both command line and Qt Creator.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not stopping on breakpoint in a 32-bit program
To manage notif
I’ve tested version 8.1-0ubuntu3.2 from ubuntu-proposed on my Xubuntu
18.04.3 x86_64 from both the command line and Qt Creator and the problem
has not appeared.
I am also setting verification-done because no other supported releases
seem affected.
** Tags removed: verification-needed verification
Public bug reported:
After I upgraded my testing server from 16.04 to Ubuntu 18.04.2 LTS the
last week, I keep getting errors during SVN update while running CTest
(version 3.10.2) which cause CTest to quit too early:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std:
Same problem here when trying to installing Ubuntu 14.04.3 LTS Server
x64 using the media created by both Linux Live Usb Creator and
UNetbootin. After the error message appeared, I tried to mount the drive
manually as suggested by Vladimir and Jav but still no success. The CD-
ROM integrity check (
I’ve got the same problem on Ubuntu 22.04.5 LTS. However, Ubuntu
repositories do not contain Python 3.12 for 22.04 as well as 20.04, see
https://packages.ubuntu.com/search?keywords=python3.12&searchon=names&suite=all§ion=all.
Therefore I guess this could be caused by
https://launchpad.net/~deadsna
** Bug watch added: github.com/deadsnakes/issues/issues #304
https://github.com/deadsnakes/issues/issues/304
** Also affects: ubuntu-release-upgrader via
https://github.com/deadsnakes/issues/issues/304
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
> Is the Deja Dup window active and focused when the backup finishes? In
that case, it doesn't submit a desktop notification.
I tried it both with the window open and without opening it. The result
in both cases was as I described. I doubt I’ve ever had the window
active when the backup finished a
Public bug reported:
I use Deja-dup (alias Backups) for regular automated backups. I get a
notification when the backup is starting. However, there is no
notification about finishing the backup. (If I have the progress window
open during the backup, it simply disappears when the backup finishes.)
