Yeah, it has the same symptoms, though I have different errors in my
journal. Is there a way to merge the bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688636
Title:
Firefox gets stuck in a p
Public bug reported:
I recently upgraded to zesty from yakkety, and occasionally Firefox
(53.0+build6-0ubuntu0.17.04.1) and Thunderbird (45.8.0+build1-0ubuntu1)
get stuck in a page fault. In the journal the kernel notices that a
thread is stuck in a spinlock waiting for a page fault to return, but
The wily-proposed version (5.1.1-1ubuntu2.1) fixed it for me too.
Thanks Brian, it's much appreciated.
Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503034
Title:
Autofs 5.1.1-1ubuntu2 crash
I edited the description in line to make it mostly in line with the SRU
wiki. It's hard to provide a test case without having a full ldap client
and server configuration, plus an NFS system. I don't have access to the
server side configs so I can't provide those.
What extra information is necessar
I've been running the autofs-ldap & autofs binaries from 14.04 in 15.10,
they work fine.
I had different issues with the 14.10 and 15.04 binaries (on their
respective releases), which never worked with LDAP, but appeared to hard
lock rather than segfault so it was harder to track down.
--
You re
This is the backtrace I got out of apport-cli, but I couldn't figure out
where the debug symbols for autofs are. I followed the instructions to
add extra debug symbols (https://wiki.ubuntu.com/DebuggingProgramCrash).
** Attachment added: "_usr_sbin_automount.0.crash"
https://bugs.launchpad.net
Public bug reported:
I'm running Wily Beta 2, updated to the latest packages in the wily
repository, with autofs-ldap using mounts stored in LDAP. On startup
systemd immediately puts autofs into a failed state as it segfaults when
reading the auto.master.
Autofs & autofs-ldap version is 5.1.1-1ub
It seems the NIS was also adding a postfix user, and these conflicted.
It seems to have been a problem between me and my network.
Sorry about that.
--
Could not install postfix - postinst failed to properly create postfix user
https://bugs.launchpad.net/bugs/512646
You received this bug notifica
I manually added the line to /etc/passwd and it worked. No idea why
adduser wasn't doing that though.
--
Could not install postfix - postinst failed to properly create postfix user
https://bugs.launchpad.net/bugs/512646
You received this bug notification because you are a member of Ubuntu
Bugs, w
Additionally when I try and execute the commands given in post 2 I get
contradictory error messages.
>adduser --system --no-create-home --disabled-password --ingroup postfix postfix
The user `postfix' already exists. Exiting.
>usermod -g postfix postfix
usermod: user 'postfix' does not exist in /
I have the same error caused by installing mutt, though I have a
slightly different terminal output.
sudo apt-get install postfix
Reading package lists... Done
Building dependency tree
Reading state information... Done
postfix is already the newest version.
0 upgraded, 0 newly installed, 0
11 matches
Mail list logo
