Hardware report for Lenovo Thinkpad X250, submitted via the site form.
A maintainer: copy the block below into a new file under data/reports/ (see CONTRIBUTING.md) to add it to the list.
device_model:"Lenovo Thinkpad X250"form_factor:laptopcpu:"Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz"1.8.10-alpharam_gb:16storage:type:ssdsize_gb:500wifi_chip:"Intel Wireless 7260"archy_version:"1.8.10-alpha"install_method:usb-isostatus:workingtested_date:"2026-09-03"
Hardware report for **Lenovo Thinkpad X250**, submitted via the site form.
A maintainer: copy the block below into a new file under `data/reports/` (see CONTRIBUTING.md) to add it to the list.
```yaml
device_model: "Lenovo Thinkpad X250"
form_factor: laptop
cpu: "Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz"1.8.10-alpha
ram_gb: 16
storage:
type: ssd
size_gb: 500
wifi_chip: "Intel Wireless 7260"
archy_version: "1.8.10-alpha"
install_method: usb-iso
status: working
tested_date: "2026-09-03"
```
Merged as data/reports/lenovo-thinkpad-x250.yml in d403b5e — thanks for the first real report!
One thing worth flagging: the submitted YAML had cpu and archy_version glued together with no line break (...2.60GHz"1.8.10-alpha). I tested the form's YAML-building code directly against these exact field values and it produces correct output, so this looks like something that happened during actual submission in the browser (Gitea draft-restore or autofill interacting with the pre-filled body) rather than a bug in the form. Reconstructed the two fields by hand since the correct values were unambiguous. Flagging in case it happens again on a future report — if so, worth noting what browser/steps led to it.
Merged as `data/reports/lenovo-thinkpad-x250.yml` in d403b5e — thanks for the first real report!
One thing worth flagging: the submitted YAML had `cpu` and `archy_version` glued together with no line break (`...2.60GHz"1.8.10-alpha`). I tested the form's YAML-building code directly against these exact field values and it produces correct output, so this looks like something that happened during actual submission in the browser (Gitea draft-restore or autofill interacting with the pre-filled body) rather than a bug in the form. Reconstructed the two fields by hand since the correct values were unambiguous. Flagging in case it happens again on a future report — if so, worth noting what browser/steps led to it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hardware report for Lenovo Thinkpad X250, submitted via the site form.
A maintainer: copy the block below into a new file under
data/reports/(see CONTRIBUTING.md) to add it to the list.Merged as
data/reports/lenovo-thinkpad-x250.ymlind403b5e— thanks for the first real report!One thing worth flagging: the submitted YAML had
cpuandarchy_versionglued together with no line break (...2.60GHz"1.8.10-alpha). I tested the form's YAML-building code directly against these exact field values and it produces correct output, so this looks like something that happened during actual submission in the browser (Gitea draft-restore or autofill interacting with the pre-filled body) rather than a bug in the form. Reconstructed the two fields by hand since the correct values were unambiguous. Flagging in case it happens again on a future report — if so, worth noting what browser/steps led to it.