READ-ONLY Archive
https://oldforum.puppylinux.com/
No solution but a workaround which works for me (most time):Flash wrote:...and I can't reach the part at the top of the window that would allow me to drag it around.
Code: Select all
# wallpaper
** ERROR **: gtkdialog: Error in line 37, near token '<separator>': syntax error
aborting...
/usr/local/apps/Wallpaper/AppRun: line 284: 25417 Aborted gtkdialog3 --program BG_DLG
No difference....another problem cropped up....when the system boots...it never goes into the desktop...I have to type xwin to have the desktop appear.rerwin wrote:
tlchost: Try blacklisting the HSF driver and reboot to see if anything changes regarding the sound issue. Use Menu > System > BootManager... then click the button to 'blacklist' a module. Select "hsfpcibasic2" and click "add", "Ok", "Quit", then reboot.
Hard drive is fine;veronicathecow wrote:Hi rjbrewer, could it be a HDD fault (Dodgy sectors etc. Normally faults tend to be fairly fixed unless the hardware is a bit dicky.
Hope it helps
Tony
I just burned ttuuxxx's 214X11 to CD and installed to a USB stick. 214X11 does not suffer from the cold boot problem exhibited by 4.24 (4.3 beta 2)rwishlaw wrote:I am running 4.3 beta 2 on a no usb boot bios machine. I have burned a CD and installed to a USB stick. When I cold boot from the cdrom Grub does not see the pupsave.2fs nor the install on the USB stick.
All works as expected from a warm boot. I have installed the new Ubuntu53 Grub pet but that did not fix the cold boot problem.
Robert Wishlaw
Mick your like a newbee in Candy store, I know compiling isn't one of strong points, so yes woof is excellent, I always figured you would of tried it sooner for your retro pc. you could really make a nice small version for it., with a retro kernel01micko wrote: Er... you would not believe how easy woof is... no kernel compiling involved at all! As a matter of fact.. no as in zero.. compiling by user.. all done in the scripts!
(Sorry for getting off topic)
Trio,trio wrote:darwin
I just converted and load OpenOffice 3.0 sfs, all works perfectly, including menu items and desktop icons
Yes certainly! If anyone wants to mess around with the default theme in 4.3beta2 and improve it, go for it!01micko wrote:jakfish
One thing.. when BarryK uploads a version (be it a beta or whatever) he usually uploads a 'woof' to go with it. That 'woof' usually has BarryK's latest configuration, such as, what distro, what packages ...etcetera .. (without going into too much detail.. it is a 4.3beta2 bug thread!). BarryK also offers a variety of kernels and of the four or five woofs I've built k2.6.25.16 has always been an option.
So, if you don't mind downloading a few hundred meg and have a spare five hours and a fastish (1.5GHz plus with 512 ram) box, build 4.3 yourself with the older kernel. It will come out essentially the same but may have bugs.
BarryK
I notice the gtk theme is identical to the one in upup-476. Maybe.. (and there is time) you should put out a request for a matching gtk theme for the Raymond Levang (provided by zigbert) wallpaper. Those blokes in the eyecandy thread go nuts when there is a challenge thrown out! Trio has made it easy too, with his 'maker' series, 'JWM theme maker', 'gtk theme maker'.. etc.
Just some food for thought.
Gtkam has been flakey as long as we have used it. This has been going on for a long time, and with each new release I have hoped it would become more stable, but no.paulh177 wrote:gtkam hangs and has to be killed after accessing my canon ixus750 (SD550).
it correctly identifies and connects to the camera. I descend the directory tree in the left pane, then once i clikc on the "100CANON" directory the "initialising camera" progress bar fills, stops and then the whole application is dead and has to be killed.
according to the output of dmesg it seems to have segfaulted
Not just symlinks, file permissions may also get corrupted, which will break some apps.darwinev0lved wrote:darwinev0lved wrote:trio wrote:
oops, my bad - completely missed the "you must not use a FAT directory" warning when upgrading old sfs to sfs4 - have now done so and all seems well. Perhaps we should make it flash a bit and shout "no really, all your simlinks will break if you do not obey this simple command"
Yes, and I must get onto adding dependency checking into Woof, to make it easier to choose a cutdown selection of packages. It's on the to-do list.ttuuxxx wrote:Mick your like a newbee in Candy store, I know compiling isn't one of strong points, so yes woof is excellent, I always figured you would of tried it sooner for your retro pc. you could really make a nice small version for it., with a retro kernel01micko wrote: Er... you would not believe how easy woof is... no kernel compiling involved at all! As a matter of fact.. no as in zero.. compiling by user.. all done in the scripts!
(Sorry for getting off topic)
ttuuxxx
Code: Select all
# probepart
/dev/sda1|vfat|41029946
/dev/sda2|ext3|41013944
/dev/sda3|vfat|894724110
/dev/sdb1|none|208782
/dev/sdb2|none|43006004
/dev/sdb3|none|43006004
/dev/sdb4|none|2
/dev/sdb5|swap|4192902
/dev/sdb6|ext3|886354182
/dev/sr0|iso9660|237856
# fdisk -l /dev/sdb
# Code: Select all
# probepart
/dev/sda1|vfat|41029946
/dev/sda2|ext3|41013944
/dev/sda3|vfat|894724110
/dev/sdb1|ext3|208782
/dev/sdb2|ext3|43006004
/dev/sdb3|ext3|43006004
/dev/sdb4|none|2
/dev/sdb5|swap|4192902
/dev/sdb6|ext3|886354182
/dev/sr0|iso9660|237856
# fdisk -l /dev/sdb
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 2690 21503002+ 83 Linux
/dev/sdb3 2691 5367 21503002+ 83 Linux
/dev/sdb4 5368 60801 445273605 5 Extended
/dev/sdb5 5368 5628 2096451 82 Linux swap / Solaris
/dev/sdb6 5629 60801 443177091 83 Linux