Page 19 of 19
Puppy's desktop help-Midori Browser hanging
Posted: Mon 13 Sep 2010, 23:48
by gcmartin
Using 'help' from the Puppy 5.1.1 desktop. The help browser hangs and top shows"
Code: Select all
# [b]top[/b]
CPU: 99% usr 0% sys 0% nic 0% idle 0% io 0% irq 0% sirq
Load average: 1.11 0.39 0.19 2/74 31871
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
17871 18237 root R 126m 6% 0 97% midori file:///usr/share/doc/index.html
31766 4736 root R 2576 0% 0 0% top
Anyone know anything about this Midori lockup in Puppy 5.1.1?
Seems strange that I am getting continual "lock-ups" when viewing Puppy Help from the desktop.
Only way around this is either killing the task(s) or restarting the desktop.
Posted: Tue 21 Sep 2010, 22:53
by edoc
Our son is trying to use a Dpg converter to convert a mkv video file to dpg.
The original file is 343mb.
The computer crashes and powers-off.
Help?
EDIT: When I try Dpg4x on my computer I get the following error text. It was working so I don't know what may have changed in the week or so since I last used it. I do see python2.6 using pfind.
# Dpg4x
Traceback (most recent call last):
File "/usr/local/lib/python2.6/dist-packages/cx_Freeze/initscripts/Console.py", line 27, in <module>
File "/dpg4x_1.1.1/Dpg4x.py", line 17, in <module>
File "/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/__init__.py", line 45, in <module>
File "/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 4, in <module>
File "ExtensionLoader_wx__core_.py", line 12, in <module>
ImportError: /usr/lib/libwx_gtk2u_core-2.8.so.0: version `WXU_2.8.10' not found (required by /usr/share/Dpg4x/wx._core_.so)
#
Puppy clock time
Posted: Mon 04 Oct 2010, 01:12
by In the Doghouse
Set my P.L.510 desktop settings to hardware clock UTC, time zone Pacific. Kept getting the wrong time at bootup. Looked at /root/Startup/settime, which has the single command:
hwclock --hctosys --localtime
The man page for hwclock says --localtime is telling hwclock that my hardware clock runs local time. Why would the settime script contain the --localtime option when I have used the desktop time settings to say I run utc on the hardware clock??? Shouldn't the desktop settings change the the content of the settime script??? Anyway, I changed settime to:
hwclock --hctosys --utc [--utc says my hardware clock is utc]
Now my Puppy Linux boots up with the correct time.
Is it time (excuse the pun) for a bugfix?
P.S.-I would maintain the current utc time on my hardware clock with Psync, but: who wants to have to dismiss the Psync dialogue box after every bootup? Why not add an instruction to Psync for the dialogue box to remove itself after, say, 10 seconds?
Posted: Mon 04 Oct 2010, 11:49
by L18L
Using 'help'
seems that no real newbee ever used Lucid Puppy
Anyone know anything about this Midori lockup in Puppy 5.1.1?
Seems strange that I am getting continual "lock-ups" when viewing Puppy Help from the desktop.
Only way around this is either killing the task(s) or restarting the desktop.
Was the same, of course, in
lupq quickset edition, see
Posted: Sat 02 Oct 2010, 10:57 Subject description: midori again
I have made puppyhelp launch my default browser which is seamonkey and does not lockup.