GNOME Asia Summit 2026

31 Oct 2026, 08:50 → 2 Nov 2026, 17:00 Asia/Kuala_Lumpur

Terengganu Digital 1303

Kristi Progri, Muhd Syazwan Md Khusaini

GNOME.Asia Summit is the featured annual GNOME conference in Asia. It focuses primarily on the GNOME desktop but also covers applications and platform development tools. The summit brings together the GNOME community in Asia to provide a forum for users, developers, foundation leaders, governments, and businesses to discuss the present technology and future developments.

---

Event Agenda:-

31st October & 1st November : Talk's Day

2nd November : Day Trip / Social Event

---

About GNOME

GNOME is a free and open-source software environment project supported by a non-profit foundation. Together, the community of contributors and the Foundation create a computing platform and software ecosystem, composed entirely of free software, that is designed to be elegant, efficient, and easy to use.

---

 

Saturday 31 October

09:10 Registration

09:55 Opening Remarks

1 From "Gotong Royong" to Open Source: Empirical Insights on How FOSS Reshaped the Indonesian Contributor Mindset

Open source software in Indonesia is often evaluated through code contributions and infrastructure adoption. However, its most transformative impact lies in human cognition and cultural behavior. This session presents original empirical research gathered from 22 Indonesian FOSS contributors—spanning veteran sysadmins, software engineers, non-tech professionals, and community educators—exploring how open source shapes daily thinking outside of technology.

Quantitative findings reveal that FOSS engagement fundamentally alters decision-making: 90.9% of respondents report prioritizing transparent evidence over institutional authority, while 77.3% adopt a strong DIY ownership mindset over vendor lock-in.

Furthermore, qualitative analysis reveals a fascinating cultural alignment: Indonesian contributors perceive FOSS not as a foreign tech framework, but as a digital evolution of Gotong Royong (traditional mutual assistance). By highlighting real-world stories—from collaborative bug-fixing over blame culture to open knowledge sharing—this talk demonstrates how open source serves as a socio-cultural engine in Southeast Asia, turning passive software users into active, community-first thinkers.

Speaker: Siska Iskandar (GNOME Indonesia)

How Open Source Community Shaped The Way We Think (Responses) - Form Responses 1.csv

iskandar.jpg

2 Community Building Without a Blueprint: What Worked (and What Didn't) for GNOME Nepal

GNOME Nepal grew to a community of ~400 members without an established GNOME chapter or a local roadmap to follow. Building from that position meant experimenting constantly: reaching students, introducing people to GNOME and open source, creating opportunities for newcomers to participate, and learning which approaches actually sustained engagement.

This talk is an honest account of that process — including the experiments that worked, those that failed, and the assumptions we had to change along the way. Rather than presenting community building as a repeatable formula, it shares practical lessons from building GNOME in an emerging ecosystem and what we would approach differently today.

Speakers: Sailesh Singh (GNOME Nepal), Shraddha Tiwari (Gnome Nepal)

3 Improving the New User Experience in GNOME

GNOME provides a clean, modern, and user-friendly desktop environment for Linux. However, users who are new to Linux can still experience difficulties when performing common tasks or trying to understand system problems.

This talk explores the GNOME desktop from the perspective of a new Linux user. It focuses on common situations such as connecting to Wi-Fi, using Bluetooth devices, accessing external storage, installing applications, changing system settings, and understanding error messages.

The main idea is that a user interface should not only report that something went wrong, but should also help the user understand what happened and what they can do next.

Speaker: Aashish Kumar Sah (Worldlink Communication)

sah.jpeg

11:05 Coffee Break

4 Isolating tools in the age of agentic development

It is becoming really common for users and developers to have to download and install tools directly from the network and just run them on their systems. To some extent this has always been the case, and there is a degree of trust implied when downloading binaries, particularly now with the all too common "curl-to-shell" installs.

This talk presents a few CLI tools providing simple basic isolated environments: primarily using Linux containers. In particular the author's experiments with his encapsule project will be described and shown, built on top of Podman. It is a restricted Toolbox-like environment that provides a simple way to only expose specific files and system access to such a downloaded tool, which is something he had wanted for quite some time.

Speaker: Jens Petersen (Red Hat)

juhp.jpg

12:10 Break

5 Digital Government in Nepal: Opportunities for Free and Open-Source Software

Digital government is usually discussed in terms of platforms and policy, but citizens experience it at ground level — often at the ward office. I speak from that vantage point: a Ward Secretary with 2.5 years handling the systems citizens actually touch, like VERSP-MIS (for vital event registration), SuTRA (for revenue collection), and CCIMS (for online recommendation of citizenship).
These tools work, but only as well as the conditions around them allow. Server downtime, patchy internet, unscheduled power cuts, low digital literacy, and rural-urban infrastructure gap (digital divide within Nepal) all shape whether "digital government" delivers. Demand spikes (like annual social security renewals) and recent disaster-hit districts like Rasuwa and Nuwakot show how fragile that promise can be.
I'll explore where Free and Open-Source Software might genuinely help — and where it can't, without infrastructure, people, and funding behind it.

Speaker: Rajesh Pudasaini (Admin Asst - Provincial government/ local government of Nepal)

IMG_20260908_210656.jpg

6 Open Source Agentic AI Needs Community: How We Build It Together

Open source agentic AI is growing fast with projects like Hermes Agent and OpenClaw, but technology alone is not enough. Drawing on experience organising Hong Kong Open Source Conference 2026’s agentic AI track and daily use of Hermes Agent, this talk shows why community and ecosystem building matter, and offers practical ways GNOME and Asian F/OSS communities can shape open, sustainable agentic AI together.

Speaker: Sammy Fung

fung.jpg

12:50 Lunch Break

7 Bus Factor: Mapping Single Points of Failure in GNOME's Maintainer Network

Every open source project relies on a few people who know how things really work. When too much knowledge is concentrated in just one or two people, it can become a real risk for the project.

In this talk, I’ll look at how we can use data engineering to better understand that risk. I’ll use public GitLab data from GNOME modules, looking at things like who is contributing code, reviewing changes, and helping with merges over time.

I’ll walk through a simple, fully open-source pipeline that collects and processes this data and turns it into a dashboard. The idea is to get a clearer picture of which modules have a healthy spread of contributors and which ones may depend heavily on a small number of people.

This isn’t about ranking or calling out individual contributors. Instead, the goal is to give maintainers and the GNOME Foundation a practical way to spot areas where additional maintainers, mentoring, or knowledge sharing might be useful.

By the end of the talk, attendees will have a reference architecture they can adapt for their own open source projects, along with some practical lessons on working with community data and focusing on useful metrics rather than numbers that simply look good.

Speaker: Prasis Angdembe

8 Virtual Machines Made Simple with Boxes

Learn how to work with virtual machines in GNOME. Creating virtual machines from various operating systems and sharing resources between your system and the virtual machine.

Speaker: Felipe Borges (Red Hat)

Borges.png

9 You Don't Need Big Tech to Build Big Things

My journey into open source and homelab started from a simple idea: learn by building, not just by consuming technology.

I started with Linux and gradually discovered the world of open source. Debian became one of the foundations of my learning journey. From there, I explored servers, networking, virtualization, containers, automation, web development, and self-hosted services.

My homelab became a place to experiment. I learned to run services myself, break things, fix them, document what happened, and try again. Instead of depending entirely on expensive infrastructure, I learned how much can be achieved with ordinary hardware, free software, and a willingness to learn.

Along the way, I worked with technologies such as Linux, Incus, Docker, Laravel, Go, Nginx, Tailscale, Cloudflare, databases, and self-hosted applications. Each project taught me something different—not only about technology, but also about reliability, security, backups, documentation, and responsible system design.

Open source taught me that you don't always need the latest hardware or a huge budget to build useful things.

A small computer can become a server.
A spare machine can become a laboratory.
Open-source software can become an entire platform.
And a curious mind can turn all of them into something much bigger.

My homelab is not a replacement for big technology companies. It is my learning ground—a place where I can understand how things actually work instead of simply clicking a button and accepting the result.

The journey is still going.

I'm still learning, still breaking things, still rebuilding, and still discovering better ways to do things.

You don't need big tech to build big things. Sometimes, you just need a small lab, open-source software, and the courage to start.

Speaker: Hardy N Jafar

14:35 Coffee Break

10 Creating a GTK4/Libadwaita/Flatpak App From Scratch!

Building native applications for the GNOME ecosystem has never been easier, yet starting from a blank editor can be intimidating. This talk guides attendees step-by-step through the process of building a modern GNOME application from the ground up using GTK4, Libadwaita, and Flatpak.

Speaker: Felipe Borges (Red Hat)

Borges.png

11 GNOME and its Accessibility features

It's an a11y awareness campaign and shows that GNOME already has it. Accessibility isn't an extra feature you need to install on GNOME. It is already part of the desktop. GNOME provides built-in a11y features designed to support different ways people interact with their computers, including screen reading, magnification, visual adjustments, and alternative ways to use the keyboard and pointer. In this session, I’ll take a quick look at where these features live, how to activate them, and most importantly, experience how they actually work in everyday use.

Speaker: Yudhi Satrio

IMG_6371.JPG

12 From GSoC Rejection to GNOME Contributor: A Year of Showing Up

In early 2026, I applied for Google Summer of Code with the GNOME Foundation - and I didn't get selected. For many students, that rejection is the end of the story. They close the laptop, move on, and never contribute to open source again.

I chose a different path. Instead of waiting for a program to give me permission to contribute, I opened GNOME's GitLab, found a project that needed help - Gitg, the official GNOME Git repository browser - and started submitting merge requests on my own.

That was almost a year ago. Since then, I have:
- Driven the GTK3 to GTK4 migration for Gitg through dozens of focused micro-commits
- Got the chance to represent the GNOME Foundation at OOSC 4.0 in IIITA, India, organized by OpenPrinting and The Linux Foundation.
- Modernized over 40 UI components, replacing deprecated event handlers, container packing methods, and display APIs
- Learned Vala from scratch - a language I had never written a single line of before
- Built a genuine working relationship with the project maintainer
- Been selected as a Linux Foundation LiFT Scholar for my open-source work

This talk is not a technical deep-dive into GTK4 APIs. It is an honest, practical story about what happens when you refuse to let a rejection define your open-source journey.

What the Audience Will Learn:
- Why GSoC rejection doesn't matter - and why self-directed contribution is often more valuable
- How to find your first GNOME project — navigating GitLab, reading issue trackers, and identifying where help is needed
- The micro-commit strategy - why mass rewrites fail and small, 10-line merge requests succeed
- Building trust with maintainers - how to go from "random outsider" to "trusted contributor" through consistency and patience
- Sustaining motivation for a full year - how to keep contributing when there's no stipend, no deadline, and no one telling you what to do

Speaker: Divyanshu Rajput (OSS Contributor @GNOME)

13 From Reviving a Distro to Building an Open Source Movement: Lessons from GNOME

BlankOn Linux, one of Indonesia’s long-running Linux distributions, reached a point where its sustainability was uncertain. Before attempting to revive the project, I asked a broader question: what makes an open source project sustainable beyond the enthusiasm of its contributors?

Looking at successful open source organizations, I found that technology and contributors were only part of the answer. The GNOME Foundation offered an especially valuable example of how an open source ecosystem can be supported through sustainable funding, transparent stewardship, community governance, effective use of resources, and clear enforcement of community standards such as the Code of Conduct.

These lessons became the foundation for establishing a new organization to support Indonesia's open source movement. Rather than focusing solely on reviving BlankOn, we built an institution designed to support the wider ecosystem and open source national movement: providing legal assistance, funding, sponsorship, community support, infrastructure, and organizational help to open source initiatives and communities.

The results came faster than expected. The foundation is already supporting six external initiatives, with more expected to join in the coming year. At the same time, the work to revive and modernize local Linux distributions has gained significant momentum.

This talk shares what I learned from studying the GNOME Foundation, what we adapted for the Indonesian context, what worked, what did not, and how institutional sustainability can turn a struggling open source project into a platform for supporting an entire community.

Ultimately, this is a story about moving from “How do we save our project?” to “How do we build an ecosystem where projects can survive?”

Learn more about BlankOn Foundation here: https://blankon.id/en

Speaker: Herpiko Dwi Aguno (BlankOn Foundation)

herpiko-v2.png

Sunday 1 November

14 Does GNOME Speak Your Language? Screen Reader Support Beyond English.

GNOME's accessibility support is genuinely good — Orca has been around since 2006 and it's one of the more mature screen readers in the FLOSS world. But "mature" mostly means mature for English. I wanted to find out what happens when you try to use it in a language that almost nobody has tested it in.
I picked Nepali, my own language, spoken by over 30 million people, and started digging. I went through the whole pipeline that makes Orca talk — speaking pronunciation rules, speech-dispatcher, and Orca's own text handling — to see where things actually break. Some of it was what I expected. Some of it wasn't.
I also talked to Nepali-speaking screen reader users directly — because for someone who relies on Orca every day to read email, do schoolwork, or apply for a job, a mispronounced word isn't a minor bug, it's a barrier.
In this talk I'll walk through what I found, [what I ended up fixing/filing upstream], and what the process of contributing to a project like Orca actually looks like for someone doing it for the first time. My hope is that this isn't just a talk about Nepali — it's a nudge for anyone in the room whose language GNOME hasn't gotten to yet.

Speaker: Abhishek Kushwaha

kushwaha.jpeg

15 Operationalizing GNOME Ambassadorship: Lessons from Bootstrapping Communities in Africa and Asia

After introducing the GNOME Ambassador concept at GUADEC 2026, we formed a small dedicated team to turn high-level community advocacy into real-world, actionable local chapters. This session shares practical lessons, wins, and friction points from bootstrapping open-source communities across two continents: Africa and Asia.

We will explore our real-world case studies, from the early momentum built by GNOME Nepal to cross-border efforts in reviving GNOME Africa, initiating GNOME Nigeria, and running an onboarding session for GNOME Kenya that welcomed nearly 30 new attendees.

Beyond initial local recruitment, a key focus of this talk will be upstream integration: how to bridge local grassroots initiatives directly into the main GNOME project ecosystem. We will cover methods for transitioning local event attendees into active global contributors, integrating regional teams into GNOME’s translation (l10n), engagement, and development workflows, and establishing sustainable pathways toward GNOME project contributions.

Speaker: Aaditya Singh (GNOME)

aaditya-profile.jpg

16 Who Owns the Code That Runs Justice? A Legal Case for Free and Open-Source Software in Public Institutions

Free and open-source software is usually framed as a technical choice an alternative stack, a cheaper license, a community of contributors. This talk argues it should also be understood as a matter of public institutional governance, using the judiciary as the sharpest possible test case.
Courts across Asia are adopting case management systems, e-filing platforms, and digital record systems, but almost none of this software is released under open licenses, and almost no public institution asks the questions the FOSS community asks by default: Who can read this code? Who can audit it? Who can fork it if the vendor disappears? Who owns the modifications built with public money?
Drawing on Nepal's judiciary as a case study, I'll show how the absence of open licensing, public source availability, and community-style governance around judicial software creates real risks-vendor lock-in, unauditable systems handling sensitive personal data, and institutions with no legal or technical path to independence from a single contractor.
I'll then turn to what FOSS communities- GNOME chief among them- already do well: transparent governance, copyleft and permissive licensing models, accessibility-first development, and contributor ecosystems that outlive any single vendor. I'll propose a legal framework, grounded in copyright, procurement, and data protection law, for how public institutions can responsibly adopt FOSS licensing and governance norms- not as ideology, but as a safeguard for democratic accountability.

Speaker: Shrinkhala Tiwari (Nepal Bar Council)

Tiwari.png

11:05 Coffee Break

17 Beyond Funding: How Meaningful Sponsorships Build Sustainable Open Source Communities

Open-source communities are powered by people, ideas, and collaboration. However, organizing sustainable community events also requires resources, partnerships, and meaningful support.

Through my experience working in different events and communities, including serving as a Sponsorship Lead for UbuCon Asia, I have learned that sponsorship is more than simply asking companies for financial support. Successful sponsorships are built through relationships, shared value, trust, and a clear understanding of how businesses and communities can support each other's goals.

In this talk, I will share practical insights and lessons from my experience in community events and sponsorship management. I will discuss how organizers can identify potential partners, communicate the value of supporting open-source communities, create meaningful sponsorship opportunities, and build relationships that can continue beyond a single event.

The session will also explore the challenges involved in sponsorship, including approaching potential partners, handling rejection, understanding sponsor expectations, and balancing commercial interests with the values and goals of a community.

This talk is intended for community organizers, event volunteers, new contributors, and anyone interested in helping open-source communities build stronger and more sustainable partnerships.

Speaker: Rabina Karki (Gnome Nepal / Periwinkle Services)

karki.PNG

18 Why Your Linux Desktop Doesn’t Need sudo as Much as You Think.

sudo is one of the most familiar commands in the Linux world. For many desktop users, however, it has quietly become the default solution whenever something doesn't work: installing software, managing services, changing configuration, or fixing permissions.

This talk takes a practical look at Linux's user and privilege model and asks a simple question: does this operation actually need root?

We will explore how Linux desktops already provide mechanisms that allow users and applications to accomplish many tasks without elevated privileges, including user-owned configuration, systemd --user, D-Bus, polkit, Flatpak, virtual environments, and rootless containers. Through practical examples, we will look at common situations where users reach for sudo unnecessarily, what can go wrong when they do, and how to approach permissions more deliberately.

The goal isn't to argue that sudo is bad or that users should never become root. Instead, the talk aims to build a better mental model of Linux permissions: use your normal user account by default, elevate privileges when the operation genuinely requires them, and understand what that elevation actually means.

The session will be accessible to Linux desktop users and developers, while still providing enough technical detail to explain what is happening underneath the commands we use every day.

Speaker: Aaditya Yadav (GNOME Nepal)

Yadav.jpeg

11:50 Break

19 Root-Level Digital Freedom: Introducing K-12 Linux Fundamentals and Localized GNOME in Schools

True open-source independence requires shifting technical literacy from late-undergraduate computer science down to primary and lower secondary school fundamentals. This presentation details our complete operational and educational framework for transforming K-12 computer science using a localized GNOME and Ubuntu ecosystem, driven by university student-led community outreach.

Key initiatives covered in this session:

• The K-12 Paradigm Shift: Replacing proprietary, skill-locked software curricula with Linux fundamentals, terminal basics, and GNOME Shell navigation for primary and lower secondary students.
• Localization at the Grassroots: Establishing native-language documentation and localizing GNOME UI components to eliminate language barriers for young learners.
• College-Led Outreach: Conducting university sessions on open-source freedom to build momentum, train student mentors, and onboard school educators.
• System Deployment: Securing school computer lab environments using dconf lock-downs and customized Ubuntu desktop profiles for low-resource hardware.

Speaker: Sailesh Singh (GNOME Nepal)

SaileshSingh.jpg

12:30 Lunch Break

20 AI Overload in GNOME: When Faster Coding Leads to Worse Pull Requests

In under two years, AI coding assistants went from a productivity promise to a maintainer's headache inside GNOME itself. In December 2025, the GNOME Extensions team banned AI-generated submissions outright after reviewer Javad Rahmatzadeh reported spending hours a day wading through 15,000+ lines of AI-produced code riddled with unnecessary try-catch blocks, invented APIs, and comments written for an LLM's benefit rather than a human's. By July 2026, GNOME's security team went further, collapsing its 90-day disclosure window to 30 days specifically because AI-generated vulnerability reports had become the norm rather than the exception, and by August, reviewers were reduced to writing instructions aimed directly at the bots generating the noise.
This talk uses GNOME's own paper trail as a case study for a pattern now documented across open source: AI lowers the cost of producing a contribution while leaving the cost of evaluating one untouched, and that imbalance is quietly reshaping maintainer labor. The broader evidence backs this up. A controlled study of experienced open-source developers found they were actually 19% slower when using AI tools, despite believing the opposite. Multiple studies have found that AI-generated code carries measurably more code smells, defects, and complexity than human-written code, alongside recurring security weaknesses. And even after a contribution merges, the maintenance burden doesn't disappear: one empirical study found that 83% of the follow-up work on AI-generated files still falls on human maintainers, not the agents that wrote them.
The talk closes with practical takeaways for maintainers: what a defensible AI-contribution policy looks like, where automated triage genuinely helps versus where it just adds a layer of bureaucracy, and how to protect reviewer time without shutting the door on genuine new contributors.

Speaker: Shraddha Tiwari (Gnome Nepal)

tiwari.jpg

21 Tying Up Loose Threads: Making your Project No-GIL Ready

Python's Global Interpreter Lock, which determines which single thread can execute native Python code and call C API functions, simplifies writing multithreaded code. However, sticking with this execution model leaves out extra performance afforded by modern multicore CPUs with hyperthreading, as automatic locking and unlocking of the GIL does not scale well with thread counts, especially in performance-sensitive workloads.

The newfangled free-threaded interpreter promises salvation when running either pure Python code or with compiled extensions. General multithreading rules apply (prefer thread-local variables, using locks to prevent simultaneous access of shared data), but when dealing with projects containing compiled extensions that directly or indirectly interface with Python's C API, more porting rules also apply.

Key porting tips, including projects using the Limited API, include: modify unit tests to catch concurrency bugs arising from assuming the presence of the GIL; and extend CI coverage of Python interpreters both for testing and to build free-threaded compatible wheels.

Speaker: Charlie Lin

lin.jpg

22 Beyond Pinyin: Designing Chinese Input Methods for GNOME — Lessons from libcangjie

Chinese input is often treated as a single localisation problem, but users across Mainland China, Taiwan, Hong Kong, Macau, and other Chinese-speaking communities rely on very different writing systems, phonetic conventions, input methods, and long-established typing habits.

At GNOME.Asia 2012 in Hong Kong, I presented some of these challenges in Cantonese. Fourteen years later, this English talk revisits the subject and asks what has changed — and what we have learned — about Chinese input on the Linux desktop.

I am the original author of libcangjie. The current Project Cangjie library was later built upon that original work and today provides the Cangjie and Quick input logic used by ibus-cangjie.

Using Cangjie and Quick as a case study, I will explain why Chinese input is not one problem; how phonetic, shape-based, and stroke-based input methods differ; and why details such as candidate ordering, filtering, regional character sets, and user expectations can make or break the input experience.

Finally, I will look at how Chinese input has evolved since 2012 and discuss what GNOME and the wider FOSS community can learn from it. Localisation is not simply translation: input methods sit at the intersection of language, culture, muscle memory, interface design, and software architecture.

Speaker: Wan Leung Wong (Hong Kong Linux User Group)

wong.png

15:10 Coffee Break

23 Growing GNOME in a Vacuum: Community Building in Low-Resource Regions

This paper tells the story of GNOME Nepal: how it grew from a two-person effort into a 15-strong core team, hundreds of members, without funding, institutional backing, or existing open source literacy to build on. In a country where most university curriculum have never mentioned GNOME, and open source itself remains poorly understood, growing a community is not a technical challenge, it's a cultural one.
I speak from personal experience, starting as a non-technical contributor with zero exposure to open source, and gradually becoming an active technical contributor, GNOME advocate, and core team member. That journey shaped how we designed our community-building approach: workshops that spark curiosity instead of overwhelming beginners with a full software walkthrough on day one; deliberate collaboration with Fedora and Ubuntu community groups in Nepal to jointly generate interest rather than compete for a small pool of newcomers; and a repeatable growth cycle of awareness, hands-on sessions, and mentorship.
I talk candidly about what didn't work, the constant risk of demotivation, the difficulty of retaining contributors after their first event, and the slow work of turning short-term curiosity into long-term contribution through small, consistent incentives. I also cover how addressing diversity, language barriers, and localization directly improved contributor communication and retention, and how mentorship turned early participants into the leaders now running the community.
This talk is for organizers in similarly under-resourced, low-open-source-literacy regions trying to build community from nothing, not from an existing base of technical contributors.

Speaker: Shraddha Tiwari (Gnome Nepal)

tiwari.jpg

24 Living with Windows: Key Differences from a Linux User's Perspective

1. How Linux and Windows differ as desktop environments
2. Linux as Lego bricks; Windows as a finished product.
3. Proprietary Windows applications that Linux users sometimes have no
   choice but to use.
4. Windows as an accessible environment for less technical users; Linux for
   professional work.
5. macOS as a middle ground between the two.
6. How deeply can Windows internals actually be investigated?
7. The challenge of investigating a proprietary operating system.
8. Linux users are not Windows kernel or core system developers.

9. With AI's help, investigating and finding practical answers.

10. Windows tools Masafumi built as a Linux user

11. Controlling application startup order as far as possible with Task
    Scheduler.
12. Stopping unwanted applications from launching at startup.
13. Shutting Windows down when the normal shutdown action does not work.
14. Terminating child applications when their parent application exits.
15. Crash dump analysis, with AI offering an interpretation.
16. Temperature and system load monitoring, with AI offering an assessment.

17. An SBOM checking tool.

18. Major differences in system behavior

19. svchost: the monster that eats your system.
20. Why startup order cannot be fully controlled.
21. Why sudden crashes such as Blue Screens of Death (BSODs) are so hard to diagnose.

22. How Linux kernel panics and Windows BSODs differ.

23. Conclusion

24. What can Linux users do when they have no choice but to use Windows?

Speaker: Masafumi Ohta (Japanese Raspberry Pi Users Group)

masafumi.jpg

16:00 Lightning Talks

16:40 Closing