[Touch-packages] [Bug 1863165] Re: autoremove-kernels doesn't purge kernels

2020-02-15 Thread Christian Kujau
I'd consider having remnants of old package versions (and lots of them)
to be a bug, but it's your distribution, so having this dismissed is an
answer to this problem nonetheless. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165

Title:
  autoremove-kernels doesn't purge kernels

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Maybe this is a configuration issue, but:

  # apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  # dpkg -l | grep ^rc | cut -c-70
  rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
  rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
  rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
  rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
  rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
  rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
  rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
  rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
  rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
  rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
  rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
  rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
  rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
  rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
  rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
  rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext

  And the "rc" translates to "Remove/Conf-files". For some reason
  /etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
  upgrades.service) doesn't seem to remove the kernel's configuration
  files.

  The kernel images and modules are removed, only the package list (and
  maybe /usr/share/doc/linux*) is cluttered with the remnants of old
  kernels.

  Workaround:

   dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
  -P

  # lsb_release -r; dpkg -s apt | grep Ver; uname -r
  Release:18.04
  Version: 1.6.12
  5.3.0-23-generic

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1863165] Re: autoremove-kernels doesn't purge kernels

2020-02-14 Thread Christian Kujau
** Changed in: apt (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165

Title:
  autoremove-kernels doesn't purge kernels

Status in apt package in Ubuntu:
  New

Bug description:
  Maybe this is a configuration issue, but:

  # apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  # dpkg -l | grep ^rc | cut -c-70
  rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
  rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
  rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
  rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
  rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
  rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
  rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
  rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
  rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
  rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
  rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
  rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
  rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
  rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
  rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
  rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext

  And the "rc" translates to "Remove/Conf-files". For some reason
  /etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
  upgrades.service) doesn't seem to remove the kernel's configuration
  files.

  The kernel images and modules are removed, only the package list (and
  maybe /usr/share/doc/linux*) is cluttered with the remnants of old
  kernels.

  Workaround:

   dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
  -P

  # lsb_release -r; dpkg -s apt | grep Ver; uname -r
  Release:18.04
  Version: 1.6.12
  5.3.0-23-generic

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1863165] Re: autoremove-kernels doesn't purge kernels

2020-02-13 Thread Christian Kujau
So, how can I convince APT to _automatically_ remove all kernel
leftovers? I could of course run a cron job with the workaround, but
maybe this can be done The Right Way? :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165

Title:
  autoremove-kernels doesn't purge kernels

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Maybe this is a configuration issue, but:

  # apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  # dpkg -l | grep ^rc | cut -c-70
  rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
  rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
  rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
  rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
  rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
  rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
  rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
  rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
  rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
  rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
  rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
  rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
  rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
  rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
  rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
  rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext

  And the "rc" translates to "Remove/Conf-files". For some reason
  /etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
  upgrades.service) doesn't seem to remove the kernel's configuration
  files.

  The kernel images and modules are removed, only the package list (and
  maybe /usr/share/doc/linux*) is cluttered with the remnants of old
  kernels.

  Workaround:

   dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
  -P

  # lsb_release -r; dpkg -s apt | grep Ver; uname -r
  Release:18.04
  Version: 1.6.12
  5.3.0-23-generic

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1863165] [NEW] autoremove-kernels doesn't purge kernels

2020-02-13 Thread Christian Kujau
Public bug reported:

Maybe this is a configuration issue, but:

# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext

And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.

The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.

Workaround:

 dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg -P

# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic

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

** Description changed:

  Maybe this is a configuration issue, but:
- 
  
  # apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  
- # dpkg -l | grep ^rc | cut -c-80
- rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel image 
generic
- rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel image 
generic
- rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel extra 
modules
- rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel extra 
modules
+ # dpkg -l | grep ^rc | cut -c-70
+ rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
+ rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
+ rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
+ rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
+ rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
+ rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
+ rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
+ rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
+ rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
  
- 
- And the "rc" translates to "Remove/Conf-files". For some reason 
/etc/apt/apt.conf.d/01autoremove-kernels 

[Touch-packages] [Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup

2017-12-10 Thread Christian Kujau


-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/556372

Title:
  Please remove the plymouth dependency from mountall / cryptsetup

Status in cryptsetup:
  Fix Released
Status in mountall package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: mountall

  I noticed that mountall (and cryptsetup) depends on plymouth now.
  Whatever plymouth is doing or not doing, my headless system is booting
  fine without plymouth (dpkg --force-depends -P plymouth), yet all
  disks (local, NFS) are mounted and cryptsetup is setting up encrypted
  swap as it used to.

  IMHO the "Depends: plymouth" is too hard and should be replaced with
  "Recommends:" or "Suggests:" for the following reasons:

  - Headless systems won't ever see what plymouth is doing ("graphical boot 
animation")
  - Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily 
adding code to the installation- Mountall is of "Priority: required" while 
plymouth is "optional". The "Depends:" makes plymouth essentially "required" as 
well and cannot be uninstalled w/o --force options.

  Please reconsider this dependency.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu lucid (development branch)
  Release:10.04
  Codename:   lucid

  # dpkg -l | egrep 'mountall|cryptsetup' | cut -c1-90
  ii  cryptsetup  
2:1.1.0~rc2-1ubuntu13 
  ii  mountall2.10 

  # apt-cache show plymouth | egrep 'Vers|Depe'
  Version: 0.8.1-4ubuntu1
  Depends: libc6 (>= 2.8), libdrm-intel1 (>= 2.4.9), libdrm-nouveau1 (>= 
2.4.11-1ubuntu1~), libdrm-radeon1 (>= 2.4.17), libdrm2 (>= 2.4.3), libplymouth2 
(= 0.8.1-4ubuntu1), upstart-job, udev (>= 149-2), mountall (>= 2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2017-11-04 Thread Christian Kujau
*** This bug is a duplicate of bug 578431 ***
https://bugs.launchpad.net/bugs/578431

** This bug has been marked a duplicate of bug 578431
   wpa_supplicant spams syslog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2017-10-30 Thread Christian Kujau
Launchpad really needs something similar to RESOLVED/DUPLICATE, as I had
to crawl through the whole report to find out that this is considered a
duplicate of 578431.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 555852] Re: Make it possible to use ULOG instead of LOG

2017-03-02 Thread Christian Kujau
I guess bug #1475676 would be the logical consequence here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/555852

Title:
  Make it possible to use ULOG instead of LOG

Status in ufw package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: ufw

  This is related to bug #244232 I guess.

  I dislike using the LOG target, as it pollutes the dmesg output and
  kern.log. I prefer to use ULOG, as this causes the logged messages to
  go to /var/log/ulog/syslogemu.log by default.

  Please add a configuration option or configuration file option to
  generate the Netfilter rules with the ULOG target instead of the LOG
  target.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2014-11-14 Thread Christian Kujau
Same here, every 2 minutes with wpa_supplicant v2.3:

$ sudo grep wpa_supplicant /var/log/messages | grep -v WPA | tail -3
Nov 14 11:24:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs 
failed: -33
Nov 14 11:26:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs 
failed: -33
Nov 14 11:28:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs 
failed: -33

No connectivity issues though, rekeying happens just fine every 10min:

$ sudo grep wpa_supplicant /var/log/messages | grep WPA | tail -3
Nov 14 11:07:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:17:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:27:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]

Wifi chip:
04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in “wpa” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 398670] Re: eject: unable to eject, last error: Inappropriate ioctl for device

2014-09-17 Thread Christian Kujau
This just happened here with eject-2.1.5, but using eject -i off as
suggested by zheoffec in comment #2 helped - thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eject in Ubuntu.
https://bugs.launchpad.net/bugs/398670

Title:
  eject: unable to eject, last error: Inappropriate ioctl for device

Status in “eject” package in Ubuntu:
  Invalid

Bug description:
  When issuing an eject command on the console, I get:

  $ eject
  eject: unable to eject, last error: Inappropriate ioctl for device

  $ dmesg
  reports:

  [  149.469374] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  149.469380] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] 
  [  149.469385] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track
  [  149.469393] end_request: I/O error, dev sr0, sector 0
  [  149.469397] __ratelimit: 68 callbacks suppressed
  [  149.469400] Buffer I/O error on device sr0, logical block 0
  [  149.469403] Buffer I/O error on device sr0, logical block 1
  [  149.469407] Buffer I/O error on device sr0, logical block 2
  [  149.469410] Buffer I/O error on device sr0, logical block 3
  [  149.469412] Buffer I/O error on device sr0, logical block 4
  [  149.469415] Buffer I/O error on device sr0, logical block 5
  [  149.469417] Buffer I/O error on device sr0, logical block 6
  [  149.469419] Buffer I/O error on device sr0, logical block 7
  [  149.469422] Buffer I/O error on device sr0, logical block 8
  [  149.469424] Buffer I/O error on device sr0, logical block 9
  [  149.486612] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  149.486618] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] 
  [  149.486623] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track
  [  149.486630] end_request: I/O error, dev sr0, sector 0
  [  149.503096] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  149.503105] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] 
  [  149.503112] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track
  [  149.503121] end_request: I/O error, dev sr0, sector 0
  [  149.505347] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  149.505360] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] 
  [  149.505373] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track
  [  149.505390] end_request: I/O error, dev sr0, sector 0

  Even if the CD cannot be read, I should still be able to eject it!

  $ eject -v
  eject: using default device `cdrom'
  eject: device name is `cdrom'
  eject: expanded name is `/dev/cdrom'
  eject: `/dev/cdrom' is a link to `/dev/sr0'
  eject: `/dev/sr0' is not mounted
  eject: `/dev/sr0' is not a mount point
  eject: `/dev/sr0' is not a multipartition device
  eject: trying to eject `/dev/sr0' using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: trying to eject `/dev/sr0' using SCSI commands
  eject: SCSI eject failed
  eject: trying to eject `/dev/sr0' using floppy eject command
  eject: floppy eject command failed
  eject: trying to eject `/dev/sr0' using tape offline command
  eject: tape offline command failed
  eject: unable to eject, last error: Inappropriate ioctl for device

  $ lsb_release -rd
  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  $ apt-cache policy eject
  eject:
Installed: 2.1.5+deb1+cvs20081104-6
Candidate: 2.1.5+deb1+cvs20081104-6
Version table:
   *** 2.1.5+deb1+cvs20081104-6 0
  500 http://de.archive.ubuntu.com karmic/main Packages
  500 http://us.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp