On Fri, 3 Mar 2017 18:27:40 +0000 Joseph Salisbury <[email protected]> wrote:
> Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular > problem? I first started having issues with this problem this fall. I've taught a UNIX programming course for over 15 years and this is the first time students have had a problem with this. Our computers were upgraded to 16/4 during the summer. This is not a kernel bug. This is a stdio bug. > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the > latest v4.10 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug > as "Confirmed". I'll see if I can check it out for the latest version. --Phil -- Phil Nelson, Computer Science at WWU http://facultyweb.cs.wwu.edu/~phil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669149 Title: improper lseek in stdio code called via exit(3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669149/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
