[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system

2017-06-08 Thread amichair
Thanks for the analysis @atom, I think that explains my issue as well -
I had a long-running rsync in parallel. Once killed, the update worked.

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

Title:
  update-initramfs hangs on upgrade, dpkg unusable, unbootable system

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  At least four users, including myself, are having an issue with
  update-initramfs hanging while updating ubuntu 16.04. The bug has been
  documented while attempting an update to multiple kernel versions (
  4.4.0-24, 4.4.0-62,  4.4.0-63). The bug causes any apt-get update or
  install to fail, and may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)   
  
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for cracklib-runtime (2.9.2-1build2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic

   Uh oh! Let's try to troubleshoot.

  $ sudo killall dpkg
  $ sudo dpkg --configure -a
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Setting up base-files (9.4ubuntu4.4) ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  initrd.img(/boot/initrd.img-4.4.0-63-generic
  ) points to /boot/initrd.img-4.4.0-63-generic
   (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  vmlinuz(/boot/vmlinuz-4.4.0-63-generic
  ) points to /boot/vmlinuz-4.4.0-63-generic
   (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
  ^CFailed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-63-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.4.0-63-generic; however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-signed-image-4.4.0-63-generic:
   linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic 
(= 4.4.0-63.84); however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-signed-image-generic:
   linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; 
however:
Package linux-signed-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-image-extra-4.4.0-63-generic:
   linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; 
however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-extra-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   lin

[Touch-packages] [Bug 1541751] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2016-05-04 Thread amichair
After upgrade to Kubuntu 16.04 with kernel 4.4.6-040406-generic, the
crashes seem to have stopped, although the error messages are still
there. Maybe they were unrelated, or maybe the error is handled more
gracefully now...

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Kubuntu 15.10, KDE Framework 5.18.0, Qt 5.5.1, kernel
  4.4.1-040401-generic from http://kernel.ubuntu.com/~kernel-
  ppa/mainline/ (I upgraded hoping it would solve the problem, but it
  did not). Haswell i7-4771 with integrated GPU (no other graphics
  card). 3-monitor setup.

  Several times a day the display seems to crash in various ways, some
  recoverable (e.g. by restarting plasmashell or sddm) but sometimes a
  monitor stays blank, corrupt or unresponsive and only a full reboot
  helps. I also see a plasma crash dialog every time I return to my
  desktop after the screens went into power-savings mode when I was away
  (I don't know if this is related or a plasma bug). It also happens
  sometimes while dragging a windows (desktop effects are on), while
  watching a video (I now get occasionally a few seconds with black
  output in the middle of the video too). It's hard to pinpoint which
  components are unstable, likely more than one, but this is a starting
  point since I get the following message in dmesg which I assume is at
  a lower level than the desktop environment (correct me if I'm wrong):

  [Thu Feb  4 10:44:20 2016] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe A
  [Thu Feb  4 10:44:20 2016] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] 
*ERROR* CPU pipe A FIFO underrun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541751/+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 1385709] Re: network-manager service doesn't start at boot time

2014-10-25 Thread amichair
After wasting a whole day on this, I think I found the culprit. I had to
delete a whole bunch of files named 'sendmail' which were scattered
around /etc (/etc/ppp/ip-up.d/sendmail /etc/ppp/ip-down.d/sendmail
/etc/network/if-post-down.d/sendmail /etc/network/if-up.d/sendmail
/etc/network/if-down.d/sendmail /etc/dhcp3/dhclient-exit-
hooks.d/sendmail /etc/resolvconf/update-libc.d/sendmail, and there are a
few more that should probably also be deleted). Note that I do not have
the sendmail package installed at all!

I do not know, however, why the upgrade to 14.10 triggered this failure.
Maybe it removed something related to sendmail, or started doing
something with these files that were previously ignored... dunno. In any
case, it's a pretty serious upgrade bug, since it prevents the network
from connecting, and is quite non-trivial to trace back to its origin
(there were lots of other errors/warnings in syslog that seemed related
but weren't, and nothing there about these sendmail files or a hint as
to the cause of failure).

The indirect reason this happens on wired connections is probably that
there is a correlation between hosts which at some point had sendmail
installed and those that are on a wired connection :-)

Please fix this issue quickly before others upgrade and lose their
connectivity... (already encountered someone else with the same
symptoms).

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

Title:
  network-manager service doesn't start at boot time

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had
  any network trouble before the upgrade. After the upgrade, the
  network-manager service does not start when the computer boots up -
  the Kubuntu splash screen says 'waiting for network configuration',
  then 'waiting another 60 seconds for network configuration' (or
  something like that), then finally boots up without a network
  connection. Also the Network Management tray icon tooltip says that
  the network-manager service is not running. However if I then manually
  open the terminal and run 'sudo service network-manager start', then
  it starts ok and the network connects within a few seconds and
  everything works ok until the next reboot. I'm on a desktop PC with a
  wired LAN connection and no wifi adapter. network-manager version is
  0.9.8.8-0ubuntu28.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1385709/+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 1385709] [NEW] network-manager service doesn't start at boot time

2014-10-25 Thread amichair
Public bug reported:

I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had
any network trouble before the upgrade. After the upgrade, the network-
manager service does not start when the computer boots up - the Kubuntu
splash screen says 'waiting for network configuration', then 'waiting
another 60 seconds for network configuration' (or something like that),
then finally boots up without a network connection. Also the Network
Management tray icon tooltip says that the network-manager service is
not running. However if I then manually open the terminal and run 'sudo
service network-manager start', then it starts ok and the network
connects within a few seconds and everything works ok until the next
reboot. I'm on a desktop PC with a wired LAN connection and no wifi
adapter. network-manager version is 0.9.8.8-0ubuntu28.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  network-manager service doesn't start at boot time

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had
  any network trouble before the upgrade. After the upgrade, the
  network-manager service does not start when the computer boots up -
  the Kubuntu splash screen says 'waiting for network configuration',
  then 'waiting another 60 seconds for network configuration' (or
  something like that), then finally boots up without a network
  connection. Also the Network Management tray icon tooltip says that
  the network-manager service is not running. However if I then manually
  open the terminal and run 'sudo service network-manager start', then
  it starts ok and the network connects within a few seconds and
  everything works ok until the next reboot. I'm on a desktop PC with a
  wired LAN connection and no wifi adapter. network-manager version is
  0.9.8.8-0ubuntu28.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1385709/+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