Language Selection

English French German Italian Portuguese Spanish

Linuxinsight

Syndicate content
LinuxInsight - aggregated feeds
Updated: 1 hour 35 min ago

LXer: It's Time for Open Citations

Friday 7th of April 2017 01:08:09 AM
Mozilla is signing on to the Initiative for Open Citations (I4OC). We believe open data is integral to a healthy Internet [he]#8212[/he] and to a healthy society. ? Today, Mozilla is announcing support for the Initiative for Open Citations (I4OC), [he]#8230[/he] Read moreThe post It’s Time for Open Citations appeared first on The Mozilla Blog.

Phoronix: GNOME Could Soon Have An Alternative To Microsoft Paint

Friday 7th of April 2017 12:59:36 AM
While there is GIMP for advanced image manipulation and then a few other alternatives for more simpler image manipulation or drawing, a new "GNOME Paint" program is in development...

Reddit: The situation with Wayland need to change

Friday 7th of April 2017 12:20:34 AM

This is coming from a guy who abandoned Wayland and have succeeded creating an alternative in-house Display Server for enterprise office. I've worked with DRM/KMS, EGL, EGLStream/GBM, RT (Shared Memory library), and GL. I wanted Wayland to succeed, but the way things are going right now, they are not doing well at all.

The Reasons why I abandoned Wayland:

  1. Lack of documentation
  2. Security Model Bullshit
  3. Using an alternative library as an excuse for convoluted API in Wayland
  4. API Need to be more Layman-friendly
  5. Proposal to use an alternative model (hear me out on this)

There are lack of tutorials for writing Compositor or even a Client Wayland. I think this need to be said before we discuss documentation for Wayland, we cannot and shouldn't force everyone to use GUI Toolkit like GTK, QT4/5 or WxWidgets, it's that simple. The documentation for using Wayland protocol is nearly nonexistent and we only have a reference for implementation for Wayland. The tutorial for using Wayland is the closest thing you have for a tutorial on Wayland and it's out of date (XDG Surface isn't covered.) If Wayland developers want widespread adoption of their protocol and to avoid display protocol fragmentation, there is no excuse for having almost no documentation, tutorials, or explanation on their protocol. They should explain beginning to the end on how to implement Compositor and Client side windows.

The current Wayland developer's excuses for not implementing features for security reason is entirely bullshit. There are thousands of alternative methods that could balance the needs for security and features such as showing a confirmation dialog to the users from Compositor whenever application need access to recording entire screen or to hook global input. Those excuses need to end.

Lately, I've been hearing a lot from many Wayland Developers that while they fail to document their shit, they actually refer you to use SWC library as an excuse to not document their shit for Compositor and SWC library is still pale in comparison to Gnome/KDE features. Also if you ever want to make your own GUI Toolkit, you're in for an uphill battle and the most common excuses for that is you have to use something like GTK to create the window (The ENTIRE GTK Library and all of it dependencies just to create one bloodly window) and slap on whatever rendering engine you use. People shouldn't be forced to use whatever renown GUI Toolkit just to make their own GUI Toolkit.

There are no explanation for how Wayland is supposed to be used for any beginners or immediate programmers, you have to deal with knowing what the event loop is, what calls are needed to query the input, damage the surface, keeping track of events, how to modeset and create a framebuffer in DRM/KMS, how to work with EGLStream or GBM, how to use OpenGL, and so forth. It's overwhelming for anyone who wanted to create their own compositor or a GUI application and we need to simplify the protocol so everyone know what pieces goes where.

Here my alternative take on this, let's centralize all of the complicated backend code under Wayland similarly to XServer, but instead of having compositor making a connection to XServer like what X11 been doing, people can make their own library that adjust the logics of Wayland Server based similar to events and callbacks.

Let's assume this:

We have a header file for use by both Wayland Server and User's Defined Compositor Library that have a definition for all of the eventhandlers within a struct like so:

typedef struct { void (*OnMouseMove)(int32_t x, int32_t y); ... } CompositorEventHandlers;

The Wayland Server would import the User's Defined Compositor Library with dlopen/dlclose/dlsym functions from DL library. So Wayland Server can query the compositor library if a symbol such as "OnWaylandInit" exists and then call the function from that symbol to receive the CompositorEventHandlers struct from that library.

So from Wayland Server code, we would have this:

char* pathToLib ...

void* handle = dlopen(pathToLib, RTLD_LAZY);

CompositorEventHandlers* (*)() OnInitCall = dlsym(handle, "OnWaylandInit");

CompositorEventHandlers* OurEventHandlers = OnInitCall();

And from User Defined Compositor Library, they can set their own logics for Compositor Event Handlers above and Wayland will execute those event handlers when needed. There you go, massive headache of reading their protocol is simplified down to just handling the events that can consistently be expanded and improved on while suffering almost no performance penalty compared to XServer in X11. On top of that, this enables us to provide some REAL abstraction for such a complicated back-end codes.

Inb4 OP is a faggot.

submitted by /u/AntiTrustMicrosoft
[link] [comments]

LXer: Ubuntu convergence implodes

Friday 7th of April 2017 12:06:37 AM
With Ubuntu 18.04 LTS, Canonical will replace Ubuntu’s touch-enabled Unity8 “convergence” desktop with GNOME, thereby abandoning its mobile ambitions. Ubuntu’s Unity desktop and its related Ubuntu Phone project were always long-shots, so it was not unexpected that Canonical would eventually call a retreat. That is exactly what Ubuntu founder Mark Shuttleworth did in an April […]

Reddit: Advanced Bash-Scripting Guide

Thursday 6th of April 2017 11:42:06 PM

LXer: Ubuntu Boosts Linux Performance on AWS Cloud

Thursday 6th of April 2017 11:05:05 PM
Running Ubuntu Linux on the Amazon Web Services (AWS) cloud is a fairly common practice. Though Ubuntu has been available in the AWS marketplace for years, until recently there wasn't a version of Ubuntu with a Linux kernel that was specifically tuned for the AWS environment.

Reddit: What should I tell my brother ? I wanted to burn a live usb to fix my install but used dd on the wrong disk... :(

Thursday 6th of April 2017 10:52:38 PM

I wonder why echo still works despite having no more /bin, even ls and cd don't work.

I feel even more stupid than the guy who did rm /bin/rm, at least he did it on purpose...

submitted by /u/EizanPrime
[link] [comments]

Linux.com: APIStrat

Thursday 6th of April 2017 10:14:46 PM

The API Strategy & Practice Conference, known as APIStrat, is a conference focused on the API economy. The eighth edition of the conference will bring together everyone – from the API curious to today's leaders – to discuss opportunities and challenges in the API space.

Event Title: APIStrat6 AprLearn more

Reddit: Trouble uninstalling Linux program.

Thursday 6th of April 2017 10:13:22 PM

I am having trouble uninstalling Genymotion that was installed into my download directory. Can anyone provide assistance please? Not sure where to ask, so hope this is an okay post. Thanks all!

submitted by /u/obtheobbie
[link] [comments]

LXer: OpenGL vs Vulkan in Mad Max, re-tested

Thursday 6th of April 2017 10:03:33 PM
Since Feral Interactive have fixed up the OpenGL renderer in the Mad Max Beta, here are some fresh OpenGL vs Vulkan tests.

TuxMachines: AMDGPU vs. Radeon DRM With GCN 1.0/1.1 GPUs On Linux 4.11, Mesa 17.1-dev

Thursday 6th of April 2017 09:54:57 PM

With the upcoming Linux 4.11 kernel release as well as for the next cycle (Linux 4.12), the Radeon DRM driver remains the default for AMD GCN 1.0/1.1 GPUs while the newer AMDGPU DRM driver continues offering "experimental" support for these earlier generations of GCN GPUs. As it's been a while since our last Radeon vs. AMDGPU GCN 1.0/1.1 benchmarks, here are some fresh tests today with Linux 4.11 Git.

read more

TuxMachines: SODIMM-style COM sharpens IoT focus with i.MX6 ULL SoC

Thursday 6th of April 2017 09:50:55 PM

iWave has replaced an earlier i.MX6 UL module with an almost identical “iW-RainboW-G18M-SM” COM equipped with the more power efficient i.MX6 ULL.

iWave has re-released its two-year old iW-RainboW-G18M computer-on-module as a new iW-RainboW-G18M-SM COM that cashes in the old i.MX6 UltraLite (UL) SoC for NXP’s even more energy efficient i.MX6 ULL. The original COM still has its own pull-down menu entry, but when you click on it you are redirected to the new iW-RainboW-G18M-SM. The similarly Linux-driven, SODIMM-style module seems to be identical except for the new SoC. There is, however, a new Pico-ITX development platform, which we cover below.

read more

LinuxToday: Samba 4 Domain Controller Installation on CentOS 7

Thursday 6th of April 2017 09:00:00 PM

HowToForge: Starting from version 4.0, Samba is able to run as an Active Directory (AD) domain controller (DC)

LXer: Linux-driven SODIMM COM lightens up with i.MX6 ULL

Thursday 6th of April 2017 08:58:24 PM
iWave has replaced an earlier i.MX6 UL module with an almost identical “iW-RainboW-G18M-SM” COM equipped with the more power efficient i.MX6 ULL. iWave has re-released its two-year old iW-RainboW-G18M computer-on-module as a new iW-RainboW-G18M-SM COM that cashes in the old i.MX6 UltraLite (UL) SoC for NXP’s even more energy efficient i.MX6 ULL. The original COM […]

Reddit: A post not about Ubuntu

Thursday 6th of April 2017 08:44:29 PM

As a person that uses neither Ubuntu nor GNOME, I feel like whenever there's an Ubuntu announcement, this place becomes pure blogspam garbage for the next 3 days.

So I made this post to balance things out. Hi. Is there any decent way to manage RSS subscriptions in Akregator across devices? If need be, I'll just sync the directory it stores them in once I find out where that is.

submitted by /u/CounterPillow
[link] [comments]

Linux.com: Speak at The Linux Foundation’s Open Source Summit North America in L.A.

Thursday 6th of April 2017 08:30:00 PM
Title: Speak at The Linux Foundation’s Open Source Summit North America in L.A.6 AprLearn more

More in Tux Machines

GNOME News

  • GNOME's JavaScript Component Will Be Seeing More Improvements For 3.26
    GJS -- the GNOME JavaScript system that allows for GObject introspection and other capabilities via JavaScript on the desktop -- is planning for further improvements with GNOME 3.26.
  • Show desktop icon in Gnome 3 - Where and how
    Despite my recently found liking for Gnome 3, largely because of Fedora 24 and Fedora 25, plus some rigorous work with extensions like Dash to Dock, it is still a highly inefficient desktop environment. The unnecessary touch emphasis is there, regardless of what anyone says, and it makes things difficult. For instance, Show desktop. This is an action slash widget in pretty much every other desktop, and despite occasional setbacks and regressions, it's always been there, a loyal companion in the moment of need. Not so in Gnome 3. Not just hidden. Not there at all. And what if you want it? Far from trivial. Hence this tutorial.
  • There's a script that makes the GNOME launcher a bit more organised
    I follow a great many sources for news and one that popped up in my feed is the 'gnome-dash-fix' script. It sorts out the mess that is the GNOME application launcher.

Leftovers: KDE and Qt

  • KDE neon CMake Package Validation
    In KDE neon‘s constant quest of raising the quality bar of KDE software and neon itself, I added a new tool to our set of quality assurance tools. CMake Package QA is meant to ensure that find_package() calls on CMake packages provided by config files (e.g. FooConfig.cmake files) do actually work.
  • Aether Icon Theme
  • Krita 2017 Survey Results
    A bit later than planned, but here are the 2017 Krita Survey results! We wanted to know a lot of things, like, what kind of hardware and screen resolution are most common, what drawing tablets were most common, and which ones gave most trouble. We had more than 1000 responses! Here’s a short summary, for the full report, head to Krita User Survey Report.
  • Cutelyst 1.6.0 released, to infinity and beyond!
    Once 1.5.0 was release I thought the next release would be a small one, it started with a bunch of bug fixes, Simon Wilper made a contribution to Utils::Sql, basically when things get out to production you find bugs, so there were tons of fixes to WSGI module.
  • LaKademy 2017 just started!
    The Latin America KDE Summit, LaKademy, just started today in Belo Horizonte, Minas Gerais, Brazil. The country is in the middle of a general strike, which I’m supporting, but the LaKademy couldn’t stop. We’ve been organizing this meeting for a year.
  • KDE Connect from the eyes of a newbie... What sorcery is this?
    Of course, I inferred it was something to connect a phone and a PC in some way and enabling the swapping of files in between the two devices, but I really did not care much about it. After all, that is what bluetooth is for, right? Today, I decided to give it a try on PCLOS.
  • 9 months of Atelier project, almost time to launch(or not) =D
  • Nextcloud Plugin for QuickShare
    So after a long hiatus I chose the Plasma QuickShare applet (which is sort of the Plasma5 replacement for the old Pastebin Plasmoid) as my point of re-entry into KDE code work. There was after all a deal of itches there I wanted scratched. It’s been quite a bit of fun figuring out the various interesting frameworks QuickShare is connected to at the backend. Anyways, some days ago I got a rudimentary Nextcloud plugin past review and pushed it, which should mean it’ll soon be coming to a 5.10-powered desktop near you :)
  • QNX as a desktop operating system
    On his spare time, Elad Lahav (a kernel developer at BlackBerry) built an experimental Qt-based desktop environment to try and see if he could use QNX as a desktop operating system. And it works!
  • Performance regression testing of Qt Quick
    We recently added a new toy to The Qt Project, and I wanted to give an overview on what it is and how it can be used.
  • Qt World Summit 2017 Call for Presentations
  • Give us a proper mimetype name for OpenCL C files!
    KDevelop, your cross-platform IDE, since version 5.1 has initial OpenCL language support.

Oh Snap – to boldly package where no one has packaged before

One of the great disadvantages of the Linux desktop is its software distribution mechanism. While the overall concept of central software repos works great and has been adapted into powerful Stores in commercial products, deploying and using programs, delivered as packages, is a tricky business. It stems from the wider fragmentation of the distro ecospace, and it essence, it means that if you want to release your product, you must compile it 150 odd ways, not just for different distributions but also for different versions of the same distribution. Naturally, this model scares away the big game. Recently though, there have been several attempts to make Linux packages more cross-distro and minimize the gap between distributions. The name of the game: Snap, and we’ve tasted this app-container framework before. It is unto Linux what, well, Windows stuff is unto Windows, in a way. Not quite statically compiled stuff, but definitely independent. I had it tested again in Ubuntu 17.04, and it would appear that Snap is getting more and more traction. Let’s have another look. Read more

Kubuntu 17.04 - the next generation

As usual, Kubuntu 17.04 does not give you any surprises. It is stable and reliable. It is reasonably resource-hungry. There are no wonders in this new release. Just a well-rounded distribution for everyday use. Yes, there are small bugs or inconveniences here and there, but they are not huge and can be easily fixed, replaced or lived with. The biggest of them for me, of course, is the lack of multimedia codecs. You can heal that easily. Read more