[SOLVED] Openbox _ What is a "libpng error"?

[rockland]

Installed latest Openbox distro. Laptop freezes and cycles through this error (libpng error) message every time I shutdown. Only way stop the flickering screen and error cycling is a hard reset. Had same problem with PCLinuxOS KDE flavour.

What is the command to find out what is "under the hood" of my laptop and kernel version? to assist in finding this solution.

How do I "acpi=force" ? Read this on the Forum. Is that the issue?

Best

[djohnston]

Installed latest Openbox distro. Laptop freezes and cycles through this error (libpng error) message every time I shutdown. Only way stop the flickering screen and error cycling is a hard reset. Had same problem with PCLinuxOS KDE flavour.

"No, the 'libpng read error' message is not important. It does it on all, it's when Plymouth finishes to display the boot image. We never quite understood how this message appeared and what triggers it, but we all have been living with it for more than one year now. You can neglect it."

In addition, you should not be doing any hard resets. Doing so may eventually cause filesystem corruption. What video card are you using?

What is the command to find out what is "under the hood" of my laptop and kernel version? to assist in finding this solution.

In a terminal, enter uname -a to get all kernel information.

How do I "acpi=force" ? Read this on the Forum. Is that the issue?

acpi is not the issue with the libpng error. However, in order to enter the acpi=force parameter at boot time, look for the kernel options function key listed at the bottom of the GRUB boot screen. On the Openbox flavors, I believe it is F6. Press the key, then press ENTER to select the highlighted Default option. Your cursor will be at the end of the line showing in the text string at the bottom of the screen. Simply type acpi=force, then press ENTER.

[rockland]

Thank for the response.
Video card
Identification
Vendor: ‎Intel Corporation
Description: ‎Mobile 4 Series Chipset Integrated Graphics Controller
Media class: ‎VGA compatible controller
Connection
Bus: ‎PCI
PCI domain: ‎0
Bus PCI #: ‎0
PCI device #: ‎2
PCI function #: ‎0
PCI revision: ‎0x07
Vendor ID: ‎0x8086
Device ID: ‎0x2a42
Sub vendor ID: ‎0x107b
Sub device ID: ‎0x0390
Misc
Module: ‎Card:Intel 810 and later

uname -a information: Linux localhost 2.6.38.8-pclos3.bfs #1 SMP PREEMPT Fri Jul 8 18:01:30 CDT 2011 i686 i686 i386 GNU/Linux

[djohnston]

Laptop freezes and cycles through this error (libpng error) message every time I shutdown. Only way stop the flickering screen and error cycling is a hard reset.

I'm still trying to figure out from that whether you mean that the computer does not properly shut down all the way to a poweroff.

[daniel]

What is the latest messages by shutdown?
ESC tab after click on shutdown, will bring boot messages...

[rockland]

Hello again
Yes, it looks like a terminal screen (black background, white lettering) and ligpng errorline repeating itself line by line. The screen is sort of having a short circuit, flickering and the PCLinuxOS bull keep flashing in the background at the same time.

The laptop does not shut down, flickers and flickers. Sort of disturbing, not natural at all.

[Neal ManBear]

The libpng read error is plymouth trying to read another png image at the end of your boot theme. It is a "null" message; i.e. you can ignore it completely. This is the normal situation of the libpng read error.     

You may have introduced some file system corruption through your hard shutdowns and need to run a file system check/repair, as djohnston said.     

Log in as root, open a Terminal.

Change directory to root (/) directory:
type #: cd /

Create a file called forcefsck:
type#: touch /forcefsck

Now reboot the system:
Type#: reboot

That should clear out any file corruption from the power offs.     

After you have run the file system check, try a reinstall of plymouth and your plymouth theme.     

[rockland]

Neal ManBear
That worked well. Tried several shutdowns and restarts. No errors

For the record
libpng error: read error - kept repeating itself
tried: ctrl alt del
response: INIT: sending process to the TERM signal
response: could not log bootup address already in use
response: libpng error - keeps repeating.

tried F6 at shutdown
response: same png error sequence
ctrl alt del
response: restarting system successful.

Quite the experience. All is well. System is somewhat slower at boot, but no hard reset linux heart attacks. Have no clue what a "plymouth" is or does.

I truly appreciate the support.

Thank You all.

[Neal ManBear]

Neal ManBear
That worked well. Tried several shutdowns and restarts. No errors

     
Mark this as [Solved] please.

For the record
libpng error: read error - kept repeating itself

     
I understood that. That is why I said, "This is the normal situation of the libpng read error." in my description of the libpng error.     

tried: ctrl alt del
response: INIT: sending process to the TERM signal
response: could not log bootup address already in use
response: libpng error - keeps repeating.

tried F6 at shutdown
response: same png error sequence
ctrl alt del
response: restarting system successful.

     
It seems like you had some corruption in plymouth that was causing it to not complete its run.

Quite the experience. All is well. System is somewhat slower at boot, but no hard reset linux heart attacks. Have no clue what a "plymouth" is or does.

I truly appreciate the support.

Thank You all.

     
Plymouth runs the sequence of boot graphics.