[Bug 1878730] Re: False positive security update

2020-05-14 Thread Ivan Kurnosov
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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878730

Title:
  False positive security update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1878730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878730] [NEW] False positive security update

2020-05-14 Thread Ivan Kurnosov
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 moment it's not installed either

```
$ apt policy libpq5
libpq5:
  Installed: (none)
  Candidate: 10.12-0ubuntu0.18.04.1
  Version table:
 10.12-0ubuntu0.18.04.1 500
500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 10.3-1 500
500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
```

After debugging some more it looks like

```
if not (depcache.marked_install(pkg) or
depcache.marked_upgrade(pkg)):
continue
```

this is the condition to blame: I expect the predicate in parentheses to
be false - as the package is not marker for install or upgrade.

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878730

Title:
  False positive security update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1878730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865063] Re: snapd package hangs on deb postinst

2020-02-28 Thread Ivan Kurnosov
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865063] Re: snapd package hangs on deb postinst

2020-02-28 Thread Ivan Kurnosov
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 53 48 83 ec 08 e8 
9d c7 ff ff 49 89 c7 31 c0 4d 85 ff 0f 84 85 00 00 00 4c 89 e2 48 89 ee 4c 89 
ff e8 a1 be ff ff 49 89 c4 <8b> 40 08 85 c0 74 58 31 db 0f 1f 44 00 00 49 8b 14 
24 89 d8 4c 89

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865063] Re: snapd package hangs on deb postinst

2020-02-28 Thread Ivan Kurnosov
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840995] [NEW] check_stamp() function of apt.systemd.daily should not assume interval is a number

2019-08-21 Thread Ivan Kurnosov
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="${interval%m}"
interval=$((interval*60))
elif [ "${interval%h}" != "$interval" ] ; then
interval="${interval%h}"
interval=$((interval*60*60))
else
interval="${interval%d}"
interval=$((interval*60*60*24))
fi

so, a variable might hold something like "1d", "100m", etc.

Yet in the first there is a condition

if [ "$interval" -eq 0 ]; then
debug_echo "check_stamp: interval=0"
# treat as no time has passed
return 1
fi

which treats the value as a number and leads to

/usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840995

Title:
  check_stamp() function of apt.systemd.daily should not assume interval
  is a number

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1840995/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784757] Re: rabbitmq-server does not properly shutdown

2019-06-08 Thread Ivan Kurnosov
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
incorrect):

lxc launch ubuntu:bionic
lxc exec  bash

inside container:
apt update
apt install rabbitmq-server
systemct restart rabbitmq-server

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757

Title:
  rabbitmq-server does not properly shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1784757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815699] Re: installed ejabberd package post-installation script subprocess returned error exit status 1

2019-04-22 Thread Ivan Kurnosov
@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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815699

Title:
  installed ejabberd package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1815699/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815699] Re: installed ejabberd package post-installation script subprocess returned error exit status 1

2019-02-12 Thread Ivan Kurnosov
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:
  installed ejabberd package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1815699/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815699] Re: installed ejabberd package post-installation script subprocess returned error exit status 1

2019-02-12 Thread Ivan Kurnosov
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 error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1815699/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815699] [NEW] installed ejabberd package post-installation script subprocess returned error exit status 1

2019-02-12 Thread Ivan Kurnosov
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 (18.01-2) ...

Creating config file /etc/ejabberd/ejabberd.yml with new version
Created symlink /etc/systemd/system/multi-user.target.wants/ejabberd.service → 
/lib/systemd/system/ejabberd.service.
Job for ejabberd.service failed because the control process exited with error 
code.
See "systemctl status ejabberd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript ejabberd, action "start" failed.
● ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2019-02-13 
01:16:29 UTC; 17ms ago
 Docs: https://www.process-one.net/en/ejabberd/docs/
  Process: 1588 ExecStart=/bin/sh -c /usr/sbin/ejabberdctl start && 
/usr/sbin/ejabberdctl started (code=exited, status=1/FAILURE)
dpkg: error processing package ejabberd (--configure):
 installed ejabberd package post-installation script subprocess returned error 
exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10.11) ...
Processing triggers for ufw (0.35-5) ...
Errors were encountered while processing:
 ejabberd
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish


Systemctl status:

● ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled; vendor 
preset: enabled)
   Active: activating (start) since Wed 2019-02-13 01:22:17 UTC; 23s ago
 Docs: https://www.process-one.net/en/ejabberd/docs/
Cntrl PID: 10571 (sh)
Tasks: 52 (limit: 4915)
   CGroup: /system.slice/ejabberd.service
   ├─10571 /bin/sh -c /usr/sbin/ejabberdctl start && 
/usr/sbin/ejabberdctl started
   ├─10591 /usr/lib/erlang/erts-9.2/bin/beam.smp -K true -P 25 -- 
-root /usr/lib/erlang -progname erl -- -home /var/lib/ejabberd -- -sname 
ejabberd@localhost -smp auto -mnesia dir "/var/lib/ejabberd"
   ├─10592 /bin/sh /usr/sbin/ejabberdctl started
   ├─10610 erl_child_setup 65536
   ├─10639 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10640 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10641 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10642 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10643 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10644 /usr/lib/erlang/lib/p1_eimp-1.0.2/priv/bin/eimp
   ├─10645 sh -s disksup
   ├─10647 /usr/lib/erlang/lib/os_mon-2.4.4/priv/bin/memsup
   ├─10648 inet_gethost 4
   ├─10649 inet_gethost 4
   ├─10650 /bin/sh -c inotifywait $0 $@ & PID=$!; read a; kill $PID -m 
-e modify -e close_write -e moved_to -e create -e delete -e attrib --quiet -r 
/etc/ejabberd
   ├─10651 inotifywait -m -e modify -e close_write -e moved_to -e 
create -e delete -e attrib --quiet -r /etc/ejabberd
   └─11122 sleep 2

Feb 13 01:22:17 unified-monkey systemd[1]: ejabberd.service: Scheduled restart 
job, restart counter is at 6.
Feb 13 01:22:17 unified-monkey systemd[1]: Stopped A distributed, 
fault-tolerant Jabber/XMPP server.
Feb 13 01:22:17 unified-monkey systemd[1]: ejabberd.service: Failed to reset 
devices.list: Operation not permitted
Feb 13 01:22:17 unified-monkey systemd[1]: Starting A distributed, 
fault-tolerant Jabber/XMPP server...

** Affects: ejabberd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1815699/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784757] [NEW] rabbitmq-server does not properly shutdown

2018-07-31 Thread Ivan Kurnosov
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

● rabbitmq-server.service - RabbitMQ Messaging Server
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor 
preset: enabled)
   Active: deactivating (final-sigterm) since Wed 2018-08-01 01:17:04 UTC; 7s 
ago
  Process: 1183 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, 
status=0/SUCCESS)
  Process: 178 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait 
(code=exited, status=0/SUCCESS)
  Process: 177 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
 Main PID: 177 (code=killed, signal=TERM)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/rabbitmq-server.service
   └─1493 /usr/lib/erlang/erts-9.2/bin/epmd -daemon

Aug 01 01:11:20 rmq-1 systemd[1]: rabbitmq-server.service: Failed to reset 
devices.list: Operation not permitted
Aug 01 01:11:20 rmq-1 systemd[1]: Starting RabbitMQ Messaging Server...
Aug 01 01:11:25 rmq-1 rabbitmq[178]: Waiting for 'rabbit@rmq-1'
Aug 01 01:11:25 rmq-1 rabbitmq[178]: pid is 204
Aug 01 01:11:30 rmq-1 systemd[1]: Started RabbitMQ Messaging Server.
Aug 01 01:17:04 rmq-1 systemd[1]: Stopping RabbitMQ Messaging Server...
Aug 01 01:17:06 rmq-1 rabbitmq[1183]: Stopping and halting node 'rabbit@rmq-1'

** Affects: rabbitmq-server (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784757

Title:
  rabbitmq-server does not properly shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1784757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1578552] Re: irq 20: nobody cared

2016-06-05 Thread Ivan Kurnosov
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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] Re: irq 20: nobody cared

2016-05-05 Thread Ivan Kurnosov
> 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] WifiSyslog.txt

2016-05-05 Thread Ivan Kurnosov
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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578552

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] ProcEnviron.txt

2016-05-05 Thread Ivan Kurnosov
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

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] UdevDb.txt

2016-05-05 Thread Ivan Kurnosov
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:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] ProcCpuinfo.txt

2016-05-05 Thread Ivan Kurnosov
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

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] IwConfig.txt

2016-05-05 Thread Ivan Kurnosov
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:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] ProcModules.txt

2016-05-05 Thread Ivan Kurnosov
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

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] ProcInterrupts.txt

2016-05-05 Thread Ivan Kurnosov
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/1578552

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] PulseList.txt

2016-05-05 Thread Ivan Kurnosov
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

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] Lspci.txt

2016-05-05 Thread Ivan Kurnosov
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 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] CurrentDmesg.txt

2016-05-05 Thread Ivan Kurnosov
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

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] JournalErrors.txt

2016-05-05 Thread Ivan Kurnosov
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/1578552

Title:
  irq 20: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] CRDA.txt

2016-05-05 Thread Ivan Kurnosov
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: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1578552] Re: irq 20: nobody cared

2016-05-05 Thread Ivan Kurnosov
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
  checking the syslog that is what I've found:
  
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623139] irq 20: nobody cared (try 
booting with the "irqpoll" option)
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623157] CPU: 1 PID: 0 Comm: 
swapper/1 Tainted: P   OE   4.4.0-21-generic #37-Ubuntu
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623159] Hardware name: ASUSTeK 
Computer Inc.  K50IN/K50IN  , BIOS 222 01/22/2010
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623163]  0086 
87c743a25af182af 8800bfa83cf8 813e93c3
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623168]  8800b57abe00 
8800b57abeb4 8800bfa83d20 810dd3a3
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623171]  8800b57abe00 
 0014 8800bfa83d58
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623176] Call Trace:
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623178]
[] dump_stack+0x63/0x90
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623192]  [] 
__report_bad_irq+0x33/0xc0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623196]  [] 
note_interrupt+0x247/0x290
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623199]  [] 
handle_irq_event_percpu+0x167/0x1d0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623202]  [] 
handle_irq_event+0x3e/0x60
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623206]  [] 
handle_fasteoi_irq+0x96/0x150
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623211]  [] 
handle_irq+0x1a/0x30
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623215]  [] 
do_IRQ+0x4b/0xd0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623220]  [] 
common_interrupt+0x82/0x82
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623439]  [] ? 
_nv013458rm+0x30/0x30 [nvidia]
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623446]  [] ? 
__do_softirq+0x7e/0x290
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623450]  [] 
irq_exit+0xa3/0xb0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623454]  [] 
do_IRQ+0x54/0xd0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623458]  [] 
common_interrupt+0x82/0x82
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623460]
[] ? cpuidle_enter_state+0x10e/0x2b0
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623468]  [] 
cpuidle_enter+0x17/0x20
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623473]  [] 
call_cpuidle+0x32/0x60
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623476]  [] ? 
cpuidle_select+0x13/0x20
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623480]  [] 
cpu_startup_entry+0x290/0x350
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623485]  [] 
start_secondary+0x154/0x190
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623487] handlers:
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623492] [] 
usb_hcd_irq
  May  5 16:39:03 lyu-ubuntu kernel: [11999.623495] Disabling IRQ #20
  
  
  The currently running kernel version is 4.4.0-21-generic #37-Ubuntu SMP Mon 
Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lyulyu 1730 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=9cae2df7-f2e2-4b1e-9abc-c7a72011d3f8
+ InstallationDate: Installed on 2016-02-23 (71 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
+ Lsusb:
+  Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC 
Webcam / CNF7129
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: ASUSTeK Computer Inc. K50IN
+ NonfreeKernelModules: nvidia_uvm nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=4a825d1e-bfce-46f1-ae82-565557acdab2 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm lpadmin sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/22/2010
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 222
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: K50IN
+ dmi.board.vendor: ASUSTeK Computer Inc.
+ dmi.board.version: 1.0
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK Computer Inc.
+ dmi.modalias: 

[Bug 1578552] [NEW] irq 20: nobody cared

2016-05-05 Thread Ivan Kurnosov
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-ubuntu kernel: [11999.623139] irq 20: nobody cared (try 
booting with the "irqpoll" option)
May  5 16:39:03 lyu-ubuntu kernel: [11999.623157] CPU: 1 PID: 0 Comm: swapper/1 
Tainted: P   OE   4.4.0-21-generic #37-Ubuntu
May  5 16:39:03 lyu-ubuntu kernel: [11999.623159] Hardware name: ASUSTeK 
Computer Inc.  K50IN/K50IN  , BIOS 222 01/22/2010
May  5 16:39:03 lyu-ubuntu kernel: [11999.623163]  0086 
87c743a25af182af 8800bfa83cf8 813e93c3
May  5 16:39:03 lyu-ubuntu kernel: [11999.623168]  8800b57abe00 
8800b57abeb4 8800bfa83d20 810dd3a3
May  5 16:39:03 lyu-ubuntu kernel: [11999.623171]  8800b57abe00 
 0014 8800bfa83d58
May  5 16:39:03 lyu-ubuntu kernel: [11999.623176] Call Trace:
May  5 16:39:03 lyu-ubuntu kernel: [11999.623178][] 
dump_stack+0x63/0x90
May  5 16:39:03 lyu-ubuntu kernel: [11999.623192]  [] 
__report_bad_irq+0x33/0xc0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623196]  [] 
note_interrupt+0x247/0x290
May  5 16:39:03 lyu-ubuntu kernel: [11999.623199]  [] 
handle_irq_event_percpu+0x167/0x1d0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623202]  [] 
handle_irq_event+0x3e/0x60
May  5 16:39:03 lyu-ubuntu kernel: [11999.623206]  [] 
handle_fasteoi_irq+0x96/0x150
May  5 16:39:03 lyu-ubuntu kernel: [11999.623211]  [] 
handle_irq+0x1a/0x30
May  5 16:39:03 lyu-ubuntu kernel: [11999.623215]  [] 
do_IRQ+0x4b/0xd0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623220]  [] 
common_interrupt+0x82/0x82
May  5 16:39:03 lyu-ubuntu kernel: [11999.623439]  [] ? 
_nv013458rm+0x30/0x30 [nvidia]
May  5 16:39:03 lyu-ubuntu kernel: [11999.623446]  [] ? 
__do_softirq+0x7e/0x290
May  5 16:39:03 lyu-ubuntu kernel: [11999.623450]  [] 
irq_exit+0xa3/0xb0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623454]  [] 
do_IRQ+0x54/0xd0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623458]  [] 
common_interrupt+0x82/0x82
May  5 16:39:03 lyu-ubuntu kernel: [11999.623460][] 
? cpuidle_enter_state+0x10e/0x2b0
May  5 16:39:03 lyu-ubuntu kernel: [11999.623468]  [] 
cpuidle_enter+0x17/0x20
May  5 16:39:03 lyu-ubuntu kernel: [11999.623473]  [] 
call_cpuidle+0x32/0x60
May  5 16:39:03 lyu-ubuntu kernel: [11999.623476]  [] ? 
cpuidle_select+0x13/0x20
May  5 16:39:03 lyu-ubuntu kernel: [11999.623480]  [] 
cpu_startup_entry+0x290/0x350
May  5 16:39:03 lyu-ubuntu kernel: [11999.623485]  [] 
start_secondary+0x154/0x190
May  5 16:39:03 lyu-ubuntu kernel: [11999.623487] handlers:
May  5 16:39:03 lyu-ubuntu kernel: [11999.623492] [] 
usb_hcd_irq
May  5 16:39:03 lyu-ubuntu kernel: [11999.623495] Disabling IRQ #20


The currently running kernel version is 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 
18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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: nobody cared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578552/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565194] [NEW] Files button disappears from unity launcher

2016-04-01 Thread Ivan Kurnosov
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 minimize the application - I have no chance to close
the application rather than killing its process with kill.

The opposite is also true: sometimes a Files instance that I have
minimised (and which has already disappeared from the launcher)
sometimes - appears back.

I cannot determine under what circumstances it happens, but it's more
often happens than not.

In the attachment there is a gif file with the problem demostration.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-desktop 1.354
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr  2 17:09:58 2016
InstallationDate: Installed on 2016-02-07 (54 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "desktop-2.gif"
   
https://bugs.launchpad.net/bugs/1565194/+attachment/4620174/+files/desktop-2.gif

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565194

Title:
  Files button disappears from unity launcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1565194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1372750] Re: A patch for collecting swap utilization in openvz

2016-01-25 Thread Ivan Kurnosov
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

Title:
  A patch for collecting swap utilization in openvz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1372750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1372750] Re: A patch for collecting swap utilization in openvz

2015-11-03 Thread Ivan Kurnosov
@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 to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1372750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1230917] Re: php5-fpm logrotate errors after package switched to upstart

2014-11-16 Thread Ivan Kurnosov
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
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1230917

Title:
  php5-fpm logrotate errors after package switched to upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1230917] Re: php5-fpm logrotate errors after package switched to upstart

2014-11-16 Thread Ivan Kurnosov
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:
  php5-fpm logrotate errors after package switched to upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1392100] [NEW] Restarting pgbouncer when port is changed

2014-11-12 Thread Ivan Kurnosov
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 (since port was changed) so it waits for the
timeout and does nothing:

 * Invoking PgBouncer restart pgbouncer
sleep 0.1
sleep 0.2
sleep 0.2
sleep 0.5
sleep 1.0
sleep 1.0
sleep 2.0
   ...done.

** Affects: pgbouncer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392100

Title:
  Restarting pgbouncer when port is changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pgbouncer/+bug/1392100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1372750] [NEW] A patch for collecting swap utilization in openvz

2014-09-22 Thread Ivan Kurnosov
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 issue
and would be applicable for 5.4.0:
https://github.com/collectd/collectd/commit/1a146775d42a15202cba4e19c0fcda465705bcb8

PS: forwarded from
https://answers.launchpad.net/ubuntu/+source/collectd/+question/254877

** Affects: collectd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1372750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1238369] [NEW] `restart` target is broken (lucid)

2013-10-10 Thread Ivan Kurnosov
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 \
   /var/run/$NAME.pid --exec $DAEMON


with

start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE

** Affects: supervisor (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238369

Title:
  `restart` target is broken (lucid)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/supervisor/+bug/1238369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs