Page 3 of 23
Posted: Sun 14 Aug 2011, 20:24
by pemasu
Peebee. I would not call that error message. It is information that you dont have ac_adapter, battery or lid in your comp. So it is normal report of normal behavior.
Posted: Sun 14 Aug 2011, 22:52
by peebee
pemasu wrote:Peebee. I would not call that error message. It is information that you dont have ac_adapter, battery or lid in your comp. So it is normal report of normal behavior.
hi pemasu
but I do have both battery and ac-adapter and the indicator is there in luci528 but not in 529 with the new kernel....
Posted: Mon 15 Aug 2011, 01:38
by aarf
at first test i think startmount was broke by adding the cputemp v1.3.pet as well.
Code: Select all
** (roxterm:17053): WARNING **: Failed to connect to session manager: SESSION_MANAGER environment variable not defined
/usr/local/Startmount/Startmount: line 110: kill: (21279) - No such process
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
ok
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
** ERROR **: gtkdialog: Error in line 62, near token '</default>': syntax error
aborting...
/usr/local/Startmount/Startmount: line 430: 21482 Aborted gtkdialog3 -p STARTMOUNT -c
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
Posted: Mon 15 Aug 2011, 05:23
by pemasu
Peebee. Okay then it is probably due to the newer kernel. I had that non working situations at the beginning of Ice Puppy 2.6.38.4 kernel project. Powerapplet_tray didnt work. I think it is due to changed way to store the information in linux folder structure by kernel.
CPUTemp pet as posted above, Gatotray, Xsensors and improved conky with separate cpu temp script worked for temp, Vattery (there is pet by Jemimah) worked for battery status, I have abandoned Powerapplet_tray until someone fixes it for newer kernels. Also Conky (1.81 version), and for example e17 wm battery gadget works straight for battery status.
Posted: Mon 15 Aug 2011, 06:44
by peebee
pemasu wrote:Peebee. Okay then it is probably due to the newer kernel. I had that non working situations at the beginning of Ice Puppy 2.6.38.4 kernel project. Powerapplet_tray didnt work. I think it is due to changed way to store the information in linux folder structure by kernel.
Hi Pemasu
I think you are correct - there was also a problem with Vattery as used by your dpup Exprimo if you recall see:
http://www.murga-linux.com/puppy/viewto ... 840cfd846c
but that can be cured by a simple edit as 1vattery is a script.
Cheers
peebee
Posted: Mon 15 Aug 2011, 07:16
by pemasu
Peebee. Yes, your and some other finding was that corrected script with stopping to use vattery-ibam binary, if battery state is unknown is not enough. Sometimes in 1vattery script the unknown should be changed to yes. Otherwise vattery-ibam seqfaults.
Another solution is to remove everything else from the 1vattery starting script and left only exec vattery-acpitool. Acpitool is needed to be installed of course.
Posted: Mon 15 Aug 2011, 08:40
by aarf
my pwidgets battery status is working as it normally does.
the icon i the bottom traty from previous luci/lupu is not there though. puppeees icon/status was better. didnt have to click it to get the info.
Posted: Mon 15 Aug 2011, 11:53
by aarf
aarf wrote:at first test i think startmount was broke by adding the cputemp v1.3.pet as well.
next reboot sdb3 mounted as before! ?
Posted: Mon 15 Aug 2011, 14:37
by playdayz
IMHO, things are coming together very nicely in the Puppy World. Barry has been busy, and has just released an updated Wary, 5.1.3. He has also designated 01micko as Coordinator for the newest Official Puppy, Slacko, which will be released in 6 weeks or so. First off, that means, Slacko can use testers
http://www.murga-linux.com/puppy/viewtopic.php?t=69798
With the release of Wary 5.1.3 now, and the upcoming release of Slacko, there is no need for an official release updating Lucid 5.2.5. The project to update Lucid was originally conceived as a way to get a Puppy release on the charts in the interim--not the purest of motives. This was to be a simple bug-fix release, but it assumed a life of its own. In brief, we made more changes and innovations than we had time to test.
Lucid will not disappear.
All of the changes and innovations have been released as
Two-Headed Dog.
http://www.murga-linux.com/puppy/viewtopic.php?t=70736
Additionally, all of the changes and innovations plus the newer 2.6.37.6 kernel, the same one used in Slacko, have been released as
Three-Headed Dog. So we get two for one.
http://www.murga-linux.com/puppy/viewtopic.php?t=70688
These two releases will be maintained--after all, Lucid is an LTS (Long Term Support) release.
Posted: Mon 15 Aug 2011, 15:22
by Terryphi
Great work, playdayz. I am back with Lucid enjoying the Three-Headed Dog after concentrating on Wary for a while. Glad to hear that the Lucid releases will be maintained as LTS releases! No need to go mad - just update what really must be updated.
Posted: Tue 16 Aug 2011, 06:01
by calexand
What is used as the Devx for three-headed dog, please? Where can it be found/downloaded?
Thank you,
CA
Posted: Tue 16 Aug 2011, 07:42
by aarf
sdb3 mounted at start and startmount gui will open but still the broken pipe in error log?
Code: Select all
usr/local/Startmount/Startmount: line 110: kill: (4506) - No such process
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
ok
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
cat: /root/.startmount/progitem_list: No such file or directory
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
sh: line 5: echo: write error: Broken pipe
(removed many duplicates of broken pipe)
Posted: Tue 16 Aug 2011, 13:44
by playdayz
sdb3 mounted at start and startmount gui will open but still the broken pipe in error log?
I will test that myself and pass it on. We could fix it with update pet. Thanks.
Add -> aarf, For me Startmount only gives that message when the gui is running. I will tell 01micko about that, but what it means to me is that it is safe to use Startmount as is until it gets fixed. When you run the gui it will throw 150 or so messages, but when you close the gui it will stop and it seemed to run as designed--it mounted sdb1 for me.
----------------------------------------------------------------------------
What is used as the Devx for three-headed dog, please? Where can it be found/downloaded?
http://diddywahdiddy.net/Puppy500/luci_devx_528.sfs
9335c402116caea7c302793069e67706
You will need to rename it luci_devx_529.sfs.
Posted: Wed 17 Aug 2011, 00:03
by cthisbear
My N150 wireless usb adaptor now works with this variant....no reboots.
But has a strange bug.
Thanks to all.
"""""""""""
" But when you type in your user name and passwords
the typing box discolours....goes a light purple. "
Weird.
http://www.murga-linux.com/puppy/viewto ... 999#553999
Chris.
Reports
Posted: Wed 17 Aug 2011, 00:44
by gcmartin
System performing very nicely on this laptop. See reports below.
Posted: Wed 17 Aug 2011, 01:32
by aarf
playdayz wrote:sdb3 mounted at start and startmount gui will open but still the broken pipe in error log?
I will test that myself and pass it on. We could fix it with update pet. Thanks.
Add -> aarf, For me Startmount only gives that message when the gui is running. I will tell 01micko about that, but what it means to me is that it is safe to use Startmount as is until it gets fixed. When you run the gui it will throw 150 or so messages, but when you close the gui it will stop and it seemed to run as designed--it mounted sdb1 for me.
- .
what concerns me is that startmount seems to have conflicts with other things eg. boot manager loading sfs (as posted earlier) , and also when pets are installed. if startmount has this issue will/do other things have problems too, or is it something confined to startmount only.
Is this where we report general Lucid issues now?
Posted: Thu 18 Aug 2011, 10:34
by Snail
I upgraded my lupusave from 526rc to Lucisave for 529 via 528. No problems as far as I can see, except the GTK and openbox themes were reset. I had to reload xorg-high, but that may have been "lost" in some previous upgrade.
Since this version seems to have few problems, I assume that it will become the main-line LucidPuppy. Hence it seems to make sense to report any issues in this forum, even if they are not confined to 529?
I was sent a .wav file. Clicking on it in Rox resulted in maximum volume static that seemed likely to destroy my speakers, with no way of turning it off, except by rebooting. This also happens if right-click is used to select Gnome-Mplayer or Mplayer. The file plays OK in WinXP. It also plays beautifully in PMusic in 529.
The only other .wav files I have are the Skype sounds. They are fine in all three sound programs. I cannot post the rogue .wav file as it contains confidential info. However, Rox right click -> Properties gives:
RIFF (little-endian) data, WAVE audio, mono 8000 Hz
whereas the Skype sounds are:
RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 16000 Hz
An easy fix was to set the .wav run action to PMusic
The file came as an email attachment. Trying to open it in the Seamonkey email window crashes Seamonkey. It sometimes leaves a large blank black window behind, which can be shut down, so it isn't completely unresponsive.
Rox right clicks Again!!
Posted: Thu 18 Aug 2011, 11:08
by Snail
It will be no secret by now that right clicks is dear to my heart
I have just booted 529 with pfix=ram and discovered to my intense amazement that right-clicks has been left out! When did this happen? Is this intended?
I see that there are more .wav files in the system files and none of them seem to have problems with the default player, but mine still does with pfix-ram.
Posted: Thu 18 Aug 2011, 13:32
by tasmod
Startmount
sdb3 suggests USB stick ??
In the notes Micko and I mention that support for USB is experimental.
Posted: Thu 18 Aug 2011, 13:40
by playdayz
It will be no secret by now that right clicks is dear to my heart I have just booted 529 with pfix=ram and discovered to my intense amazement that right-clicks has been left out!
Snail, Right-clicks is in luci-529. I just checked. I removed a few items such as "play audio/video with mplayer" because I thought they were confusing--that something would play and the user would have no obvious way to turn it off.
Unless we mean something different by "right-clicks."