Dreambox Board

Andro1 · Nov 8th 2024

Hi,

There is an issue in the file Standby.py, located at /usr/lib/enigma2/python/Screens, related to an incorrect variable name assignment. Specifically, the code contains the following line:

Code

self.conntected=False

The correct variable name should be self.connected, but a typo has caused it to be incorrectly written as conntected (with an extra "t").

This results in the assignment of False to a non-existent attribute, which prevents the expected behavior of the program and can lead to potential runtime errors. The intended functionality appears to involve updating the connected state, which manages the connection to the event system, but due to the typo, this update does not occur as expected.

Impact:

The error prevents the proper removal from events in the TryQuitMainloop class.
This can lead to memory leaks or unexpected behavior, as events remain subscribed even though they should be removed.
It may cause issues in the system when performing shutdown or reboot operations.

To resolve this issue, the code should be updated as follows:

Code

self.connected = False

This change ensures that the correct connected attribute is being updated, allowing proper removal of events and restoring expected system behavior.

Best regards.

Fred Bogus Trumper · Nov 8th 2024

there will be no updates in the future anymore

this code can also be found in a "frozen" enigma2 dated on May 2019 - so if this is a bug, it's a very "old" one ..

Code

root@dm820:~# dpkg -l enigma2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                        Version                    Architecture               Description
+++-===========================================-==========================-==========================-============================================================================================
ii  enigma2                                     4.3.2r5-r0   mipsel                     Framebuffer-based digital media application
root@dm820:~#

Code

root@dm820:~# grep conntected $(find /usr/lib/enigma2/python/ -iname "*.py")
/usr/lib/enigma2/python/Screens/Standby.py:            self.conntected=False
/usr/lib/enigma2/python/Components/NimManager.py:        # remove nims, that have a conntectedTo reference on
root@dm820:~#

If this is not a feature but a bug with safety a quick 'n dirty adjustment executed in the terminal

Code

PY="/usr/lib/enigma2/python/Screens/Standby.py"
if grep "self.conntected=False" $PY & >/dev/null; then sed -i 's/self.conntected=False/self.connected = False/' $PY;fi
systemctl restart enigma2

Fred Bogus Trumper · Nov 9th 2024

I was informed that this bug was already fixed in OE2.6 AIO beta, but not in OE2.6 or OE2.5

alpha · Nov 9th 2024

what is the failure that is caused by this bug? i've used oe2.5 for 6 years now, and never experienced a problem during shutdown.

Andro1 · Nov 9th 2024

Quote from alpha

what is the failure that is caused by this bug? i've used oe2.5 for 6 years now, and never experienced a problem during shutdown.

The issue caused by self.conntected=False (which should be self.connected = False) might not be immediately noticeable to the user in all cases, but it could affect certain scenarios and become apparent in the following situations:

1. Attempting to Stop Recording or Close the Application

If there is an active recording or background process (e.g., a task in job_manager or a new recording process), the user may experience delays or unresponsiveness when trying to stop the recording or close the application.
If the code fails to correctly detach events due to the incorrect self.conntected variable, the application might continue waiting for a response or fail to act on commands like "shutdown" or "stop recording".

2. Closing the Standby Screen or Switching to Another State

When trying to close the Standby screen or switch to another state (e.g., resuming playback or returning from standby mode), if the connected state isn't properly updated, the application may remain in an inconsistent state or fail to respond properly to transitions (such as resuming the previous service or returning to the previous state).
The user may not immediately notice this, but if there is a service running when exiting Standby, or if the user tries to resume from Standby, things may not behave as expected.

3. Displaying Confirmation Messages for Shutdown or Reboot

If the code includes a confirmation message ("Really shutdown now?"), the user might notice a delay in the message appearing or unexpected behavior after responding to the message.
Due to the incorrect self.conntected variable, the message might not close as expected or might close incorrectly.

4. Tasks or Functions Dependent on the `connected` State

If there are other tasks or functions dependent on the event being correctly attached or detached, such as managing recordings or stopping background jobs, these may fail or not execute as expected.
The user might not notice an immediate impact, but these functions might not work correctly in the background, causing delays or incorrect behavior.

5. Memory Leaks or Incomplete Operations

If tasks are not properly canceled or connections are not detached due to the incorrect connected variable, it could lead to memory leaks or pending operations, which might degrade system performance or slow down the device over time.
The user might not notice the issue immediately, but over time, the system could slow down or become unresponsive due to these "orphaned" tasks.

Cepheus62 · Nov 9th 2024

Auch wenn wahrscheinlich kein fix in die alte OE geben wird, finde ich es sehr informativ, das einige User sich die mühe machen, solche "bug" zur finden und zur publizieren.

Auch an alle die ein "fix" publizieren.

Max11 · Jan 23rd 2025

I noticed that there is an issue with the samba file at the path /etc/init.d/samba for the DM520.

The file path is incorrectly written inside the file.

Code

if [ ! -d /usr/bin ]
then                    # /usr not mounted
        exit
fi

killproc() {            # kill the named process(es)
        pid=`/usr/bin/ps -e |
             /usr/bin/grep -w $1 |
             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
        [ "$pid" != "" ] && kill $pid
}

Display More

When trying to stop the service, I get the following result:

Code

root@dm520:
/etc/init.d/samba stop

/etc/init.d/samba: line 15: /usr/bin/ps: No such file or directory
/etc/init.d/samba: line 16: /usr/bin/grep: No such file or directory
/etc/init.d/samba: line 17: /usr/bin/sed: No such file or directory
root@dm520:

But it seems that this issue has been resolved in DM ONE and DM TWO (Unstable & AIO):

Code

if [ ! -d /bin ]
then                    # /usr not mounted
        exit
fi

killproc() {            # kill the named process(es)
        pid=`/bin/ps -e |
             /bin/grep -w $1 |
             /bin/sed -e 's/^  *//' -e 's/ .*//'`
        [ "$pid" != "" ] && kill $pid
}

Display More

xunil80 · Jan 23rd 2025

"ridiculous"

Code

 Copyright (c) Timo Knuutila <knuutila@cs.utu.fi>     1996.

Max11 · Jan 23rd 2025

It kept giving me error messages in /var/log/samba.

Since I don’t use it, I disabled it using the following commands:

Code

systemctl disable nmb
systemctl disable smb

Andro1 · Jan 24th 2025

No system is free from errors.

If you delve deeper into the system, you might discover some issues such as:

A problem in the file /usr/lib/tmpfiles.d/etc.conf at line 14.
A typo in "filescan_open" in the file /usr/lib/enigma2/python/Screens/DefaultWizard.py.
Other errors in DreamBLE, OpenGL ES, and eglGetDisplay.

Nothing is perfect.

xunil80 · Jan 25th 2025

Quote from Andro1

Nothing is perfect.

exactly ...

Max11 · Jan 26th 2025

I used commands to check whether the DM520 has any errors, and the results are as follows:

journalctl | grep -i "failed" >> /media/hdd/failed.log &

Code

Jan 01 02:00:15 dm520 kernel[145]: [    9.587000] VIDEO0 got pts failed !!!! (ret 0)
Jan 01 02:00:16 dm520 connmand.real[144]: Failed to open RFKILL control device
Jan 26 15:42:50 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/skin_default/spinner/wait10.png': No such file or directory
Jan 26 15:42:57 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/skin_default/icons/notification_mail.png': No such file or directory
Jan 26 15:43:07 dm520 enigma2[150]: gPixmap: Failed to access '': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_s-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_c-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_t-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_service_group-fs8.png': No such file or directory
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd1/mtdblock1/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/spi_brcmstb.0/spi_master/spi0/spi0.0/mtd/mtd3/mtdblock3/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd0/mtdblock0/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd2/mtdblock2/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop1/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop2/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop0/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop4/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop3/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop5/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop6/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/mtd/mtd4/mtdblock4/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop7/partition
Jan 26 15:51:57 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:20 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:24 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:40 dm520 enigma2[150]: getting program info failed.
Jan 26 15:53:42 dm520 enigma2[150]: getting program info failed.
Jan 26 15:54:19 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:54:20 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:55:57 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:55:58 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:59:07 dm520 systemd-tmpfiles[2076]: Failed to open directory /var/tmp: Too many levels of symbolic links

Display More

journalctl | grep -i "error" >> /media/hdd/error.log &

Code

Jan 26 15:42:49 dm520 enigma2[150]: EGL Error: 0 ((null))
Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetError not implemented!
Jan 26 15:51:57 dm520 kernel[145]: [  565.637000] audio ch0: pts error 0 PTS 0x78cf7e9e, STC 0x78cf600c, type 0
Jan 26 15:54:14 dm520 kernel[145]: [  692.228000] audio ch0: pts error 0 PTS 0x1c4a1776, STC 0x1c4a15c8, type 0
Jan 26 15:54:14 dm520 kernel[145]: [  692.440000] audio ch0: pts error 1 PTS 0xd89e995e, STC 0xd89e9502, type 0
Jan 26 15:54:15 dm520 kernel[145]: [  693.232000] audio ch0: reset pts error counter

journalctl | grep -i "warning" >> /media/hdd/warning.log &

Code

Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetDisplay not implemented!
Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetError not implemented!
Jan 26 15:43:08 dm520 enigma2[150]: WARNING! ConfigEnableDisable is deprecated, please use ConfigOnOff instead!
Jan 26 15:43:11 dm520 enigma2[150]: warning, skin is missing element RassLogo in <class 'Screens.RdsDisplay.RdsInfoDisplay'>
Jan 26 15:43:11 dm520 enigma2[150]: warning, skin is missing element state in <class 'Screens.PVRState.TimeshiftState'>
Jan 26 15:43:13 dm520 enigma2[150]: warning, skin is missing renderer <Components.Renderer.extvolumeText.extvolumeText object at 0x6afd1cb0> in <class 'Screens.Volume.Volume'>
Jan 26 15:52:51 dm520 enigma2[150]: libpng warning: iCCP: known incorrect sRGB profile
Jan 26 15:54:05 dm520 enigma2[150]: libpng warning: iCCP: known incorrect sRGB profile

dre · Jan 26th 2025

And about 50 percent of what you claim to be errors are missing files of your skin

Max11 · Jan 26th 2025

This is not my problem, it's an issue with the image and the default skin.

The developer added 9 "wait" files to the spinner folder, and now the system is telling me that the file wait10.png is missing. How can I get it?!

The developer did not add the file notification_mail.png. How can I get it?!

The developer did not add the files (ico_dvb_s-fs8, ico_dvb_c-fs8, ico_dvb_t-fs8, ico_service_group-fs8). How can I get them?!

The developer did not add RassLogo and state. How can I get them?!

This is the developer's issue; they defined the files but didn't add them.

Recently, I installed the Zombi-Shadow-FHD skin, and the system is telling me that the extvolumeText render is missing, but when I searched inside the skin, I found it in its correct place! How could this happen?!

The problems are related to the mistakes of the previous developers who are now gone, leaving us with these annoying issues.

dhwz · Jan 27th 2025

Max11

The only problem I see is that you've no clue what these warnings/errors mean.

Besides that everything is fine.

dre · Jan 27th 2025

Quote from Max11

The developer added 9 "wait" files to the spinner folder, and now the system is telling me that the file wait10.png is missing. How can I get it?!
The developer did not add the file notification_mail.png. How can I get it?!
The developer did not add the files (ico_dvb_s-fs8, ico_dvb_c-fs8, ico_dvb_t-fs8, ico_service_group-fs8). How can I get them?!
The developer did not add RassLogo and state. How can I get them?!

Generate them yourself? If warnings that do have zero impact on any functionality of your dreambox are an issue for you, then it's a simple two liner (and one import) to get rid of most of them. E.g. the icons for reception type have been added that skinners who would like to show them in channellist can do that easily but they have never been included by default.

Quote from Max11

Jan 26 15:43:08 dm520 enigma2[150]: WARNING! ConfigEnableDisable is deprecated, please use ConfigOnOff instead!

This is a warning that is very helpful and tells devs that they should no longer use ConfigEnableDisable. This is not a but but a very important information.

Max11 · Jan 27th 2025

Quote from dre

Generate them yourself? If warnings that do have zero impact on any functionality of your dreambox are an issue for you, then it's a simple two liner (and one import) to get rid of most of them. E.g. the icons for reception type have been added that skinners who would like to show them in channellist can do that easily but they have never been included by default.

This is a warning that is very helpful and tells devs that they should no longer use ConfigEnableDisable. This is not a but but a very important information.

Well, regarding the messages about the missing UI files, they can be added easily. However, what I meant is that as long as these files are defined in the system, they should be included with the image. Or if the developer doesn’t want to add them, they could be referenced as an informational message or a warning, not as a failed message as if they are critical and required by the system!

As for other messages like 'VIDEO0 got pts failed,' 'RFKILL,' 'Harddisk.py,' 'eStaticServiceDVBBouquetInformation,' 'eglGetError,' 'eglGetDisplay,' etc., are they related to issues with the drivers, kernel, or something else?

alpha · Jan 27th 2025

der schwabe wuerde sagen: "die katz is de bom nuff"

dhwz · Jan 27th 2025

Why are you bothering about anything in the journal, actually nothing in there is relevant to a user.

Max11 · Jan 27th 2025

dhwz
Your responses do not help me understand the results I got.

You're suggesting that I have a problem understanding the meaning of these warnings or errors, and that my interest in understanding the reasons behind these results isn't important to me as a user!!

Could you please explain how you arrived at these conclusions?!

If you could help me understand the reasons behind these results and possible solutions, it would be incredibly helpful.

If your focus is on assessing my understanding or the reason for my interest, it might be more helpful to refrain from further comments on that.

1. Attempting to Stop Recording or Close the Application

2. Closing the Standby Screen or Switching to Another State

3. Displaying Confirmation Messages for Shutdown or Reboot

4. Tasks or Functions Dependent on the connected State

5. Memory Leaks or Incomplete Operations

4. Tasks or Functions Dependent on the `connected` State