https://bugzilla.novell.com/show_bug.cgi?id=824037 https://bugzilla.novell.com/show_bug.cgi?id=824037#c0 Summary: Apper Fails to Install New Kernel, With Error, if Insufficient Space Exists on Device Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bwayson@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.3 Safari/534.34 Apper asked me to report this bug. Apper failed to install a new kernel because insufficient space existed in my boot partition. It failed with a message similar to 'Apper experienced an unexpected problem....' It apparently did not check for sufficient disk space prior to beginning the installation. By default, openSUSE 12.3 keeps two kernels in the /boot directory. I deleted the older one from the command line, and then Apper installed the new kernel without error. Reproducible: Always Steps to Reproduce: 1. Create a separate boot partition of 130 MB 2. Install openSUSE 12.3 3. Have two kernel versions installed 4. Have Apper try to install, thorugh the normal software update process, a kernel version newer than the two installed kernels Actual Results: Apper starts to install the third kernal, then produces an error message similar to 'Apper has experienced an undespected problem.' Expected Results: Apper would first check for sufficient device space and not attempt the installation if it is found (or, at least, produce an 'Insufficent device space' error message when the installation failed). Additionally some guidance for the less technical user on how to free up privileged disk space (i.e. space that can only be modified by root) would be helpful in an event like this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.