I didn't quite have Dan's patience, but FWIW my system successfully
rebooted 25/25 times with the systemd package (237-3ubuntu10.42) from
bionic-proposed in combination with libseccomp2:amd64
(2.4.3-1ubuntu3.18.04.3) installed and syscall filtering enabled in
> I wonder if you see anything related to systemd-resolved with 'journalctl |
> grep audit | grep systemd'
No, not since March 30th.
> at the time of the boot failure.
No log files were written at that time (no log entries made it to disk before
the segfault).
--
You received this bug
Hmmh, if I see this right, there's a systemd-dbg package available for
Ubuntu 16.04, but not for 18.04.
FWIW, I attached the original core file as bug1886115.core .
** Attachment added: "original core dump of systemd-237-3ubuntu10.41 with
libseccomp2-2.4.3-1ubuntu3"
2.3.1-2.1ubuntu4 is the version of libseccomp2 which is available, i.e.
$ sudo apt install libseccomp2=2.3.1-2.1ubuntu4
succeeds. That allowed me to uncomment, i.e. enable, the SystemCallFilter in
/lib/systemd/system/systemd-resolved.service again and reboot successfully.
--
You received this
> can you confirm which one you have had to disable the SystemCallFilter?
Both files are just symlinks to /lib/systemd/system/systemd-resolved.service.
> Also there appear to be a bunch of systemd managed services which have failed
> to run
I moved snap related services out of the way
apport information
** Attachment added: "SystemdFailedUnits.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389205/+files/SystemdFailedUnits.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389197/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
Title:
apport information
** Tags added: apport-collected bionic
** Description changed:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few seconds into
the boot, the last message displayed is "/var mounted". The system
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389196/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389207/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "SystemdDelta.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389204/+files/SystemdDelta.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389201/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389200/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389206/+files/UdevDb.txt
** Description changed:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389199/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389208/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389202/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389203/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389198/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
Title:
> have you customised the syscall filtering in this profile at all?
Don't know what you mean by profile there. The OS runs on bare-metal here.
The only related modification I made has been (now) the reported commenting-out
of
--8<--
SystemCallFilter=~@clock @cpu-emulation @debug @keyring
> apport-collect 1886115
That doesn't seem to succeed (because the installed package is libseccomp2, but
here listed as libseccomp since the former isn't known to launchpad).
I tried
$ apport-bug -u 1886115 libseccomp2
but that appears to attempt to create a new bug, rather then updating the
Public bug reported:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few seconds into
the boot, the last message displayed is "/var mounted". The system then
appears to hang indefinitely.
Luckily, the 'rescue' boot
Public bug reported:
I just installed Ubuntu 12.04 LTS on a white box. After installation the
system failed to boot, as the root fs couldn't be found. I noticed that
some of the hard drives were not found and consequently the RAID5 stripe
hosting the LVM volume hosting the root fs couldn't be
That Ubuntu 8.10 is about to be released is very commendable, but will
benefit only a small share of Ubuntu 8.04 users, namely those who do not
care about the 'LTS' and are willing and able to upgrade all their hosts
(I wrote something to that effect before - do I have to do that for each
bug
I ran into this problem this morning for the first time, but now it is reliably
reproducable on my work PC ;-|
For me the short-term solution to be able to work again is to disable the
automounter (and to live without NFS on this host for the time being).
Strangely, I was using Ubuntu 8.04 (rc
The issue seems to go away (at least in 3 out of 3 attempts ;-) when
using Colin's 2.6.24-20.35 kernel (amd64/generic tested only). IOW,
works for me. Thanks!
--
Kernel Panic due to null pointer dereference in do_add_mount()
https://bugs.launchpad.net/bugs/214810
You received this bug
On Fri, 2008-08-29 at 01:55 +, Leann Ogasawara wrote:
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of
I don't use Evolution against the Exchange server regularly anymore (due
to the thread id algorithm which seems to be incompatible with MS
Outlook). I just created a test mail and Evolution (2.22.3.1) didn't
explode. So it seems to have improved, thanks to all involved.
--
Evolution consumes a
Well, if the existing output of udevmonitor doesn't contain enough
information, I can provide one of my machine. I interrupted the udevmon
process when the log file grew to 750MiB (yes, sevenhundredfifty
Megabyte) as here the udevd spins for hours after I plug in the
BlackBerry ...
--
bouncing
*** This bug is a duplicate of bug 214041 ***
https://bugs.launchpad.net/bugs/214041
Yup, seems to be fixed in nfs-common 1:1.1.2-2ubuntu2.1.
A big Thanks to all involved!
--
mount.nfs doesn't give up on EACCESS
https://bugs.launchpad.net/bugs/223885
You received this bug notification
Since bug 223885 (which actually is bug 214041) is fixed, this became a
bit of a non-issue. I'd suggest to close this bug.
--
automount attempts to mount NFS filesystems it isn't authorized to
https://bugs.launchpad.net/bugs/221576
You received this bug notification because you are a member of
My laptop hung after calling NetworkManager on shutdown too this
morning. Here the cause was that it tried to deconfigure a network
interface which wasn't listed in /etc/network/interfaces (file edited).
What's actually the motivation to call NetworkManager on shutdown? Why
deconfigure network
Public bug reported:
Binary package hint: evolution
Evolution (2.22.1 of Ubuntu 8.04rc) doesn't remove messages stored on a
MS Exchange (2003) server. Even after messages are deleted and the trash
is expunged the messages are still on the Exchange server (and
accessible via MS Outlook) although
The problems (this, as well as
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/59) seems
to occur (only) when I start to compose a new message and have entered
the password for the global addressbook (provided by MS AD server).
The problems persists then until the Evolution process
Public bug reported:
Binary package hint: evolution
While this may sound like nit-picking, it's actually a show-stopper
here. Evolution (2.22.1-0ubuntu3) computes the Thread-index header field
differently than MS Outlook (2000, 2003). A consequence of this is that
whenever I reply to an e-mail
Public bug reported:
Binary package hint: nfs-common
After upgrading from Ubuntu 7.10 to 8.04rc I noticed that the /net
automounter is badly broken, in that it attempts to mount exports for
which the client is not authorized, cacusing large (infinite?) delays.
The problem seems to be in
The problem is two-fold: i) the auto.net script ignores the access
restrictions for a share, as described above and ii) mount.nfs doesn't
give up on EACCESS, see bug 223885
(https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/223885) .
--
automount attempts to mount NFS filesystems it isn't
This is happening from time to time; the bug was also in feisty and seems to
be more likely to occurr in hardy.
Yes, it is.
there is one such directory on every mount that's why it's trying to use those
That's simply not the case and this erroneous assumption is the bug. Perhaps
every mount
Public bug reported:
Binary package hint: evolution
Since the upgrade to Ubuntu 8.04rc Evolution (2.22.1-0ubuntu3) and
gconfd (gconf2 2.22.0-ubuntu3) occasionally start eating up all
available CPU time. Once they started doing this, they wont stop (at
least not within a few hours) on their own.
Public bug reported:
Binary package hint: evolution
The evolution process uses here 2.5GiB RSS (RES). Even considering that
my inbox contains some 1500 messages, this is rather a lot. I like
memory of my computer to be used for other tasks then just reading
e-mail too ;-)
Evolution
Public bug reported:
Binary package hint: autofs
The automounter (autofs 4.1.4+debian-2.1ubuntu1 of Ubuntu 8.04) or
rather it's /etc/auto.net script, attempts to mount remote (NFS)
filesystems, even if those aren't exported to the local host.
/etc.auto.net just creates a list of shares to mount
I just see, that the illustration is erroneous and hence rather confusing, as
all listed shares could be mounted, but not e.g.
--8--
/svn10.2.1.198
--8--
--
automount attempts to mount NFS filesystems it isn't authorized to
https://bugs.launchpad.net/bugs/221576
You received
On Fri, 2008-04-25 at 00:59 +, Shane Huang wrote:
Yann:
Can you add this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a878539ef994787c447a98c2e3ba0fe3dad984ec
to see whether it can fix your bug?
This patch is already in kernel 2.6.25, if it can
Uh, invalid?
I guess, what makes this defect 'invalid' is, that it is believed to be
an interrupt routing issue caused by the BIOS, see http://www.gossamer-
threads.com/lists/linux/kernel/879808 , but I might be wrong.
I see, if I can get the diagnostics of this system and send them to
Meanwhile I found that the kernel (2.6.24-16) finds the SATA drive, if
the command line option pci=nomsi is provided. This works for me (I'll
check later, if a BIOS upgrade helps too).
--
Hard drives recognizing issues (P5W-DH with Intel 82801GR/GH Sata Controller)
I just ran into what looks the very same issue: the SATA drives here worked
fine in 2.6.22, but aren't found in 2.6.24-16-generic. The kernel spits out
messages of the form (transcription - I can't get to it otherwise):
--8--
[56.463297] SCSI subsystem initialized
[56.477843] ACPI: PCI
On Mon, 2008-04-21 at 23:41 +, Yann SLADEK wrote:
Hi,
I don't know if you have any clues to fixed this issue but I've spent my
entire week end on it so I'm able to give you some kind of help.
To have a system fully bootable and working, you need to modify the IDE
options in the
The same problem occurs in Ubuntu 6.06 too. There libxmms-flac.so complains
about a different symbol though:
/usr/lib/xmms/Input/libxmms-flac.so: undefined symbol: safe_malloc_mul_2op_
dpkg -l xmms-flac
Desired=Unknown/Install/Remove/Purge/Hold
|
Well next day it crashed again, see Bug #164153. Since then I run
2.6.22-14-generic #1, i.e. without Xen. It didn't crash yet since, but
this bug didn't occur using Xen for several weeks either. Thanks for
asking though.
--
kernel Oops (Unable to handle kernel paging request at
Public bug reported:
Binary package hint: linux-source-2.6.22
No cause known. I found following in the kernel's message buffer:
--8--
[ 581.955081] usb 5-2: USB disconnect, address 2
[ 581.964432] usbcore: registered new interface driver xpad
[ 581.964439]
Public bug reported:
Binary package hint: linux-image-2.6.22-14-xen
No idea, what caused the problem. Suddenly input from the keyboard
wasn't evaluated anymore (first kernel oops on this machine, which runs
Linux for 3 weeks now).
In the kernel's message buffer I found following:
--8--
Nov 19
I should mention that this is a AMD dual core Athlon 64 with 4GiB of RAM
sporting Ubuntu 7.10/amd64.
--
kernel Oops (Unable to handle kernel paging request at 001000217eaf)
https://bugs.launchpad.net/bugs/163952
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
OpenOffice's calc is unable to save existing files (it reports an error,
stating that the file exists, but does not offer to overwrite it) if the
file to be written resides on a CIFS share. Creating a new file on the
same share works fine, as well as overwriting files on
** Description changed:
OpenOffice's calc is unable to save existing files (it reports an error,
stating that the file exists, but does not offer to overwrite it) if the
file to be written resides on a CIFS share. Creating a new file on the
same share works fine, as well as overwriting
Public bug reported:
Binary package hint: tracker
After upgrading a desktop from Ubuntu 7.04 to 7.10 my NFS server got
very busy. I did recall the tracker tool, which I disabled on a laptop
where I installed Ubuntu 7.10 as well, before it could cause any harm.
This time I let it go, wondering if
Public bug reported:
After upgrade from Ubuntu 7.04 (x86) to Ubuntu 7.10, gnome-session and
startkde fail to start (.xsession-errors states that the start failed,
but gives no further indication on why they do so) and only a xterminal
and no window manager is started after log-in to the GUI.
It affects many people (at least all, which use some form of network
file system), not only 'experts'.
I don't want to work through a tedious set of questions during (expert)
installation, else I would be using Debian straight. Why not offer a
little field with the uid and gid preset to 1000 (or
57 matches
Mail list logo
