Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

No display and getting padded area too small warning

Abierto
  • ¿Algo no está bien?
#174 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
embedded-iot

Línea de trabajo

Start with the step-by-step installation guide and the [main], default fallback plugin, and Basic Clock configuration shown in the issue. Trace where the :padding warning is produced and how the configured display and plugin layout are used; the payload does not identify source files or tests. Done means the cause of the missing display is identified and the display shows plugin output on the reported setup.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Describe the bug
Not getting any display. getting the warning:

This is the error I got last install

15:19:21 Block :padding :340 :WARNING - the padded area available may be too small to display any content: Area: (360, 24), Padded Area: [340, 4]
15:19:53 Block :padding :340 :WARNING - the padded area available may be too small to display any content: Area: (216, 24), Padded Area: [196, 4]
15:19:57 Block :padding :340 :WARNING - the padded area available may be too small to display any content: Area: (144, 24), Padded Area: [124, 4]

Getting this same warning after fresh install and going through the step by step install again still no display output..
07:10:36 Block   :padding   :340 :WARNING    - the padded area available may be too small to display any content: Area: (360, 24), Padded Area: [340, 4]

To Reproduce
I don't know how to reproduce as I have tried again from a fresh install and just followed the step by step install guide.

Expected behavior
Screen to display plugins as they should.

Hardware

  • Full EPD version: epd3in52
  • Pi Version Raspberry Pi 3 Model B Rev 1.2

OS Info

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

[main] Section of Config

# CONFIG_VERSION=1.2
[main]
# waveshare display type use HD for IT8951 displays
display_type = epd3in52
# required vcom value for IT8951 screens
vcom = 0.0
# maximum refresh between total screen clear for HD displays
max_refresh = 4
# logging output level
log_level = WARNING
# display splash screen (True or False)
splash = True
# rotation of EPD display
# (cable bottom: 0; cable left: -90; cable right: 90; cable top: 180)
rotation = 0
# mirror screen outuput - useful if output to screen appears backwards
mirror = False
# Disable RGB color support for 7-color screens (Default: True)
# This setting only affects 7 color screens and does not impact bi-color screens
color = false
# Disable screen wipe at shutdown (Default: True)
# This setting will leave the last image on the screen at shutdown
no_wipe = False
# plugin timeout - amount of time in seconds to wait for a hung plugin to complete execution
plugin_timeout = 30

Plugin Issues
The these are the only two plugins enabled

[Plugin: default fallback plugin]
layout = layout
plugin = default
refresh_rate = 30
min_display_time = 60
max_priority = 2**15

[Plugin: Basic Clock]
layout = layout
plugin = basic_clock
refresh_rate = 30
min_display_time = 50
max_priority = 2

Additional context
Initially I was trying the weather plugin but to troubleshoot I switched to the basic clock one since its simpler to see if maybe the other plugin had too much and the screen was not able to display it properly. Display does work fine as I have tested it using the waveshare demos.

Lenguaje dominante
Python
Estrellas
205
Forks
17
Merge medio
5 h 42 min
PR fusionados (30 d)
50

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de txoof/PaperPi

Todos los issues de txoof/PaperPi

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.