[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
I got the same issue days ago when debugging a package in s390x, so it is not architecture-specific. ubuntu@devnoble1:~/libica-noble/libica-4.3.0$ lintian -I --pedantic --tag-display-limit 0 W: libica-utils: groff-message command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n -wmac -Tutf8 [usr/share/man/man1/icainfo-cex.1.gz:2] W: libica-utils: groff-message command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n -wmac -Tutf8 [usr/share/man/man1/icainfo.1.gz:2] W: libica-utils: groff-message command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n -wmac -Tutf8 [usr/share/man/man1/icastats.1.gz:2] W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) [usr/share/man/man1/icainfo-cex.1.gz:1] W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) [usr/share/man/man1/icainfo.1.gz:1] W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) [usr/share/man/man1/icastats.1.gz:1] I: libica4: hardening-no-bindnow [usr/lib/s390x-linux-gnu/libica-cex.so.4.3.0] I: libica4: hardening-no-bindnow [usr/lib/s390x-linux-gnu/libica.so.4.3.0] I: libica4: symbols-file-missing-build-depends-package-field libica-cex.so.4 [symbols] I: libica4: symbols-file-missing-build-depends-package-field libica.so.4 [symbols] I: libica-utils: typo-in-manual-page paramater parameter [usr/share/man/man1/icastats.1.gz:76] I: libica-utils: typo-in-manual-page sucessful successful [usr/share/man/man1/icastats.1.gz:126] P: libica source: silent-on-rules-requiring-root [debian/control] ubuntu@devnoble1:~/libica-noble/libica-4.3.0$ The apparmor profile issue was a nice catch, I was getting some trouble to reproduce it in a minimal fashion, but that was because I was leaving the pipeline just output to stdout. Should we patch lintian to only write this to /tmp ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961425] Re: 22.04: FTBFS due to test failure
Just noticed that version 0.8.0-2ubuntu2 ( https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu2 ) landed at the start of the month. This version has a patch that fixes the string issue; renameat2 issue remains, but it won't trigger unless building (and running the unit tests) from a ZFS volume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961425 Title: 22.04: FTBFS due to test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961425] Re: 22.04: FTBFS due to test failure
I was looking into this for a few days and failure:
[ TEST ] kj/string-test.c++:31: legacy test: String/Str
kj/string-test.c++:38: failed: expected ("-128 -32768 -2147483648
-9223372036854775808") == (str((signed char)-128, ' ', (signed short)-32768, '
', ((int)-2147483647) - 1, ' ', ((long long)-9223372036854775807ll) - 1)); -128
-32768 -2147483648 -9223372036854775808; str((signed char)-128, ' ', (signed
short)-32768, ' ', ((int)-2147483647) - 1, ' ', ((long
long)-9223372036854775807ll) - 1) = -128 -32768 -214748364( -9223372036854775808
stack: c27f3c60b7b c27f38280d7 764d217568b3 764d216c058f 764d217549e3
764d2175661f 764d216ef643 764d21701a83 764d216c058f 764d216f568b 764d2175314f
764d211017a3 764d21101987
[ FAIL ] kj/string-test.c++:31: legacy test: String/Str (85 μs)
... is caused by the code depending on undefined behavior, which happens
to pass on x64 and arm64 but fails on ppc64el. Reducing optimization
level works but I won't count on it to be stable. But since the problem
is already fixed in 0.9.0 (currently on experimental), we can get the
fix when that version is merged.
There are also a different FTBFS caused by a few test cases that fail
when the unit tests are ran from a ZFS volume. I only hit it after
building on a container backed by ZFS storage, btw. It's caused by a
capnproto component using its own wrapper for system call renameat2()
without implementing the fallback for it on unsupported filesystems (as
renameat2 requires collaboration from the FS layer). It is also fixed in
version 0.9.0.
If 0.9.0 does not arrive in time for the merge freeze, I tentatively
backported these two fixes to 0.8.0. A test branch in
https://code.launchpad.net/~aittner/ubuntu/+source/capnproto/+git/capnproto/+ref/backport-
upstream-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961425
Title:
22.04: FTBFS due to test failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
I was running a few test builds with different combinations of gcc, elfutils and protobuf and trying to make the build fail... but it continues working despite the older elfutils compiled with the newer gcc. Last check was with protobuf-3.12.4-1ubuntu3 (from jammy, 4 days ago) in an impish 0.185-1build1 and then downgraded to a 0.183-8 built with 11.2.0-7ubuntu2 (from impish), but it still does not trigger the issue despite the mismatches. I still could not find the reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
Testing with 20200408.1. It is easier to reproduce this situation on x64 with qemu. - Create disk images for this test: $ qemu-img create -f qcow2 sda.qcow2 10G Formatting 'sda.qcow2', fmt=qcow2 size=10737418240 cluster_size=65536 lazy_refcounts=off refcount_bits=16 $ qemu-img create -f qcow2 sdb.qcow2 4G Formatting 'sdb.qcow2', fmt=qcow2 size=4294967296 cluster_size=65536 lazy_refcounts=off refcount_bits=16 $ qemu-img create -f qcow2 sdc.qcow2 4G Formatting 'sdc.qcow2', fmt=qcow2 size=4294967296 cluster_size=65536 lazy_refcounts=off refcount_bits=16 - Put an install ISO in both sdb and sdc. Easiest way is boot qemu from the installer itself and then copy it: $ wget http://cdimage.ubuntu.com/ubuntu-server/daily-live/20200408.1 /focal-live-server-amd64.iso $ qemu-system-x86_64 -enable-kvm -M q35 -m 1G -cpu host -drive file=sda.qcow2,media=disk,format=qcow2 -drive file=sdb.qcow2,media=disk,format=qcow2 -drive file=sdc.qcow2,media=disk,format=qcow2 -drive file=focal-live-server- amd64.iso,media=cdrom -boot d - As soon as the installer starts, open the shell and do: $ sudo dd if=/dev/cdrom of=/dev/sdb $ sudo dd if=/dev/cdrom of=/dev/sdc Just to be sure: $ sudo sync - Close qemu then start it again, booting from one of the disks as we were installing from an image dd'ed from an existing install in a server which does not support virtual media: $ qemu-system-x86_64 -enable-kvm -M q35 -m 1G -cpu host -drive file=sda.qcow2,media=disk,format=qcow2 -drive file=sdb.qcow2,media=disk,format=qcow2 -drive file=sdc.qcow2,media=disk,format=qcow2 -boot menu=on - Press Esc and select 2 to boot from sdb. - Proceed with the installation and select sda as the target. >> The installer will detect sdc but won't be able to handle this situation. Crash reports and screenshots attached. ** Attachment added: "Crash report on qemu" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350302/+files/1586437687.174328804.install_fail.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
** Attachment added: "Storage summary on qemu test" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350304/+files/Screenshot%20from%202020-04-09%2010-07-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
** Attachment added: "Detected disks on qemu" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350303/+files/Screenshot%20from%202020-04-09%2010-07-36.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
** Attachment added: "1586234957.306729794.install_fail.crash" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350235/+files/1586234957.306729794.install_fail.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] [NEW] Installer crashed with multiple ISO images on system's disks
Public bug reported:
Installing 20.04 from ISO on an IBM Power8 (modoc from Power MAAS)
failed when multiple copies of this same image are available on local
disk (*not* optical drives nor virtual CDROMs, as this machine does not
have support for vmedia).
Machine configuration:
- /dev/sda will be the installation target;
- /dev/sdb will be the installation source (ISO dd'ed on disk);
- /dev/sdc is an extra ISO "forgotten" by the user (ISO dd'ed on disk);
Procedures:
- Machine deployed with bionic from MAAS;
- Boot the machine, download
(http://cdimage.ubuntu.com/ubuntu-server/daily-live/20200402/focal-live-server-ppc64el.iso
), copy it to both /dev/sdb and /dev/sdc (dd if=focal-live-server-ppc64el.iso
of=/dev/sdb);
- From another host, connect into the machine's console using "ipmitool sol
activate";
- Reboot machine. On petitboot, select /dev/sdb as the boot device;
- Run installer from SoL console, install on /dev/sda with the default options;
- subiquity will crash in the hostname/user configuration screen (when it is
running disk-relaeed tasks in background).
Stack trace for this failure:
sdc logical_block_size_bytes: 512
Verifying /dev/sdc1 exists
Verifying /dev/sdc1 size, expecting 980123648 bytes, found 1024 bytes
An error occured handling 'partition-sdc1': RuntimeError - Verifying
/dev/sdc1 size, expecting 980123648 bytes, found 1024 bytes
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring partition: partition-sdc1
TIMED BLOCK_META: 4.679
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
curtin command block-meta
Traceback (most recent call last):
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File "/snap/subiquity/1617/lib/python3.6/site-packages/curtin/log.py",
line 97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File "/snap/subiquity/1617/lib/python3.6/site-packages/curtin/log.py",
line 79, in log_time
return func(*args, **kwargs)
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 100, in block_meta
return meta_custom(args)
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1796, in meta_custom
handler(command, storage_config_dict)
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 782, in partition_handler
partition_verify(part_path, info)
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 671, in partition_verify
verify_size(devpath, int(util.human2bytes(info['size'])))
File
"/snap/subiquity/1617/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 645, in verify_size
raise RuntimeError(msg)
RuntimeError: Verifying /dev/sdc1 size, expecting 980123648 bytes, found
1024 bytes
Verifying /dev/sdc1 size, expecting 980123648 bytes, found 1024 bytes
Installation worked when I zeroed /dev/sdc (with "dd if=/dev/zero of=/dev/sdc
bs=1M count=50") and repeated the process.
Repeating these two procedures a few times, I noticed the installation
with another ISO (apart from the one used as source for the install)
seems to fail consistently. Maybe it is not a problem, I'm not sure if
subiquity is intended to support this kind of installation procedure
when machine does not have support for virtual media.
On the stack trace, the size of 1024 bytes makes sense if the installer
is reading /dev/sd[bc]1 instead of /dev/sd[bc]2: verify_size (from
https://github.com/CanonicalLtd/curtin/blob/master/curtin/commands/block_meta.py#L645
) calls read_sys_block_size_bytes (from
https://github.com/CanonicalLtd/curtin/blob/638c9a7849222575dacde5e43d1201bb4e0db1d1/curtin/block/__init__.py#L699
). Value read from /sys/class/block/sdb1/size is "2", so 1024 bytes.
Crash reports from several attempts attached.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "1586201114.498370886.install_fail.crash"
https://bugs.launchpad.net/bugs/1871832/+attachment/5350234/+files/1586201114.498370886.install_fail.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871832
Title:
Installer crashed with multiple ISO images on system's disks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
** Attachment added: "1586236548.054427385.install_fail.crash" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350236/+files/1586236548.054427385.install_fail.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871832] Re: Installer crashed with multiple ISO images on system's disks
** Attachment added: "1586237649.350583553.install_fail.crash" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+attachment/5350237/+files/1586237649.350583553.install_fail.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871832 Title: Installer crashed with multiple ISO images on system's disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1871832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799356] Re: gwibber stores extreme number of messages in gwibber.sqlite
Happening for me too, my gwibber.sqlite is 1,1 GB. Counting for current
amount of messages, I got:
sqlite select count(*) from messages;
560965
So, I just removed messages older than 30 days with:
delete from messages where time (strftime('%s','now') - 30*24*60*60);
I think Gwibber should run this garbage collect periodically, but
preserving directed and send messages unless the user asks it to delete
them too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799356
Title:
gwibber stores extreme number of messages in gwibber.sqlite
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/799356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
