Ok, I now believe that my problem is that the last Linux image (kernel) update did not install correctly / completely. That image was "linux-image-3.2.0-4- amd64 Linux 3.2 for 64-bit PCs"
I believe that what has been happening since then is that, each time I've installed something else (either recommended by apper to keep the system up- to-date or as a new program I wanted) both the intended program and the Linux image attempted to install, and, typically, the intended program was installed or updated successfully, but the Linux image was not. I can't absolutely confirm that for every case before a few days ago, but, in the updates or installs I've done since then, I've noticed that the popup message that says there was a problem occurs while apper is attempting to install the new kernel. (To clarify--since that attempt about two weeks ago to install the kernel, every subsequent attempt to install anything has caused that message to popup, but, before a few days ago, I hadn't noticed that apper was re-attempting to install the Linux image). Aside: apper has installed several linux images before this one, and I never had this problem before, and typically did not reboot soon after the update-- instead, I waited until there was some other reason to reboot. So, now what do I do? Per the warning from Johann Klemmer, I want to be careful about rebooting--I don't want to attempt a reboot that might fail. Is there any log of the apper install process that would give me more information than the popup messages: <quote> Package failed to install - Apper One of the selected packages failed to install correctly. More information is available in the detailed report. </quote> And, upon clicking on Details, I get the following: <quote> subprocess installed post-installation script returned error exit status 1 </quote> Other suggestions? Thanks, Randy Kramer Aside: I suppose this might be considered somewhat rude, but I wrote the above with a headache, my glasses off, and only a cursory attempt at proofreading--I apologize! On Monday, June 27, 2016 01:48:41 PM Johann Klammer wrote: > Don't reboot until you know that the bootloader got installed correctly. > Ideally have a boot CD ready in case it goes wrong.
