Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 967
    • Issues 967
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11638
Closed
Open
Issue created Aug 15, 2016 by intrigeri@intrigeriMaintainer

Tell 32-bit users why Tails cannot start

Originally created by @intrigeri on #11638 (Redmine)

Once we have #8183 (closed), some computers won’t be able to start Tails anymore. We could use syslinux’ ifcpu64 module or similar to display a message explaining them what’s happening. This would decrease the load on our frontdesk, and be nicer to these users.

Feature Branch: feature/8183-64bit-userspace

Related issues

  • Related to #8183 (closed)
  • Blocks #12431 (closed)
  • Blocks #11997 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking