Creating a bug report/issue
Required Information
- DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=11
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘not applicable’ - Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bullseye - Kernel version |
uname -a
Linux Downloader 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux - SBC model |
echo $G_HW_MODEL_NAME
or (EG: RPi3)
Native PC (x86_64) - Power supply used | (EG: 5V 1A RAVpower)
PC Power cord. - SD card used | (EG: SanDisk ultra)
Samsung SSD
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
Transmission - Was the software title installed freshly or updated/migrated?
Installed freshly - Can this issue be replicated on a fresh installation of DietPi?
I would think not, (haven’t tried)
← If you sent a “dietpi-bugreport”, please paste the ID here → - Bug report ID |
echo $G_HW_UUID
Steps to reproduce
- Installed transmission using the diet-pi software
- Left it to run over night
Expected behaviour
- It shouldn’t crash out.
Actual behaviour
- transmission will crash out and dead itself, and I’m unsure why
https://i.postimg.cc/PqwcxkP7/2022-12-17-22-31-49.png
Extra details
- Everything was working fine, but I wanted to format Dietpi and do a fresh-install, everything went fair no issues. But later on that day I noticed I couldn’t access transmission via the URL and checking SSH shows the service is killed, this is now the 3rd time it has happend. Not sure what’s going on here?