← Back to team overview

kernel-packages team mailing list archive

[Bug 341200] Invitation to connect on LinkedIn

 

LinkedIn
------------


Bug,

I'd like to add you to my professional network on LinkedIn.

- Jesse

Jesse Berwald
Postdoctoral Fellow at Institute for Mathematics and its Applications
Greater Minneapolis-St. Paul Area

Confirm that you know Jesse Berwald:
https://www.linkedin.com/e/-4npow2-hqx50eu5-5s/isd/19637190944/oqdfgKYz/?hs=false&tok=2bGs4Eunp8IC41

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-4npow2-hqx50eu5-5s/qkG496gDUoXT0homvQqxf39D1rZZUEwzFZlcGcs/goo/341200%40bugs%2Elaunchpad%2Enet/20061/I6349535804_1/?hs=false&tok=3O9VRnlrR8IC41

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA
94043, USA.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/341200

Title:
  linux-(image or headers)-2.6.27-13 update breaks login screen

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: linux-image-2.6.27-13-generic

  On 3/6/09 the update manager brought up a host of linux-image and
  linux-header files to update (new version=2.6.27-13). After updating
  to the above version and rebooting, no login screen appears. The boot
  process appears to be working fine, but ends in a blank screen. My
  current workaround is to enter grub and boot the last version (XXX-12
  kernel).

  Also, this brings up a quick question about Synaptic for these sorts
  of situations. I attempted to uninstall the offending update via
  Synaptic but got nervous when the "Packages to be removed" screen
  reported that it would simply remove the linux-image-generic package
  when I had actually selected the XXX-13 version for removal. I suspect
  that upon removal "generic" would then get replaced by the last one
  (XXX-12), but since the kernel is not something I have time to "lose"
  these days, I'm sticking with my hackish workaround. But any advice on
  slick removal of the offending update would be appreciated as well.

  thanks for the help,
  -Jesse

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