Public bug reported:
`3.6-7ubuntu4.3` causes false positives with containerd (works fine with
`3.6-7ubuntu4.1`)
# needrestart -rl -p -v
[main] eval /etc/needrestart/needrestart.conf
[main] needrestart v3.6
[main] running in root mode
[main] systemd detected
[main] vm detected
[Core] #813 is a Ne
Upd: it's not a single unique case, I have a bunch of other machines
(with different roles and a set of installed packages) and all them
report `libpq5` as outdated (yet none of them have even it installed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
Running `/usr/lib/update-notifier/apt-check` returns `119;1`
If I patch the code to see what package is to be upgraded (eg in the
`isSecurityUpgrade` function) - it shows `libpq5`.
The machine has nothing to do and had never ever installed postgresql
client
And at the momen
I also can confirm the solution from @zanyrain forks for me as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865063
Title:
snapd package hangs on deb postinst
To manage notifications about th
And I think here is relevant syslog entries:
Feb 29 16:26:06 ubuntu-2004 kernel: [ 175.438250] pool-org.gnome.[8110]:
segfault at 8 ip 7f36e9df9b62 sp 7f36e8a03960 error 4 in
libgs_plugin_snap.so (deleted)[7f36e9df2000+1a000]
Feb 29 16:26:06 ubuntu-2004 kernel: [ 175.438258] Code: d5 5
I can confirm that it also happens to me, the latest daily-live, just
installed inside vmware player.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865063
Title:
snapd package hangs on deb postinst
Public bug reported:
In the second half of the function there is
# Calculate the interval in seconds depending on the unit specified
if [ "${interval%s}" != "$interval" ] ; then
interval="${interval%s}"
elif [ "${interval%m}" != "$interval" ] ; then
interval="${interva
I'm not sure why I did not mention originally, sorry for that, but there
is a chance that what makes it reproducible is starting the daemon
inside the lxd/lxc
For those who don't use lxd - the commands would be (I don't have access
to linuxes or my infrastructure at the moment, so might be a bit
i
@Philipp Huebner
I personally use the following systemd service override:
```
[Service]
PrivateTmp=false
ProtectHome=false
ProtectSystem=false
```
Speaking of detection: `systemd-detect-virt` in an lxd/lxc container
returns `lxc\n`
--
You received this bug notification because you are a member
Ok, found it:
PrivateTmp=true
ProtectHome=true
ProtectSystem=full
these systemd service parameters prevent it from starting properly...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815699
Title:
It looks like it only happens inside linux containers (lxc) :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815699
Title:
installed ejabberd package post-installation script subprocess
returned
Public bug reported:
On an empty just installed ubuntu 18.04 `apt install ejabberd` fails.
Relevant apt log:
Setting up erlang-p1-cache-tab (1.0.12-2) ...
Setting up erlang-p1-xml (1.1.28-1) ...
Setting up erlang-p1-eimp (1.0.2-2) ...
Setting up erlang-p1-xmpp (1.1.19-1) ...
Setting up ejabberd
Public bug reported:
When I run `systemctl restart rabbitmq-server` it waits for 90 seconds
then systemd sends SIGKILL to it.
Presumably the `epmd` process does not receive SIGTERM, since if I run
`kill 1493` (or whatever pid it currently is) then restart happens
straight after that successfully
My apologies that I did not send it before, but seems like just another
upgrade solved it.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member
> Does the issue go away if you boot into the previous kernel?
I'm not sure the other kernel is available (I mean if it was not
autoremoved - I just keep 3 latest)
Yep, I'll try the latest available, thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656282/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656277/+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/1578552
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656281/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552
Title:
ir
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656276/+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/1578552
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656273/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656279/+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/1578552
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656278/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656280/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552
Titl
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656275/+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/1578552
Title:
irq
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656272/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656274/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15785
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1578552/+attachment/4656271/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552
Title:
irq 20
apport information
** Tags added: apport-collected xenial
** Description changed:
Hi, I'm running ubuntu 16.04 (since january) and relatively recently
(after another kernel upgrade during alpha-beta stage) I've started
experience problems with the mouse (it's a radio-powered one). After
Public bug reported:
Hi, I'm running ubuntu 16.04 (since january) and relatively recently
(after another kernel upgrade during alpha-beta stage) I've started
experience problems with the mouse (it's a radio-powered one). After
checking the syslog that is what I've found:
May 5 16:39:03 lyu-ubunt
Public bug reported:
I'm experiencing this behaviour on 2 separated machines (in a virtualbox
vm and physically installed on another laptop):
Sometimes after I start the Files Gnome application - its corresponding
button disappears from the Unity Launcher couple seconds after it's
started. So if
I can confirm that the bug is fixed in the 5.4.0-3ubuntu2.1
Thank you
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372750
Titl
@mgedemin
Marius that's great, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372750
Title:
A patch for collecting swap utilization in openvz
To manage notifications about this bug go t
Guys, seriously - Importance: high, trivial fix and no attention from
maintainers?
It discredits both ubuntu and the maintainers team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230917
Title:
p
Public bug reported:
Affected version: 1.5.4-4
There is similar bug in debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=729465 so could you please backport their solution
to 1.5.4-5 please?
Short notes: if you change the port pgbouncer listens - the restart
script cannot connect it (si
Public bug reported:
In collectd-5.4.0-3ubuntu2 there is a bug that prevents collectd from
collecting information about swap utilization.
Here is a corresponding issue on github:
https://github.com/collectd/collectd/issues/733
Also the developer provided the minimalistic patch that fixes the iss
Public bug reported:
That's it - if you run `service supervisor restart` on lucid (might be
reproducible on other versions) then what you see is:
Restarting supervisor:
and it doesn't restart.
The fix is actually trivial:
to replace
start-stop-daemon --stop --quiet --pidfile \
36 matches
Mail list logo
