Language Selection

English French German Italian Portuguese Spanish

GNOME

gEdit shows that GNOME wants to drive users away

Filed under
GNOME

Great stuff. The GNOME project is almost 17 years old. When will we see some signs of maturity, some signs of stability? It shows that the people at GNOME just want change. Like the good folks at Microsoft who want to change, change, change, until the software becomes utterly unusable, the GNOME developers want to keep changing things too.

Read more

GNOME Online Accounts 3.13.1 Ditches Twitter and Windows Live Support

Filed under
GNOME

The GNOME developers announced that the latest version of GNOME Online Accounts, 3.13.1, has arrived and comes with just a couple of changes, which are quite important.

The 3.13.x branch of GNOME is strictly for development and it will eventually evolve into the stable 3.14, but that's a long way ahead. Until then, the developer chose to make some very interesting changes

Read more

GNOME MUSIC 3.13.1 RELEASED!

Filed under
GNOME

Last Monday, GNOME Music 3.13.1 was released. Here are the changes, though some of them were already released along 3.12.1.

The code that looks up and caches the album art was rewritten by Vadim, so it was a lot faster now. Also, the album art in the Albums view will now be loaded on-scroll – they won’t load unless they are not shown in the window.

Read more

GNOME 3.13.1 Released

Filed under
GNOME

Here it is, the starting point of the GNOME 3.14 development cycle:
the 3.13.1 snapshot release.

To compile GNOME 3.13.1, you can use the jhbuild [1] modulesets [2]
(which use the exact tarball versions from the official release).

[1] http://library.gnome.org/devel/jhbuild/
[2] http://download.gnome.org/teams/releng/3.13.1/

Read more

GNOME Shell & Mutter 3.13.1 Released

Filed under
GNOME

The changes are rather light this early on into the GNOME 3.13 development cycle, and there weren't even any NEWS release files to accompany Mutter 3.13.1 and GNOME Shell 3.13.1, but both packages are now checked in for the imminent release of GNOME 3.13.1.

Read more

GNOME and the GIGO Principle

Filed under
GNOME

GNOME 3 is usually defended in terms of design excellence. However, while GNOME has been developed with close attention to design, that does not mean that its basic foundations are as grounded in design principles as you might infer.

Rather, a look at GNOME 3's early history shows that development was mostly a consistent realization of principles described early in the process -- principles founded on the impressions of the Design Team and apparently backed by little theory. This inconsistency between how GNOME is marketed and how it was actually designed seems the major reason for its sometimes rocky reception.

This is not the story GNOME tries to tell. Instead, GNOME 3 is described in language that implies a triumph of design. On its home page, GNOME 3 is described as "designed from the ground up to help you have the best possible computing experience" with words like "crafted" and "harmonious whole" added for good measure. The GNOME Shell design page has a similar emphasis, with the design expertise of the project participants mentioned in the first paragraph.

Read more

Did the GNOME 3 developers violate design principles?

Filed under
GNOME

GNOME 3 is one of the most controversial desktop environments in open source history. Flame wars have raged back and forth between GNOME 3 advocates and critics for quite a while now. Datamation examines the history of GNOME 3 and considers whether or not the GNOME 3 developers violated design principles when they created it.

Read more

Parsix GNU/Linux 6.0r0 Is an Interesting Mix of Debian and GNOME

Filed under
GNU
Linux
GNOME
Debian

Parsix GNU/Linux, a live and installation DVD based on Debian, aiming to provide a ready-to-use, easy-to-install desktop and laptop-optimized operating system, is now at version 6.0r0 and is ready for testing.

The developers' ultimate goal is to offer users an easy-to-use OS based on Debian's Wheezy branch, which makes use of the latest stable release of GNOME desktop environment.

"This version ships with GNOME Shell 3.10.3, and Linux 3.12.17 kernel built on top of rock solid Debian Wheezy (7.0) platform. All base packages have been synchronized with Debian Wheezy repositories as of April 17, 2014. This version comes with a systemd based live boot mode," reads the official announcement...

Read more

Getting Things GNOME: Summer is coming!

Filed under
GNOME

The status quo of Getting Things Gnome heavily depends on generic backend & local xml database for different third-party services. The class generic backend is inherited by backends for different services. This makes it quite difficult to add new services independent of generic backend, and maintain the core modules, including generic backend, independent of backend service sub classes.

Read more

GNOME 3.12.1 out: PDF accessibility progress

Filed under
GNOME

Welcome to a new “GNOME 3.12 is out blog post”, somewhat late because I wanted to focus on 3.12.1 instead of the usual 3.12.0, and because I was away for several days due to Easter holidays.

Read more

Syndicate content

More in Tux Machines

Browsing the web with Min, a minimalist open source web browser

Does the world need another web browser? Even though the days of having a multiplicity of browsers to choose from are long gone, there still are folks out there developing new applications that help us use the web. One of those new-fangled browsers is Min. As its name suggests (well, suggests to me, anyway), Min is a minimalist browser. That doesn't mean it's deficient in any significant way, and its open source, Apache 2.0 license piques my interest. Read more

Security: Patches, FUD and Voting Machines

  • libssh 0.8.4 and 0.7.6 security and bugfix release

    libssh versions 0.6 and above have an authentication bypass vulnerability in the server code. By presenting the server an SSH2_MSG_USERAUTH_SUCCESS message in place of the SSH2_MSG_USERAUTH_REQUEST message which the server would expect to initiate authentication, the attacker could successfully authentciate without any credentials.

  • A Cybersecurity Weak Link: Linux and IoT [Ed: Blaming "Linux" for companies that put default passwords on all their products? Windows has back doors.]
  • Undetectably bypass voting machines' anti-tamper mechanism with a bit of a soda-can

    But University of Michigan grad student Matt Bernhard has demonstrated that he can bypass the tamper-evident seals in seconds, using a shim made from a slice of a soda can. The bypass is undetectable and doesn't damage the seal, which can be resecured after an attacker gains access to the system.

  • Security Seals Used to Protect Voting Machines Can Be Easily Opened With Shim Crafted from a Soda Can

    Bernhard, who is an expert witness for election integrity activists in a lawsuit filed in Georgia to force officials to get rid of paperless voting machines used in that state, said the issue of security ties and seals came up in the lawsuit earlier this year when Fulton County Elections Director Richard Barron told the court that his Georgia county relies on tamper-evident metal and plastic ties to seal voting machines and prevent anyone with physical access to the machines from subverting them while they sit in polling places days before an election.

    [...]

    He noted that defeating ties and seals in non-tamper-evident ways isn’t the only method to wreak havoc on an election in Michigan. The state has a unique law that prohibits ballots from being used in a recount if the number of voters doesn't match the number of ballots cast at a precinct or if the seal on a ballot box is broken or has a different serial number than what it should have. Someone who wanted to wreak havoc on an election or alter an election outcome in Michigan could purposely tamper with ballot box seals in a way that is evident or simply replace them with a seal bearing a different serial number in order to get ballots excluded from a recount. The law came into sharp relief after the 2016 presidential election when Green Party candidate Jill Stein sought to get a statewide recount in Michigan and two other critical swing states and found that some precincts in Wayne County couldn't be recounted because the number of voters who signed the poll books—which get certified with a seal signed by officials—didn't match the number of ballots scanned on the voting machines.

OSS: Hedera Hashgraph, Service Providers, and Renaming the Bro Project

  • Hedera Hashgraph Distributed Ledger Technology Shares New Open-Source SDK [Ed: Hedera needs to delete GitHub, however, as the new head of GitHub killed Java projects like Hedera's]
    Hedera Hashgraph, one of the DApp facilitators within the blockchain industry recently announced that it has released its Software Development Kit (SDK) in Java.
  • Service Providers Should Adapt to Open Source World
    Finding differing opinions on open source with the telecom industry isn't hard to do, especially where orchestration is concerned. That's why a panel discussion on open source and MANO at the Light Reading NFV-Carrier SDN event in Denver seemed an odd place to find such outspoken agreement on that topic, but there it was. Four smart guys, none shy with their opinions, all seemed to agree on key points around open source, the need for standards, the role of vendors and the lack of internal software skills. But they also agreed that telecom service providers are struggling a bit to understand how to proceed in an open source world and still need some fundamental internal changes.
  • Renaming the Bro Project
    More than 20 years ago I chose the name "Bro" as "an Orwellian reminder that monitoring comes hand in hand with the potential for privacy violations", as the original Bro paper put it. Today that warning is needed more than ever ... but it's clear that now the name "Bro" is alas much more of a distraction than a reminder. On the Leadership Team of the Bro Project, we heard clear concerns from the Bro community that the name "Bro" has taken on strongly negative connotations, such as "Bro culture". These send a sharp, anti-inclusive - and wholly unintended and undesirable - message to those who might use Bro. The problems were significant enough that during BroCon community sessions, several people have mentioned substantial difficulties in getting their upper management to even consider using open-source software with such a seemingly ill-chosen, off-putting name.

Back End: Apache Kafka, 'Serverless'