The Skrooge Team announces the release 1.10.0 version of its popular Personal Finances Manager based on KDE Frameworks.
Because Ubuntu 15.04 is in its first days of development, it’s hard to predict which kernel will be used on the final version of Ubuntu Vivid, scheduled for release in April 2014. Recently, the developers have integrated kernel 3.18 RC2, the newest, unstable kernel patch available for now.
We are pleased to announce the official release of OpenBSD 5.6. This is our 36th release on CD-ROM (and 37th via FTP/HTTP). We remain proud of OpenBSD's record of more than ten years with only two remote holes in the default install.
Since jumping to an testing install of Plasma 5 in my upgraded Kubuntu, I've been filing bugs as I find things not working. It took me a few days to notice that redshift no longer worked, because I didn't always use it. But when I had my eyes dilated for my annual eye exam, I needed it! And it crashed.
I love filing bugs using ubuntu-bug from the commandline. I would love to see KDE build this capability as well, because the little application gathers useful information automatically, and uploads it to the bug tracker. Man ubuntu-bug says it reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your system to help the developers to fix the problem and avoid unnecessary question/answer turnarounds. Dr. Konqui does this sometimes, but a little cli app would be nice as well.
It’s probably not a good idea to try and upgrade to Fedora 21 with fedup right now.
Currently Fedora 21 has a build of systemd that includes a new feature that was added upstream after the release of 216, which is intended to time out system startup if it’s not complete after 15 minutes – the idea being to avoid things like your laptop melting / starting a fire in your bag if it gets accidentally powered on, stuff like that.
Unfortunately, turns out that having a timeout that hard powers down the system if boot hasn’t completed after 15 minutes doesn’t work very well with fedup, because while fedup’s actual ‘install the updated packages’ step is running, systemd considers that boot has not ‘completed’. So if you try and fedup to Fedora 21 using a fedup environment that has the affected systemd build (like the one in the Beta tree, and also in the current 21 ‘stable’ tree), and your ‘install updated packages’ boot takes more than 15 minutes, it’ll just suddenly cut off and shut down. Obviously, there’s quite a high chance that’ll leave the system in a broken state.
Red Hat's David Malcolm remains committed to landing his just-in-time (JIT) compiler support for GCC.
For the past year Malcom has been working on GCC support as an embeddable JIT compiler that boasts various capabilities and potential along the likes of LLVM. The code is in the process of being mainlined and as of this week the third revision of the GCC JIT patches were published.
GCC JIT v3 incorporates various feedback from other GCC developers up to this point in getting the code in a state that's good for mainline. The updated code can be found via gcc-patches.
Hopefully GCC JIT will receive permission to be mainlined in time for GCC 5, which is already shaping up to be a very feature rich release with a ton of new functionality. GCC 5 will be released in 2015.
To be specific; back in the 90s when I was even less informed that I am today, there were at least three utilities that would give you a visual representation of disk space utilization.
The ones that come to mind are Norton SpeedDisk, Win98/(95 too?) defragmentation utility and Win 95/98/ME Scandisk utility which was sort of like chkdsk.
I want something that visually maps the physical disk utilization or something that provides a kludgy display of used "blocks" or "clusters". I don't have a practical reason for this; I'm already using K4dirstat for to visual storage utilization at a higher level.submitted by djronnieg
- Microsoft Still Engages in Criminal Activities Against Linux, Openwashing Efforts Continue Nonetheless
- Microsoft Openwashing and Hatred of GNU/Linux
- SCOTUS Decision Affects Not Only Patent Trolls
- The EPO Is More Corrupt Under Battistelli Than Under Alison Brimelow: Part VIII
- How to Complain About the EPO to National Delegations in Europe: Part IX
- Links 31/10/2014: Rubin Leaves Google, Neelie Kroes Ends EU Career
IT WORKED thanks everyone!!
Hello, total noob here trying to install Ubuntu 14.04 to a machine previously running winVista.
I burned the iso to a disc, booted from the disc, and went through the install screens no problem. I chose the option to clear all HDD data and install Ubuntu fresh. It all worked fine until now -- i got an error message along the lines of "could not write data" and the installer crashed. I tried to reboot, but it hangs every time at the UBUNTU screen with the loading dots.
Ctrl-alt-f1 yields a screen full of these error messagesSquasfs error:unable to read page, block 27190413 Squasfs error:unable to read fragment cache entry  Squasfs error: squashfs_read_data failed to read block 0x249f3cfa End_request: i/o error, dev sr0, sector 1202360
I have no idea what is going on. Also, how do you run commands from the ctrl-alt-f1 screen? I saw somewhere that running "parted" might fix it.
Any help would be vastly appreciated. Also, I can't boot into windows either, i get a full black screen with a white cursor if I try.
Edit: HOLYSHIT i just tried it from another disc and it got to the "try unix" desktop, im scared to install. Here goes!submitted by Lafoog
[link] [16 comments]