> > - The worst aspect of Fedora 16 is it has made computing a stochastic > > process. Instead of the rock-solid behaviour of previous releases, > > Fedora 16 behaves randomly. On the specific boxes you have (not a statistically valid sample). On my boxes for example 16 is way better than 15 (which was utter trash) > > - The command 'reboot' typed in an X terminal emulator, sometimes > > works; but often hangs the machine, requiring pressing reset. > What are your system specs? If you wanna criticize, do it in a > constructive manner so people can fix issues. Really useful here would be the actual logs of the end of the fail and the dmidecode of the box. Certainly we've got some cases of boxes hanging on the final step of shutdown/reboot with current kernels and that isn't a Fedora issue but a general kernel one. Mind you I've also seen systemd fail the reboot service and get itself in a right mess so it could be either. > > - The 'df' command has been rendered nearly useless due to the > > voluminous extraneous output. > df | grep sda :) > > - The mount command, which was once useful, isn't any more. It's > > simply unreadable. > See above. More to the point df is doing what it is required to do. Fedora now uses tmpfs for a variety of temporary things. That is on the whole good particularly on systems with slow storage. > > - The latest kernel, 3.1.7-1.fc16.x86_64, causes skype to crash > > unless it is run with strace, in which case it fails to fail. > > Go figure! Probably a skype problem, however skype is impossible for anyone but Skype to debug so please report it there. It's beyond even the usual proprietary problems as its intentionally self encrypting and obfuscated to prevent anyone reverse engineering their protocols. > > - The session manager for xfce seems unable to restart roxterm > > windows, but can handle xterm's fine. Why? session managers record what the app provides for restart. If roxterm doesn't provide valid session data it won't restart. > > - Libreoffice insists on making files inaccessible via nfs. > > A workaround is to edit /usr/lib64/libreoffice/program/soffice to > > comment out these two lines: > > ## SAL_ENABLE_FILE_LOCKING=1 ## export SAL_ENABLE_FILE_LOCKING > > but this must be redone whenever a new update comes along. Your NFS setup needs to have locking enabled. That's probably a configuration error on your NFS server. > > - The microphone on one machine (but not others) wouldn't work until I > > added a cryptic line to the beginning of > > /etc/modprobe.d/dist-alsa.conf: > > options snd-hda-intel model=auto dmidecode, lspci -vv and report to the alsa developers. Alan -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
